Sha256: 2e670758db154b147a0aedb9e9287f3602cfd4f7d20730c46ad26f4866973acb
Contents?: true
Size: 1.64 KB
Versions: 1
Compression:
Stored size: 1.64 KB
Contents
= StaticMatic Managing static sites with [Haml & Sass](http://haml.hamptoncatlin.com). **Please Note:** StaticMatic is fresh out the oven. It has a limited feature set and is only really covering my immediate requirements. _However_, I am interested in getting feedback on the idea and code contributions are always welcome. == Introduction 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/ pages/ index.haml layouts/ application.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' == What's Next? * Multiple directories of content * Layouts based on directory of page template * Additional Helpers
Version data entries
1 entries across 1 versions & 1 rubygems
Version | Path |
---|---|
staticmatic-0.0.1 | README |