staticmatic 0.9.5 → 0.10.0

data/website/src/helpers/application_helper.rb

@@ -1,5 +0,0 @@
-module ApplicationHelper
-  def greet(name)
-    "Hello, #{name}"
-  end
-end

data/website/src/layouts/application.haml

@@ -1,43 +0,0 @@
-!!!
-%html{ :xmlns => "http://www.w3.org/1999/xhtml", :lang => "en", 'xml:lang' => "en" }
-  %head
-    %meta{"http-equiv"=>"Content-Type", :content=>"text/html; charset=utf-8"}
-    %title StaticMatic
-    = stylesheets
-    = stylesheets :reset, :application, :media => :screen
-  %body
-    #container
-      #header
-        .bycurve21= link(img("bycurve21.gif"), "http://www.curve21.com")
-        .title StaticMatic
-
-      #menu
-
-        %ul
-          %li= link "Home", "/"
-          %li= link "Download"
-          %li= link "How to use"
-          %li= link "FAQ"
-          %li= link "Community", "http://groups.google.co.uk/group/staticmatic"
-          %li= link "Helper Central", "helper_central/"
-          %li= link "Development", "http://rubyforge.org/projects/staticmatic"
-      #content_wrapper
-        #side
-          #news= partial("news")
-
-        #content
-          = yield
-      
-      #footer
-        %p 
-          Made with StaticMatic
-          = StaticMatic::VERSION::STRING
-          \, Hosted by 
-          = link "RubyForge", "http://rubyforge.org"
-      
-      %script{:src => "http://www.google-analytics.com/urchin.js", :type => "text/javascript"}
-        _hamlspace = "";
-      %script{:type => "text/javascript"}
-        _uacct = "UA-775359-8";
-        urchinTracker();
-      

data/website/src/layouts/test.haml

@@ -1,4 +0,0 @@
-!!!
-%h1 Blah
-
-= yield

data/website/src/pages/_qa.haml

@@ -1,2 +0,0 @@
-%h3= question
-%p= answer

data/website/src/pages/download.haml

@@ -1,15 +0,0 @@
-%h1 Download
-
-%p The simplest way to get StaticMatic is via RubyGems:
-
-.code gem install staticmatic
-
-%h3 Source Code
-
-%p 
-  You can get the source code from 
-  = link "RubyForge", "http://rubyforge.org/projects/staticmatic/"
-  \:
-  
-.code svn checkout svn://rubyforge.org/var/svn/staticmatic/trunk staticmatic
-

data/website/src/pages/faq.haml

@@ -1,8 +0,0 @@
-%h1 FAQ
-
-=partial('qa', :locals => { :question => 'I hate Haml.  Can I use a different template language?', :answer => 'No. At least not at the moment.  Haml is perfect for our needs so we\'ve had no reason to investigate using other languages.  However, StaticMatic is open source so patches are always welcome.' })
-=partial('qa', :locals => { :question => 'I found a bug.  How do I report it?', :answer => 'At the StaticMatic <a href="http://rubyforge.org/tracker/?func=browse&amp;group_id=3712&amp;atid=14306">Bug Tracker</a>.' })
-=partial('qa', :locals => { :question => 'I\'d like a new feature.  How do I request it?', :answer => 'At the StaticMatic <a href="http://rubyforge.org/tracker/?atid=14309&amp;group_id=3712&amp;func=browse">Feature Request Tracker</a>.' })
-=partial('qa', :locals => { :question => 'I\'ve got a patch for you.  How do I submit it?', :answer => 'At the StaticMatic <a href="http://rubyforge.org/tracker/?atid=14308&amp;group_id=3712&amp;func=browse">Patch Tracker</a>.' })
-=partial('qa', :locals => { :question => 'How do I find neat helpers that other developers have written?', :answer => 'Go to the StaticMatic <a href="helper_central/">Helper Central</a>.' })
-=partial('qa', :locals => { :question => 'I\'ve got a neat helper to share with the world.  How do I do it?', :answer => 'Post on the <a href="http://groups.google.co.uk/group/staticmatic">StaticMatic Google Group</a> requesting it be added to the StaticMatic <a href="helper_central/">Helper Central</a>.' })

data/website/src/pages/helper_central/_helper.haml

@@ -1,7 +0,0 @@
-%tr{:valign => :top}
-  %td
-    %strong= title
-  %td= description
-  %td= author
-  %td
-    = link "Download", download_link, :id => id, :class => 'download'

data/website/src/pages/helper_central/index.haml

@@ -1,21 +0,0 @@
-%h1 Helper Central
-
-%p
-  This is a place where nifty helpers not accepted into core can be found.  
-  %span.highlight Use them at your own risk.  StaticMatic core developers are not responsible for these helpers or their results.
-  %br
-  %br
-  Helpers are listed in alphabetical order.  
-
-%table{:border => '0'}
-  %tr
-    %th Name
-    %th Description
-    %th Author
-    %th Download
-  =partial('helper', :locals => { :title => 'Blueprint Css', :author => 'Brent Beardsley', :description => 'Easily include blueprint css framework files and plugins', :download_link => 'http://staticmatic.rubyforge.org/svn/trunk/contrib/helpers/blueprintcss_helper.rb', :id => 'blueprintcss_helper' })
-  =partial('helper', :locals => { :title => 'Google Analytics', :author => 'Brent Beardsley', :description => 'Easily include google analytics javascript code using http or https', :download_link => 'http://staticmatic.rubyforge.org/svn/trunk/contrib/helpers/google_analytics_helper.rb', :id => 'google_analytics_helper' })
-  =partial('helper', :locals => { :title => 'Menubar', :author => 'Brent Beardsley', :description => 'Easily create a menubar using an unordered list', :download_link => 'http://staticmatic.rubyforge.org/svn/trunk/contrib/helpers/menubar_helper.rb', :id => 'menubar_helper' })
-  =partial('helper', :locals => { :title => 'Navigation', :author => 'Andrew Neil', :description => 'Easily create breadcrumbs, sitemaps, and menus.', :download_link => 'http://staticmatic.rubyforge.org/svn/trunk/contrib/helpers/navigation_helper.rb', :id => 'navigation_helper' })
-  =partial('helper', :locals => { :title => 'Rss List', :author => 'Brent Beardsley', :description => 'Easily create an unordered list from an rss feed. Special helpers for delicious, flickr, ebay, magnolia, and twitter.', :download_link => 'http://staticmatic.rubyforge.org/svn/trunk/contrib/helpers/rss_list_helper.rb', :id => 'rss_list_helper' })
-         

data/website/src/pages/how_to_use.haml

@@ -1,270 +0,0 @@
-%h1 How to Use
-
-%p StaticMatic is very easy to work with.  It aims to provide just the tools you need and not get in your way.
-
-%ul 
-  %li= link "Developing a site", "#developing"
-  %li= link "Configuration", "#configuration"
-  %li
-    = link "Templates", "#templates"
-    %ul 
-      %li= link "Layouts", "#layouts"
-      %li= link "Helpers", "#helpers"
-      %li= link "Partials", "#partials"
-  
-%h2{:id => 'developing'} Developing a site with StaticMatic
-
-%h3 Setting up a site
-
-%p The first thing to do with a StaticMatic site is to set up the folders and files ready for use.  A simple command will create everything you need to get started:
-
-.code staticmatic setup my_site
-
-%p This will set up a number of directories:
-
-%ul
-  %li site/  - contains your static site and any assets such as images or javascript files
-  %li 
-    src/  - where you'll work on your templates
-    %ul
-      %li
-        helpers/ - contains any helpers you want to use in your website
-        (write your own or grab some from
-        = link_to('Helper Central', '/helper_central/') + ')'
-      %li layouts/ - contains templates that 'wrap' your main content pages
-      %li pages/ - contains the actual pages of content
-      %li partials/ - contains any "partial pages" that can be reused in other pages or layouts
-      %li 
-        stylesheets/ - contains any 
-        = link 'Sass', 'http://haml.hamptoncatlin.com/docs/sass'
-        stylesheets you want to create
-
-%h3 Previewing your site
-
-%p When you're ready to start working on your site, you can fire up the preview server to see your changes:
-
-.code staticmatic preview my_site
-
-%p 
-  This will start a web server on port 3000.  Point your web browser to 
-  = link "http://localhost:3000", "http://localhost:3000"
-  to see your site.
-
-%h3 Building your site
-
-%p When you're happy with the website, you can tell StaticMatic to generate the HTML pages:
-
-.code staticmatic build my_site
-
-%h2{:id => 'configuration'} Configuration
-
-%p
-  You can put a file called configuration.rb in your staticmatic project's basedir/src directory.
-  In this file, you can set configuration settings or whatever else since it's just a 
-  ruby file.
-
-%h3 configuration.preview_server_port
-
-%p
-  The default is 3000.
-
-%h3 configuration.preview_server_host
-
-%p
-  The default is localhost.
-
-%h3 configuration.use_extensions_for_page_links
-
-%p
-  The default is true.  When false .html and index.html will be stripped off
-  urls generated by the link tag helper.
-
-%h3 configuration.sass_options
-
-%p
-  Default is an empty hash.  You can specify any options that 
-  = link 'Sass', 'http://haml.hamptoncatlin.com/docs/sass'
-  can take like :style => :compact
-
-%h2{:id => 'templates'} Templates
-
-%p 
-  %em
-    For information on how to use Haml itself, please check out the 
-    = link("Haml website", "http://haml.hamptoncatlin.com/docs/haml") + "."
-  
-%h3{:id => 'layouts'} Layouts
-
-%p 
-  As with web frameworks like
-  = link("Ruby on Rails", "http://www.rubyonrails.com") + ","
-  StaticMatic uses layouts to 'wrap' up the content contained within page templates.
-
-%p A layout typically contains the header and footer code for a page - code that is common to all pages on the site.
-
-%p The only thing a layout *must* contain is a line that tells StaticMatic where to put the content:
-
-.code = yield
-
-%p By default, StaticMatic will look for a template named 'application.haml'.  If you have a page that needs to use a different layout, this can be specified in the page itself:
-
-%em contact_us.haml:
-.code - @layout = "contact"
-
-%p The above code would tell StaticMatic to use the layout called 'contact.haml' when building and previewing the 'contact_us' page.
-
-
-%h3{:id => 'helpers'} Helpers
-
-%p StaticMatic provides a number of 'helpers' on top of those in Haml to handle common code and reduce code.
-%p
-  %em
-    Additionally you can write your own helpers and put them in your 
-    staticmatic src/helpers directory.  You can checkout the
-    = link_to 'Helper Central', '/helper_central/'
-    for some helpers that have already been written by others that 
-    you can drop in your helper directory.
-
-%h4 Links
-
-%p
-  'link' ('link_to' works too for you 
-  = link_to 'Rails', 'http://www.rubyonrails.com/'
-  types) can automatically set up hyperlinks for you:
-
-.code = link "Contact Us"
-
-produces:
-
-.code <a href="contact_us.html">Contact Us</a>"
-
-%p It is also possible to specify a relative path in your url:
-
-.code = link "../Contact Us"
-
-produces:
-
-.code <a href="../contact_us.html">Contact Us</a>"
-
-%p You can also specify a URL:
-
-.code = link "StaticMatic", "http://staticmatic.rubyforge.org"
-
-%h4 Images
-
-.code = img "me.jpg"
-produces:
-.code <img src="/images/me.jpg"/>
-
-%p It is also possible to specify a relative path in your url:
-
-.code = img "../me.jpg"
-produces:
-.code <img src="../me.jpg"/>
-
-%h4 Stylesheets
-
-.code = stylesheets
-
-%p
-  This will automatically insert links to any 
-  = link 'Sass', 'http://haml.hamptoncatlin.com/docs/sass'
-  stylesheets in your site source.  
-
-  It will also link up any static stylesheets in your site/stylesheets/ directory
-
-%p
-  You can also specify the files and the order explicitly along with setting attributes:
-
-.code = stylesheets :reset, :application, :media => :screen
-
-produces
-
-.code 
-  <link href="stylesheets/reset.css" media="screen" rel="stylesheet"/>
-  %br
-  <link href="stylesheets/application.css" media="screen" rel="stylesheet"/>
-
-%h4 Javascript
-
-.code = javascripts('test', :other)
-produces:
-.code
-  <script language="javascript" src="/javascripts/test.js" type="text/javascript"></script>
-  %br
-  <script language="javascript" src="/javascripts/other.js" type="text/javascript"></script>
-
-%h4 Current page
-
-%p
-  It can be very useful to know what page you're on in your layout and helpers
-  (ie: setting selected style on a menu item).
-
-For the page src/pages/index.html
-.code = current_page # => "/index.html"
-%br
-For the page src/pages/subdirectory/other.html
-.code = current_page # => "/subdirectory/other.html"
-
-%h4 urlify
-
-%p Will convert a string to be usable in a url
-
-.code
-  \= urlify("We love Haml") # => "we_love_haml"
-  %br
-  \= urlify("Elf & Ham") # => "elf_and_ham"
-  %br
-  \= urlify("Stephen's gem") # => "stephens_gem"
-  %br
-  \= urlify("Test/Link") # => "testlink"
-
-%h4 text_area
-
-%p Generates a text area field
-
-.code = text_area 'myname', 'myvalue'
-produces:
-.code <textarea id="myname" name="myname">myvalue</textarea>
-
-%h4 text_field
-
-%p Generates a text input field
-
-.code = text_field('first_name', 'bob')
-produces:
-.code <input name="first_name" type="text" value="bob"/>
-
-
-%h3{:id => 'partials'} Partials
-
-%p 
-  As with web frameworks like
-  = link("Ruby on Rails", "http://www.rubyonrails.com") + ","
-  StaticMatic uses partials to keep things 
-  = link('DRY', 'http://en.wikipedia.org/wiki/DRY') + "."
-
-.code = partial('mypartial')
-
-%p
-  This will first look in the current page/partial's directory for a file called _mypartial.haml.
-  If not found there it will look for src/partials/mypartial.haml.
-
-%h4 Specify the partial's local variables
-
-.code = partial('mypartial', :locals => { :title => 'My Title' })
-  
-%p
-  This will locate the partial file as in the previous example above but now passes in a local variable called
-  %em title
-  that can be used in the partial like so:
-
-.code %h1 title
-
-%h4 Specify the partial's directory
-
-.code = partial('shared/mypartial')
-
-%p
-  This will look for the file src/pages/shared/_mypartial.haml first.
-  If not found there it will look for src/partials/mypartial.haml.

data/website/src/pages/index.haml

@@ -1,27 +0,0 @@
-%h1 Static websites, the modern way
-
-%p 
-  Web developers are used to using dynamic and frameworks like
-  = link "Ruby on Rails", "http://www.rubyonrails.com"
-  to develop applications. When it comes to working with static, non-dynamic websites it can seem like stepping back in time.
-
-%h2 You'd like to
-
-%ul
-  %li.highlight Replace over-featured, cumbersome Content Management Systems
-  %li.highlight Speed up your prototypes
-
-%h2 Meet StaticMatic
-
-.columns
-  .left_column
-    %em Concise and terse Haml Templating
-    = img "homepage-templating.jpg"
-
-  .right_column
-    %em Live preview server for development
-    = img "homepage-previewing.jpg"
-  
-%p 
-  %em Output full HTML pages
-  = img "homepage-build.jpg"

data/website/src/pages/releases/0_8_10.haml

@@ -1,22 +0,0 @@
-%h1 StaticMatic 0.8.10
-
-%h2 What's New
-
-%ul
-  %li [NEW] rails-like partials.  Partials can start with an underscore and live in the pages directory tree, old way still works (Brent Beardsley)
-  %li [NEW] added current_page helper for use in other helpers, layouts, or pages (Brent Beardsley)
-  %li [NEW] add src_dir, site_dir, and current_page attr_reader's on staticmatic class (Brent Beardsley)
-
-%h2 What's Fixed
-
-%ul
-  %li [FIX] img helper changes and tests (Jason Tennier)
-  %li [FIX] removed dependency on rails needing to be installed (Brent Beardsley)
-  %li [FIX] fixed preview bug where setting a layout in a page would cause it to be used even for pages that did not have a layout specified and should be using the default (Brent Beardsley)
-  %li [FIX] tag helper only outputs the attribute if it has a value (Brent Beardsley)
-  %li [FIX] renamed RakeFile to Rakefile so it'll work on non-windows boxes (Brent Beardsley)
-  %li [FIX] write tag helper attributes out in alphabetical order for consistency (Brent Beardsley)
-
-%p
-  See what changed in 
-  = link('0.8.8', '/releases/0_8_8.html')

data/website/src/pages/releases/0_8_4.haml

@@ -1,25 +0,0 @@
-%h1 StaticMatic 0.8.4 
-
-%p Don't be fooled by the small minor increments - there's loads of great stuff in the latest release:
-
-%h2 Sub-Directory Support
-%p Thanks to Brent Beardsley, you can now have as many directories as you like.  This should be considered 'beta' at the moment as there is likely to be issues with paths in the helpers, but try it out and we'll figure out the best solution.
-
-%h2 Partials! 
-%p 
-  Simply create a 'partials' directory in your src/ and you'll be able to do: 
-  .code partial("partial_name")
-
-%h2 Layouts based on directory
-%p Along with sub-directory support, you can also create layouts based on the sub-directory a template is in.  For example, if you have a 'projects' directory and would like it to render a different template, simply create 'projects.haml' in your layouts directory.
-
-%h2 Relative Stylesheet Linking
-%p 
-  You can now tell the stylesheet helper to use relative linking:
-  .code = stylesheets :relative => true
-  
-%p
-  %em Note that you may get issues with nested directories and relative stylesheets
-
-%h2 What's Next?
-%p The main things on the list are configuration and clearing up any bugs not yet sorted.  It'd also be great to start extending the test set more.