middleman-core 3.0.0.alpha.7

data/Rakefile

@@ -0,0 +1,5 @@
+# coding:utf-8
+RAKE_ROOT = __FILE__
+
+require 'rubygems'
+require File.expand_path(File.dirname(__FILE__) + '/../gem_rake_helper')

data/bin/middleman

@@ -0,0 +1,52 @@
+#!/usr/bin/env ruby
+
+# Add our lib/ directory to the path
+libdir = File.expand_path(File.join(File.dirname(File.dirname(__FILE__)), "lib"))
+$LOAD_PATH.unshift(libdir) unless $LOAD_PATH.include?(libdir)
+
+# Setup RubyGems
+require "rubygems"
+
+# Core Pathname library used for traversal
+require "pathname"
+
+# Recursive method to find config.rb
+def locate_middleman_root!(cwd = Pathname.new(Dir.pwd))
+  return cwd.to_s if File.exists?(File.join(cwd, 'config.rb'))
+  return false if cwd.root?
+  locate_middleman_root!(cwd.parent)
+end
+
+# Only look for config.rb if MM_ROOT isn't set
+if !ENV["MM_ROOT"] && found_path = locate_middleman_root!
+  ENV["MM_ROOT"] = found_path
+end
+
+# If we've found the root, try to setup Bundler
+if ENV["MM_ROOT"]
+  
+  # Set up gems listed in the Gemfile.
+  ENV['BUNDLE_GEMFILE'] ||= File.expand_path('Gemfile', ENV["MM_ROOT"])
+  require 'bundler/setup' if File.exists?(ENV['BUNDLE_GEMFILE'])
+end
+
+# Default command is server
+ARGV << "server" if ARGV.length < 1
+
+# Require Middleman
+require 'middleman-core'
+
+begin
+  # Rubygems
+  require "middleman-more"
+rescue LoadError
+  # Local
+  require File.expand_path(File.join(File.dirname(File.dirname(libdir)), "middleman-more", "lib", "middleman-more"))
+end
+
+# Change directory to the root
+Dir.chdir(ENV["MM_ROOT"] || Dir.pwd) do
+  
+  # Start the CLI
+  Middleman::Cli::Base.start
+end

data/features/3rd_party_cli.feature

@@ -0,0 +1,5 @@
+Feature: Allow config.rb and extensions to add CLI commands
+  Scenario: Test 3rd Party Command
+    Given a fixture app "3rd-party-command"
+    When I run `middleman hello`
+    Then the output should contain "Hello World"

data/features/asset_host.feature

@@ -0,0 +1,7 @@
+Feature: Alternate between multiple asset hosts
+  In order to speed up page loading
+    
+  Scenario: Rendering html with the feature enabled
+    Given the Server is running at "asset-host-app"
+    When I go to "/asset_host.html"
+    Then I should see "http://assets"

data/features/auto_layout.feature

@@ -0,0 +1,36 @@
+Feature: Provide Sane Defaults for Layout Behavior
+
+  Scenario: Template and Layout of same engine exist
+    Given the Server is running at "engine-matching-layout"
+    When I go to "/index.html"
+    Then I should see "Comment in layout"
+  
+  Scenario: Template and Layout of different engine
+    Given the Server is running at "different-engine-layout"
+    When I go to "/index.html"
+    Then I should see "Comment in layout"
+  
+  Scenario: Multiple layouts exist, prefer same engine
+    Given the Server is running at "multiple-layouts"
+    When I go to "/index.html"
+    Then I should see "ERb Comment in layout"
+  
+  Scenario: No layout exists
+    Given the Server is running at "no-layout"
+    When I go to "/index.html"
+    Then I should not see "Comment in layout"
+  
+  Scenario: Manually set default layout in config (exists)
+    Given the Server is running at "manual-layout"
+    When I go to "/index.html"
+    Then I should see "Custom Comment in layout"
+    
+  Scenario: Manually set default layout in config (does not exist)
+    Given the Server is running at "manual-layout-missing"
+    When I go to "/index.html"
+    Then I should see "Error"
+  
+  Scenario: Overwrite manual layout
+    Given the Server is running at "manual-layout-override"
+    When I go to "/index.html"
+    Then I should see "Another Comment in layout"

data/features/automatic_image_sizes.feature

@@ -0,0 +1,16 @@
+Feature: Automatically detect and insert image dimensions into tags
+  In order to speed up development and appease YSlow
+
+  Scenario: Rendering an image with the feature disabled
+    Given "automatic_image_sizes" feature is "disabled"
+    And the Server is running at "automatic-image-size-app"
+    When I go to "/auto-image-sizes.html"
+    Then I should not see "width="
+    And I should not see "height="
+  
+  Scenario: Rendering an image with the feature enabled
+    Given "automatic_image_sizes" feature is "enabled"
+    And the Server is running at "automatic-image-size-app"
+    When I go to "/auto-image-sizes.html"
+    Then I should see "width="
+    And I should see "height="

data/features/builder.feature

@@ -0,0 +1,50 @@
+Feature: Builder
+  In order to output static html and css for delivery
+
+  Scenario: Checking built folder for content
+    Given a successfully built app at "large-build-app"
+    When I cd to "build"
+    Then the following files should exist:
+      | index.html                                    |
+      | static.html                                   |
+      | services/index.html                           |
+      | stylesheets/static.css                        |
+      | spaces in file.html                           |
+      | images/blank.gif                              |
+      | images/Read me (example).txt                  |
+      | images/Child folder/regular_file(example).txt |
+      | .htaccess                                     |
+    Then the following files should not exist:
+      | _partial                                      |
+      | layout                                        |
+      | other_layout                                  |
+      | layouts/custom                                |
+      | layouts/content_for                           |
+      
+    And the file "index.html" should contain "Comment in layout"
+    And the file "index.html" should contain "<h1>Welcome</h1>"
+    And the file "static.html" should contain "Static, no code!"
+    And the file "services/index.html" should contain "Services"
+    And the file "stylesheets/static.css" should contain "body"
+    And the file "spaces in file.html" should contain "spaces"
+    
+  Scenario: Build glob
+    Given a successfully built app at "glob-app" with flags "--glob '*.css'"
+    When I cd to "build"
+    Then the following files should not exist:
+      | index.html                                    |
+    Then the following files should exist:
+      | stylesheets/site.css                          |
+  
+  Scenario: Build with errors
+    Given a built app at "build-with-errors-app"
+    Then the exit status should be 1
+  
+  Scenario: Build empty errors
+    Given a built app at "empty-app"
+    Then the exit status should be 1
+
+  Scenario: Build alias (b)
+    Given a fixture app "large-build-app"
+    When I run `middleman b`
+    Then was successfully built

data/features/chained_templates.feature

@@ -0,0 +1,19 @@
+Feature: Templates should be chainable
+  In order to insert variables and data in "static" engines
+
+  Scenario: Data in Erb in Markdown
+    Given the Server is running at "chained-app"
+    When I go to "/index.html"
+    Then I should see "Title</h1>"
+    And I should see "Subtitle</h2>"
+    And I should see "Sup</h3>"
+    
+  Scenario: Build chained template
+    Given a successfully built app at "chained-app"
+    When I cd to "build"
+    Then the following files should exist:
+      | index.html                                    |
+
+    And the file "index.html" should contain "Title</h1>"
+    And the file "index.html" should contain "Subtitle</h2>"
+    And the file "index.html" should contain "Sup</h3>"

data/features/clean_build.feature

@@ -0,0 +1,31 @@
+Feature: Build Clean
+  Scenario: Build and Clean an app
+    Given a fixture app "clean-app"
+    And app "clean-app" is using config "empty"
+    And a successfully built app at "clean-app"
+    And app "clean-app" is using config "complications"
+    
+    Given a successfully built app at "clean-app" with flags "--clean"
+    When I cd to "build"
+    Then the following files should not exist:
+      | should_be_ignored.html                        |
+      | should_be_ignored2.html                       |
+      | should_be_ignored3.html                       |
+    And the file "index.html" should contain "Comment in layout"
+
+  Scenario: Clean an app with directory indexes
+    Given a successfully built app at "clean-dir-app"
+    When I cd to "build"
+    Then the following files should exist:
+      | about/index.html                               |
+    
+    Given a successfully built app at "clean-dir-app" with flags "--clean"
+      When I cd to "build"
+    Then the following files should exist:
+      | about/index.html                               |
+
+  Scenario: Clean build an app that's never been built
+    Given a successfully built app at "clean-dir-app" with flags "--clean"
+    When I cd to "build"
+    Then the following files should exist:
+      | about/index.html                               |

data/features/cli.feature

@@ -0,0 +1,120 @@
+Feature: Middleman CLI
+
+  Scenario: Create a new project
+    Given I run `middleman init MY_PROJECT`
+    Then the exit status should be 0
+    When I cd to "MY_PROJECT"
+    Then the following files should exist:
+      | config.rb                                     |
+      | source/index.html.erb                         |
+      | source/images/background.png                  |
+      | source/images/middleman.png                   |
+      | source/layouts/layout.erb                     |
+      | source/javascripts/all.js                     |
+      | source/stylesheets/all.css.scss               |
+      | source/stylesheets/_animate.scss              |
+      | source/stylesheets/_normalize.scss            |
+      
+  Scenario: Create a new project (alias i)
+    When I run `middleman i MY_PROJECT`
+    Then a directory named "MY_PROJECT" should exist
+    
+  Scenario: Create a new project (alias i)
+    When I run `middleman new MY_PROJECT`
+    Then a directory named "MY_PROJECT" should exist
+  
+  Scenario: Create a new project (alias i)
+    When I run `middleman n MY_PROJECT`
+    Then a directory named "MY_PROJECT" should exist
+    
+  Scenario: Create a new project with Rack
+    When I run `middleman init MY_PROJECT --rack`
+    Then a directory named "MY_PROJECT" should exist
+    When I cd to "MY_PROJECT"
+    Then the following files should exist:
+      | config.rb                                     |
+      | config.ru                                     |
+    Then the following files should not exist:
+      | Gemfile                                       |
+    
+  Scenario: Create a new project with Bundler
+    When I run `middleman init MY_PROJECT --bundler`
+    Then a directory named "MY_PROJECT" should exist
+    When I cd to "MY_PROJECT"
+    Then the following files should exist:
+      | config.rb                                     |
+      | Gemfile                                       |
+    Then the following files should not exist:  
+      | config.ru                                     |
+      
+  Scenario: Create a new HTML5 project
+    When I run `middleman init MY_PROJECT --template=html5`
+    Then a directory named "MY_PROJECT" should exist
+    When I cd to "MY_PROJECT"
+    Then the following files should exist:
+      | config.rb                                     |
+    Then the following files should not exist:
+      | config.ru                                     |
+      | Gemfile                                       |
+    Then a directory named "source" should exist
+    When I cd to "source"
+    Then the following files should exist:
+      | index.html                                    |
+      | humans.txt                                    |
+      | js/script.js                                  |
+      
+  Scenario: Create a new HTML5 project with Rack
+    When I run `middleman init MY_PROJECT --rack --template=html5`
+    Then a directory named "MY_PROJECT" should exist
+    When I cd to "MY_PROJECT"
+    Then the following files should exist:
+      | config.rb                                     |
+      | config.ru                                     |
+    Then the following files should not exist:
+      | Gemfile                                       |
+    
+  Scenario: Create a new HTML5 project with Bundler
+    When I run `middleman init MY_PROJECT --bundler --template=html5`
+    Then a directory named "MY_PROJECT" should exist
+    When I cd to "MY_PROJECT"
+    Then the following files should exist:
+      | config.rb                                     |
+      | Gemfile                                       |
+    Then the following files should not exist:  
+      | config.ru                                     |
+      
+  Scenario: Create a new Mobile HTML5 project
+    When I run `middleman init MY_PROJECT --template=mobile`
+    Then a directory named "MY_PROJECT" should exist
+    When I cd to "MY_PROJECT"
+    Then the following files should exist:
+      | config.rb                                     |
+    Then the following files should not exist:
+      | config.ru                                     |
+      | Gemfile                                       |
+    Then a directory named "source" should exist
+    When I cd to "source"
+    Then the following files should exist:
+      | index.html                                    |
+      | humans.txt                                    |
+      | js/libs/respond.min.js                        |
+      
+  Scenario: Create a new Mobile HTML5 project with Rack
+    When I run `middleman init MY_PROJECT --rack --template=mobile`
+    Then a directory named "MY_PROJECT" should exist
+    When I cd to "MY_PROJECT"
+    Then the following files should exist:
+      | config.rb                                     |
+      | config.ru                                     |
+    Then the following files should not exist:
+      | Gemfile                                       |
+    
+  Scenario: Create a new Mobile HTML5 project with Bundler
+    When I run `middleman init MY_PROJECT --bundler --template=mobile`
+    Then a directory named "MY_PROJECT" should exist
+    When I cd to "MY_PROJECT"
+    Then the following files should exist:
+      | config.rb                                     |
+      | Gemfile                                       |
+    Then the following files should not exist:  
+      | config.ru                                     |

data/features/content_for.feature

@@ -0,0 +1,6 @@
+Feature: Support content_for and yield_content helpers
+
+  Scenario: content_for works as expected in erb
+    Given the Server is running at "content-for-app"
+    When I go to "/content_for_erb.html"
+    Then I should see "In Layout: I am the yielded content erb"

data/features/current_page_request_path_backwards.feature

@@ -0,0 +1,6 @@
+Feature: Support old request.path object used by many extensions
+  
+  Scenario: Viewing the root path
+    Given the Server is running at "current-page-app"
+    When I go to "/request-path.html"
+    Then I should see "true"

data/features/custom_layout_engines.feature

@@ -0,0 +1,8 @@
+Feature: Custom Layout Engine
+
+  Scenario: Checking built folder for content
+    Given a successfully built app at "custom-layout-app"
+    When I cd to "build"
+    Then the following files should exist:
+      | index.html                                    |
+    And the file "index.html" should contain "Comment in layout"

data/features/custom_layouts.feature

@@ -0,0 +1,44 @@
+Feature: Custom layouts
+  In order easily switch between relative and absolute paths
+  
+  Scenario: Using custom :layout attribute
+    Given page "/custom-layout.html" has layout "custom"
+    And the Server is running at "custom-layout-app2"
+    When I go to "/custom-layout.html"
+    Then I should see "Custom Layout"
+    
+  Scenario: Using with_layout block
+    Given "/custom-layout.html" with_layout block has layout "custom"
+    And the Server is running at "custom-layout-app2"
+    When I go to "/custom-layout.html"
+    Then I should see "Custom Layout"
+    
+  Scenario: Using custom :layout attribute with folders
+    Given page "/custom-layout-dir/" has layout "custom"
+    And the Server is running at "custom-layout-app2"
+    When I go to "/custom-layout-dir"
+    Then I should see "Custom Layout"
+    When I go to "/custom-layout-dir/"
+    Then I should see "Custom Layout"
+    When I go to "/custom-layout-dir/index.html"
+    Then I should see "Custom Layout"
+    
+  Scenario: Using custom :layout attribute with folders
+    Given page "/custom-layout-dir" has layout "custom"
+    And the Server is running at "custom-layout-app2"
+    When I go to "/custom-layout-dir"
+    Then I should see "Custom Layout"
+    When I go to "/custom-layout-dir/"
+    Then I should see "Custom Layout"
+    When I go to "/custom-layout-dir/index.html"
+    Then I should see "Custom Layout"
+    
+  Scenario: Using custom :layout attribute with folders
+    Given page "/custom-layout-dir/index.html" has layout "custom"
+    And the Server is running at "custom-layout-app2"
+    When I go to "/custom-layout-dir"
+    Then I should see "Custom Layout"
+    When I go to "/custom-layout-dir/"
+    Then I should see "Custom Layout"
+    When I go to "/custom-layout-dir/index.html"
+    Then I should see "Custom Layout"

data/features/data.feature

@@ -0,0 +1,22 @@
+Feature: Local Data API
+  In order to abstract content from structure
+
+  Scenario: Rendering html
+    Given the Server is running at "basic-data-app"
+    When I go to "/data.html"
+    Then I should see "One:Two"
+  
+  Scenario: Rendering json
+    Given the Server is running at "basic-data-app"
+    When I go to "/data3.html"
+    Then I should see "One:Two"
+    
+  Scenario: Using data in config.rb
+    Given the Server is running at "data-app"
+    When I go to "/test1.html"
+    Then I should see "Welcome"
+    
+  Scenario: Using data2 in config.rb
+    Given the Server is running at "data-app"
+    When I go to "/test2.html"
+    Then I should see "Welcome"