brief 1.9.9 → 1.9.11

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 1e5778cd99dfcb00c4420b4fedfb0e4e69b61d0b
-  data.tar.gz: 1c551d49bf311134309dcff740d1492200deeea2
+  metadata.gz: 0df5a7957404e6281f7da3ea81daae61d24a2b42
+  data.tar.gz: eab76b0724000e106e08579e415570fd474a8139
 SHA512:
-  metadata.gz: d23643282699bf917fb20805a229e82138abe51babef4454e137f90802ef3786d4d6b8ff61661a77b368a363fbf5b21d6871002e76d7b479458409111b7a4edd
-  data.tar.gz: 861e4cc4df911860dcc481bd3e25d208f815f3f3ce078d05ae515e0d07408c71559c309d6cfb69cb898b613b150a2fd2fe18f4c7b3574bb495be70ec575e9808
+  metadata.gz: eabd297d3e1ee5ce7291156a91084a52e095aca03b798cbb1000c55fa1516c12801ceec9a8b1ec6d50f84b787057b4837d289efd67194bd967e47df262e53ae1
+  data.tar.gz: aebc6b9b3dc5974beda9cc6ca301bc0e65fd2e9009721f728258fdef68820a83660e790a6d7e454c01616e86033b18f6ed35d0129b9abb75276ef2293547dbb4

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    brief (1.9.8)
+    brief (1.9.11)
       activesupport (~> 4.0)
       commander (~> 4.3)
       em-websocket (= 0.5.1)
@@ -24,7 +24,7 @@ GEM
       minitest (~> 5.1)
       thread_safe (~> 0.3, >= 0.3.4)
       tzinfo (~> 1.1)
-    addressable (2.3.7)
+    addressable (2.3.8)
     axiom-types (0.1.1)
       descendants_tracker (~> 0.0.4)
       ice_nine (~> 0.11.0)
@@ -32,7 +32,7 @@ GEM
     coderay (1.1.0)
     coercible (1.0.0)
       descendants_tracker (~> 0.0.1)
-    commander (4.3.3)
+    commander (4.3.4)
       highline (~> 1.7.2)
     daemons (1.2.2)
     descendants_tracker (0.0.4)
@@ -70,22 +70,23 @@ GEM
       coderay (~> 1.1.0)
       method_source (~> 0.8.1)
       slop (~> 3.4)
-    rack (1.6.0)
+    rack (1.6.1)
     rack-test (0.6.3)
       rack (>= 1.0)
     rake (0.9.6)
-    rspec (3.1.0)
-      rspec-core (~> 3.1.0)
-      rspec-expectations (~> 3.1.0)
-      rspec-mocks (~> 3.1.0)
-    rspec-core (3.1.7)
-      rspec-support (~> 3.1.0)
-    rspec-expectations (3.1.2)
+    rspec (3.2.0)
+      rspec-core (~> 3.2.0)
+      rspec-expectations (~> 3.2.0)
+      rspec-mocks (~> 3.2.0)
+    rspec-core (3.2.3)
+      rspec-support (~> 3.2.0)
+    rspec-expectations (3.2.1)
       diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.1.0)
-    rspec-mocks (3.1.3)
-      rspec-support (~> 3.1.0)
-    rspec-support (3.1.2)
+      rspec-support (~> 3.2.0)
+    rspec-mocks (3.2.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.2.0)
+    rspec-support (3.2.2)
     sawyer (0.6.0)
       addressable (~> 2.3.5)
       faraday (~> 0.8, < 0.10)

data/README.md

@@ -2,194 +2,72 @@
 [![Build
 Status](https://travis-ci.org/datapimp/brief.svg?branch=master)](https://travis-ci.org/datapimp/brief)
 
-Brief is a tool for building applications on top of collections of
-documents written in markdown.  
+### Putting your writing to work
 
-Brief lets you define models very similar to how you would in
-ActiveRecord and Rails, but instead of rows in a database you are 
-going to be working with files in a folder.
+Brief lets writers build applications on top of collections of markdown
+files.  Brief lets you define different classes or types of documents, called
+`Model`s.  
 
-### Getting Started
-```
-gem install brief
-brief --help
-```
-
-### Hypothetical Example
+These models turn the documents into objects, which can be
+used to do things such as make API calls, or publish a blog post and
+send an email campaign at the same time. 
 
-```
-brief init my-cookbook
-cd my-cookbook
-brief generate model Recipe # View the DOCUMENTATION for what you can do with a model
-brief write recipe # => opens up your $EDITOR with an example recipe
-```
+### Turn documents into data 
 
-Brief treats each markdown file as an active record style model object. It treats a folder of markdown files like a database.
+The most basic way of combining writing with data, is through the use of
+YAML Frontmatter as metadata for the document.  For example:
 
-### How does it work?
-
-Brief takes a markdown file which looks like:
-
-```markdown
+```
 ---
 type: post
-status: active
+status: draft
+tags:
+  - help
+  - ruby
 ---
 
-# An introduction to brief 
-## Stop writing dead documents 
+# This is a title
+## This is a subtitle
 
-Brief is a tool which lets you define different patterns of markdown
-headings (h1,h2,h3 etc). This lets you work with collections of your
-writings, and treat each document as a database. 
-```
+This is the first paragraph.
 
-And turns it into data, not only using the metadata up top, but also the information
-contained in the structure of the document itself.  The headings, subheadings, pretty much
-anything you could query from the HTML using CSS can be turned into key value pairs that you can work
-with and build applications on top of.
-
-With your enhanced writing, you can do things like:
-
-```ruby
-# Find all the posts which are active:
-posts = briefcase.posts.where(status:"published")
-
-# Get their titles, and subheadings:
-posts.map(&:title) #=>['An introduction to brief']
-posts.map(&:subheading) #=>['Stop writing dead documents']
-
-# Publish the post
-posts.first.publish()
-
-# Email the drafts to your editor
-posts.where(status:"draft").each &:mail_to_editors
+This is another pargraph.
 ```
 
-From the Command line we can:
+This YAML content at the top gets turned into data associated with the
+document. 
 
-```bash
-brief publish posts 
-brief write post #=> Opens your editor
+```
+post = Post.new("/path/to/post.md") 
+post.status # => 'draft'
+post.tags # => ['help','ruby']
 ```
 
-This type of interactivity is made possible by the `Brief::Model`
+The YAML data is useful, but where the brief model system really shines
+is in the ability to extract data and metadata from the writing itself.
 
-### Documents as models
+Each `Model` prescribes its own specific structure, usually
+in the form of heading hierarchys (h1, h2, h3, etc). Any CSS selector
+can be used against the rendered HTML produced by the markdown.  A
+model can define attributes that will be extracted from the writing, for
+example:
 
 ```ruby
 define "Post" do
-  meta do
-    status
-  end
-
   content do
     title "h1:first-of-type"
-    subheading "h2:first-of-type"
-    sample "p:first-of-type"
-  end
-
-  actions do
-    def publish
-      update_attributes(status: "published")
-    end
-  end
-end
-```
-
-### CLI Tool
-
-Brief gives you a CLI called `brief`
-
-This lets you run some general commands, but also gives you an
-intelligent interface to work with your models.  In the above example,
-we defined some actions.
+    subtitle "h2:first-of-type"
+    excerpt "p:first-of-type"
 
-This will be available in the CLI:
-
-```
-brief publish posts ./docs/posts/*.md
-```
-
-This will find all of the matching documents, turn them into `Post`
-models, and then run the publish method on them.  You can make your
-models as advanced as you want:
-
-```
-define "Post" do
-  actions do
-    def submit 
-      update_attributes(status:"submitted to editors")
-      mailer.send(:to => "jon@chicago.com", :subject => "Please review: #{ self.title }")
-    end
+    # parses YAML blocks inside the document
+    settings 'code.yaml', :serialize => true
   end
 end
 ```
 
-### YAML Frontmatter
-
-Each markdown document can contain YAML frontmatter.  This data will be
-available and associated with each document or model, and will also let
-you query, filter, and sort your documents.
-
-### CSS Structure Definition
-
-Since markdown renders into HTML, and HTML Documents can be queried
-using CSS selectors, we use CSS selectors in our model definition DSL so
-that we can isolate certain parts of the document, and use the content
-it contains as metadata.
-
-A real world example:
-
-```ruby
-  content do
-    title "h1:first-of-type"
-    define_section "User Stories" do
-      each("h2").has(:title     => "h2",
-                     :paragraph => "p:first-of-type",
-                     :components   => "p:first-of-type strong"
-                    )
-
-      each("h2").is_a :user_story
-    end
-  end
-```
-
-This lets me turn a markdown file like:
-
-```markdown
----
-title: Epic Example
-status: published
----
-# Epic Example
-# User Stories
-
-## A user wants to do something
-As a **User** I would like to **Do this** so that I can **succeed**
+### Getting Started
 
-## A user wants to do something else
-As a **User** I would like to **Do this** so that I can **succeed**
 ```
-
-into:
-
-```ruby
-{
-  title: "Epic Example",
-  status: "published",
-  type: "epic",
-  user_stories:[{
-    title: "A user wants to do something",
-    paragraph: "As a user I would like to do something so that I can succeed",
-    goal: "I can succeed",
-    persona: "user",
-    behavior: "do something"
-  },{
-    title: "A user wants to do something else",
-    paragraph: "As a user I would like to do something else so that I can succeed"
-  }]
-}
+gem install brief
+brief --help
 ```
-
-And we can even go in the other direction.

data/Rakefile

@@ -2,6 +2,9 @@ Dir[File.join(Dir.pwd, 'tasks', '**', '*.rb')].each { |f| require f }
 Dir[File.join(Dir.pwd, 'tasks', '*.rake')].each { |f| load f }
 
 require "bundler/gem_tasks"
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new(:spec)
 
 Distribution.configure do |config|
   config.package_name = 'brief'
@@ -21,3 +24,5 @@ Distribution.configure do |config|
     'unf_ext-0.0.6'
   ]
 end
+
+task :default => :spec

data/apps/blueprint/config.rb

@@ -13,6 +13,10 @@ view(:summary) do |*args|
   end
 end
 
+config do
+  set(:documentation_path, File.join(File.dirname(__FILE__), 'documentation'))
+end
+
 class Brief::Briefcase
   def has_table_of_contents?
     docs_path.join('index.md').exist?

data/apps/blueprint/documentation/diagram.md

@@ -0,0 +1,13 @@
+# Blueprint Diagram
+
+The Diagram model is useful for combining notes with an SVG diagram.
+
+One workflow I like to use is building a UML Diagram in Google Draw, and
+exporting it as SVG.  Then using a tool like Adobe Illustrator, I will
+group the elements of the diagram, and then assign IDs and Classes to
+them.  
+
+The Diagram document allows for a section called Annotations.  The
+Annotations section will be parsed, and treated as data.  This allows
+for rendering the diagram document, along with the diagram itself, and
+displaying the annotations in a novel way.

data/apps/blueprint/documentation/epic.md

@@ -0,0 +1,10 @@
+# Feature Epics
+
+The Feature Epic model is a document that is used to document a bunch of
+related user stories related to a general feature category or group.
+
+For example you might have a "3rd Party Integrations" Epic which has
+User Stories for LinkedIn, Facebook, Github, and Twitter.  
+
+The Epic Document can be used to describe the importance of the module 
+as a whole at the same time that it captures the user stories.

data/apps/blueprint/documentation/milestone.md

@@ -0,0 +1,4 @@
+# Milestone
+
+The milestone represents a due date for a release or delivery of
+software.   

data/apps/blueprint/documentation/outline.md

@@ -0,0 +1,6 @@
+# Outline
+
+The Outline document can be used to create a summary page with links to
+a bunch of other pages.
+
+The outline model can be 

data/apps/blueprint/models/diagram.rb

@@ -1,6 +1,8 @@
 class Brief::Apps::Blueprint::Diagram
   include Brief::Model
 
+  defined_in Pathname(__FILE__)
+
   meta do
     title
     subheading
@@ -13,7 +15,7 @@ class Brief::Apps::Blueprint::Diagram
     subheading "h2:first-of-type"
 
     define_section "Annotations" do
-      each("h2").has(:title => "h3",
+      each("h2").has(:title => "h2",
                      :paragraphs => "p",
                      :settings => "code")
     end

data/apps/blueprint/models/epic.rb

@@ -1,6 +1,8 @@
 class Brief::Apps::Blueprint::Epic
   include Brief::Model
 
+  defined_in Pathname(__FILE__)
+
   meta do
     title
     subheading

data/apps/blueprint/models/milestone.rb

@@ -1,6 +1,8 @@
-class Brief::Apps::Blueprint::Milestones
+class Brief::Apps::Blueprint::Milestone
   include Brief::Model
 
+  defined_in Pathname(__FILE__)
+
   meta do
     title
     number

data/apps/blueprint/models/outline.rb

@@ -1,6 +1,8 @@
 class Brief::Apps::Blueprint::Outline
   include Brief::Model
 
+  defined_in Pathname(__FILE__)
+
   meta do
     type
   end
@@ -14,5 +16,16 @@ class Brief::Apps::Blueprint::Outline
     h6 "h6"
     headings "h1,h2,h3,h4,h5,h6"
     settings "code.yaml:first-of-type", :serialize => :yaml, :hide => true
+
+    nested_links "li a"
+
+    items "ul > li"
+    nested_items "ul > li li"
+  end
+
+  helpers do
+    def link_elements
+      document.css('a')
+    end
   end
 end

data/apps/blueprint/models/page.rb

@@ -1,6 +1,8 @@
 class Brief::Apps::Blueprint::Page
   include Brief::Model
 
+  defined_in Pathname(__FILE__)
+
   meta do
     title
     category

data/apps/blueprint/models/persona.rb

@@ -1,6 +1,8 @@
 class Brief::Apps::Blueprint::Persona
   include Brief::Model
 
+  defined_in Pathname(__FILE__)
+
   meta do
     title
   end

data/apps/blueprint/models/project.rb

@@ -1,6 +1,8 @@
 class Brief::Apps::Blueprint::Project
   include Brief::Model
 
+  defined_in Pathname(__FILE__)
+
   meta do
     title
     category

data/apps/blueprint/models/release.rb

@@ -1,6 +1,8 @@
 class Brief::Apps::Blueprint::Release
   include Brief::Model
 
+  defined_in Pathname(__FILE__)
+
   meta do
     title
     status

data/apps/blueprint/models/roadmap.rb

@@ -1,6 +1,8 @@
 class Brief::Apps::Blueprint::Roadmap
   include Brief::Model
 
+  defined_in Pathname(__FILE__)
+
   meta do
     title
     subheading

data/apps/blueprint/models/sitemap.rb

@@ -1,6 +1,8 @@
 class Brief::Apps::Blueprint::Sitemap
   include Brief::Model
 
+  defined_in Pathname(__FILE__)
+
   meta do
     title
     status

data/apps/blueprint/models/user_story.rb

@@ -1,6 +1,8 @@
 class Brief::Apps::Blueprint::UserStory
   include Brief::Model
 
+  defined_in Pathname(__FILE__)
+
   meta do
     title
     status :in => %w(draft published)

data/apps/blueprint/models/wireframe.rb

@@ -1,6 +1,8 @@
 class Brief::Apps::Blueprint::Wireframe
   include Brief::Model
 
+  defined_in Pathname(__FILE__)
+
   meta do
     title
     parent_title

data/lib/brief.rb

@@ -69,7 +69,9 @@ module Brief
   def self.load_commands
     Dir[lib_root.join('brief', 'cli', '**/*.rb')].each { |f| require(f) }
 
-    # the instance methods which get defined with the helper
+    # Each Brief::Model can define certain "actions" which can be called on the documents.
+    #
+    # The Brief CLI interface lets users dispatch these actions to the documents specified by the PATH args.
     Brief::Model.classes.each do |klass|
       Array(klass.defined_actions).uniq.each do |action|
         Brief::Util.create_method_dispatcher_command_for(action, klass)
@@ -125,6 +127,7 @@ require 'brief/model/serializers'
 require 'brief/data'
 require 'brief/dsl'
 require 'brief/server'
+require 'brief/briefcase/documentation'
 require 'brief/briefcase'
 require 'brief/apps'
 

data/lib/brief/briefcase.rb

@@ -1,6 +1,7 @@
 module Brief
   class Briefcase
     include Brief::DSL
+    include Brief::Briefcase::Documentation
 
     attr_reader :options,
                 :model_definitions
@@ -50,6 +51,9 @@ module Brief
       end
     end
 
+    # TODO
+    # The serialization of an entire briefcase at once
+    # is important enough to be its own module
     def as_default(params={})
       params.symbolize_keys!
 
@@ -74,6 +78,10 @@ module Brief
         base[:schema] = schema_map
       end
 
+      if params[:include_documentation] || params[:documentation]
+        base[:documentation] = render_documentation
+      end
+
       if params[:include_models] || params[:models]
         model_settings = {
           docs_path: docs_path
@@ -106,12 +114,6 @@ module Brief
       run(app_config_path) if app_path.try(&:exist?)
     end
 
-    def schema_map(include_all=false)
-      list = include_all ? Brief::Model.classes : model_classes
-      list.map(&:to_schema)
-        .reduce({}.to_mash) {|m, k| m[k[:type_alias]] = k; m }
-    end
-
     def data
       @data ||= data!
     end

data/lib/brief/briefcase/documentation.rb

@@ -0,0 +1,36 @@
+module Brief
+  class Briefcase
+    module Documentation
+
+      class ModelDoc
+        def initialize(path)
+          @content = Pathname(path).read
+        end
+
+        def content
+          @content
+        end
+
+        def rendered
+          ::GitHub::Markdown.render_gfm(content)
+        end
+      end
+
+      def render_documentation(include_all=false)
+        list = include_all ? Brief::Model.classes : model_classes
+
+        list.reduce({}.to_mash) do |memo, klass|
+          docs = klass.to_documentation rescue {}
+          memo[klass.type_alias] = docs unless docs.empty?
+          memo
+        end
+      end
+
+      def schema_map(include_all=false)
+        list = include_all ? Brief::Model.classes : model_classes
+        list.map(&:to_schema)
+          .reduce({}.to_mash) {|m, k| m[k[:type_alias]] = k; m }
+      end
+    end
+  end
+end

data/lib/brief/cli/export.rb

@@ -1,42 +1,3 @@
-command 'dispatch export' do |c|
-  c.syntax = 'brief dispatch export PATH [OPTIONS]'
-  c.description = 'dispatch the export the briefcase found in PATH'
-
-  c.option '--presenter-format FORMAT', String, 'Which presenter to use?'
-  c.option '--include-schema', 'Include schema information'
-  c.option '--include-models', 'Include individual models as well'
-  c.option '--include-data', 'Gets passed to the model renderers if present'
-  c.option '--include-content', 'Gets passed to the model renderers if present'
-  c.option '--include-rendered', 'Gets passed to the model renderers if present'
-  c.option '--include-attachments', 'Gets passed to the model renderers if present'
-  c.option '--include-urls', 'Gets passed to the model renderers if present'
-  c.option '--gateway', 'The remote server is a gateway'
-  c.option '--port DRB_PORT', String, 'The DRb port to use'
-  c.option '--briefcase KEY', String, 'Which briefcase should we use? if this is a gateway'
-  c.option '--output FILE', String, 'Save the output in the specified path'
-  c.option '--format FORMAT', String, 'How to format the CLI output: defaults to printed, accepts printed,json'
-  c.option '--prefix-output CONTENT', String, 'Prefix the generated output with the following content'
-
-  c.when_called do |args, options|
-    require 'drb'
-    options.default(:port => 9000, briefcase: Pathname(Brief.pwd).dirname.to_s)
-
-    remote = DRbObject.new(nil, "druby://:#{ options.port }")
-
-    if options.gateway
-      remote = remote.briefcases[options.briefcase]
-    end
-
-    result = remote.present(options.presenter_format, rendered: options.include_rendered,
-                                             content: options.include_content,
-                                             urls: options.include_urls,
-                                             schema: options.include_schema,
-                                             data: options.include_data,
-                                             attachments: options.include_attachments,
-                                             models: options.include_models).as_json
-  end
-end
-
 command 'export' do |c|
   c.syntax = 'brief export PATH [OPTIONS]'
   c.description = 'export the briefcase found in PATH'

data/lib/brief/document/attachments.rb

@@ -9,10 +9,19 @@ module Brief
         Array(data.attachments)
       end
 
+      def attachment_paths
+        attachments.reduce({}.to_mash) do |memo, name|
+          if asset = briefcase.find_asset(name)
+            memo[name] = asset.realpath.to_s
+            memo
+          end
+        end
+      end
+
       def render_attachments
         attachments.reduce({}.to_mash) do |memo, name|
           if asset = briefcase.find_asset(name)
-            memo[name] = IO.read(asset)
+            memo[name] = IO.read(asset) if asset.to_s.match(/\.svg/i)
             memo
           end
         end

data/lib/brief/model.rb

@@ -124,12 +124,36 @@ module Brief
         (definition.content_schema.attributes.keys + definition.metadata_schema.keys).uniq
       end
 
+      def to_documentation
+        docs = definition.documentation
+
+        path = if docs.markdown
+                 Pathname(docs.markdown)
+               elsif defined_in
+                 basename = defined_in.basename.to_s.gsub(/.rb/,'')
+                 defined_in.parent.join('..','documentation',"#{basename}.md")
+               end
+
+        if path
+          model_doc = Brief::Briefcase::Documentation::ModelDoc.new(path)
+
+          {
+            content: model_doc.content,
+            rendered: model_doc.rendered
+          }
+        else
+          {
+          }
+        end
+      end
+
       def to_schema
         {
           schema: {
             content: definition.content_schema,
             metadata: definition.metadata_schema,
           },
+          documentation: to_documentation,
           class_name: to_s,
           type_alias: type_alias,
           name: name,
@@ -236,10 +260,22 @@ module Brief
         definition.send(:example_body, *args).to_s.strip
       end
 
+      def documentation(*args)
+        definition.send(:documentation, *args)
+      end
+
+      def defined_in(*args)
+        definition.send(:defined_in, *args)
+      end
+
       def method_missing(meth, *args, &block)
+        # these methods when called at a class level inside of
+        # a class definition body will modify the schema settings for that model
         if %w(meta content template example actions helpers).include?(meth.to_s)
           definition.send(meth, *args, &block)
           finalize
+        # these methods allow the model class to inspect itself and report
+        # whatever methods and actions are defined on the model class
         elsif %w(defined_helper_methods defined_actions).include?(meth.to_s)
           definition.send(meth)
         elsif meth.to_s.match(/^on_(.*)_change$/)

data/lib/brief/model/definition.rb

@@ -19,6 +19,8 @@ module Brief
       @section_mappings = {}.to_mash
       @content_schema   = { attributes: {} }.to_mash
       @model_class      = options[:model_class]
+
+      @doc_options = {}.to_mash
     end
 
     def valid?
@@ -61,6 +63,23 @@ module Brief
       Brief.configuration.model_namespace || Brief::Model
     end
 
+    # TODO
+    # There is probably a way to inspect the filename of the code calling you
+    # which would be a better way of handling this that doesn't require
+    def defined_in(filename=nil)
+      if filename
+        filename = Pathname(filename)
+        @doc_options[:defined_in] = filename
+      end
+
+      @doc_options[:defined_in]
+    end
+
+    def documentation(options={}, &block)
+      @doc_options.merge!(options) if options
+      @doc_options
+    end
+
     def meta(_options = {}, &block)
       @current = :meta
       instance_eval(&block)

data/lib/brief/model/serializers.rb

@@ -33,6 +33,7 @@ module Brief::Model::Serializers
 
       if options[:attachments] || options[:include_attachments]
         h[:attachments] = document.render_attachments
+        h[:attachment_paths] = document.attachment_paths
       end
 
       h[:urls] = {

data/lib/brief/version.rb

@@ -1,3 +1,3 @@
 module Brief
-  VERSION = '1.9.9'
+  VERSION = '1.9.11'
 end

data/spec/lib/brief/apps_spec.rb

@@ -6,7 +6,12 @@ describe "Packaged Apps" do
   end
 
   let(:blueprint) do
-    Brief::Briefcase.new(app: "blueprint")
+    Brief::Briefcase.new(app: "blueprint", root: Brief.spec_root.join('fixtures','example'))
+  end
+
+  it "renders documentation for the app" do
+    rendered = blueprint.render_documentation.epic.rendered
+    expect(rendered).to include("h1")
   end
 
   it "should find the right path for an app name" do

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: brief
 version: !ruby/object:Gem::Version
-  version: 1.9.9
+  version: 1.9.11
 platform: ruby
 authors:
 - Jonathan Soeder
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-05-11 00:00:00.000000000 Z
+date: 2015-05-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: hashie
@@ -289,6 +289,20 @@ files:
 - Rakefile
 - TUTORIAL.md
 - apps/blueprint/config.rb
+- apps/blueprint/documentation/diagram.md
+- apps/blueprint/documentation/epic.md
+- apps/blueprint/documentation/milestone.md
+- apps/blueprint/documentation/outline.md
+- apps/blueprint/documentation/page.md
+- apps/blueprint/documentation/persona.md
+- apps/blueprint/documentation/project.md
+- apps/blueprint/documentation/release.md
+- apps/blueprint/documentation/roadmap.md
+- apps/blueprint/documentation/sitemap.md
+- apps/blueprint/documentation/user_story.md
+- apps/blueprint/documentation/wireframe.md
+- apps/blueprint/example/brief.rb
+- apps/blueprint/example/docs/diagrams/example-diagram.md
 - apps/blueprint/models/diagram.rb
 - apps/blueprint/models/epic.rb
 - apps/blueprint/models/milestone.rb
@@ -314,6 +328,7 @@ files:
 - lib/brief/adapters/middleman_extension.rb
 - lib/brief/apps.rb
 - lib/brief/briefcase.rb
+- lib/brief/briefcase/documentation.rb
 - lib/brief/briefcase/initializer.rb
 - lib/brief/cli/01_extensions.rb
 - lib/brief/cli/all.rb