Contents

# Schreihals

Everybody should be developing their own blogging engine for hackers, so here's mine.
Documentation is pretty minimal at the moment, so for now, how about a list of
overall design goals?

## Overall Design Goals

* Minimal code design.
* Author your blog through git, using Markdown and friends.
* Near-zero boilerplate code in your blog project. (It's all in the gem.)
* Theme support through gems.
* No static document generation. (Not interested, there are enough engines out there that do this.)
* HAML and SASS support out of the box.

## Usage

TODO: soon

## Stuff

Just a list of keywords I need to write about:

* Configuration
* Automatic `date` and `slug` recognition
* `status` attribute and drafts
* `disqus` and `disqus_identifier` attributes
* Using different post formats (markdown, textile, haml etc.)
* pages (= posts without dates)
* deployment (Heroku!)
* code highlighting
* `google_analytics_id` and `gauges_id`
* `footer`
* `link`
* `read_more`
* `schreihals create NAME`
* `schreihals post TITLE`
* `documents_store`, `documents_source`
* `twitter_id`
* cascading views

## Version History

### development

* Add `schreihals` executable. Use it to generate new Schreihals blogs (`schreihals create <name>`) and blog posts (`schreihals post <title>`).
* Removed dependency from `data_mapper` and added our own implementation.
* The contents of the `blog_description` configuration variable are now displayed at the top of the home page. The small footer at the bottom of all pages is now being populated through the `footer` variable.

### 0.0.2

* Fix various stupid bugs from the initial release, including the broken example app. Duh!
* When a post or page could not be found, we now display a proper 404 page (with correct status code.)

### 0.0.1

* Initial release.

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
schreihals-0.0.3	README.md