Every repository with this icon (
Every repository with this icon (
tree a11930a6b1216131e68b6374e677f643e50fdc67
parent 00dea1135cbd4b9fab8e17dec7bb01534986e29c
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Fri Jan 30 04:23:26 -0800 2009 | |
| |
LICENSE | Mon Apr 27 23:41:43 -0700 2009 | |
| |
README.markdown | Mon Apr 27 23:41:43 -0700 2009 | |
| |
Rakefile | Mon Apr 27 23:42:58 -0700 2009 | |
| |
VERSION.yml | Mon Apr 27 23:41:43 -0700 2009 | |
| |
bin/ | ||
| |
lib/ | ||
| |
staticmatic.gemspec | ||
| |
test/ | Thu Jan 01 14:31:25 -0800 2009 | |
| |
website/ | Thu Apr 02 03:08:55 -0700 2009 |
StaticMatic
For information on Haml & Sass please see haml.hamptoncatlin.com.
What's it all about?
CMS is overrated. A lot of the time, clients want us to do what we do best - well designed pages with structured, accessible and maintainable markup & styling.
CMSs are often perfect for this, but sometimes they can be restrictive and more cumbersome than just working with good ol' source code. At the same time we want our code to be structured, DRY and flexible.
Enter StaticMatic.
Usage
StaticMatic will set up a basic site structure for you with this command:
staticmatic setup <directory>
After this command you'll have the following files:
<directory>/
site/
images/
stylesheets/
javascripts/
src/
helpers/
layouts/
application.haml
pages/
index.haml
stylesheets/
application.sass
StaticMatic sets you up with a sample layout, stylesheet and page file. Once you've edited the pages and stylesheets, you can generate the static site:
staticmatic build <directory>
All of the pages are parsed and wrapped up in application.haml and put into the site directory.
Templates
StaticMatic adds a few helpers to the core Haml helpers:
= link 'Title', 'url'
= img 'my_image.jpg'








