Ackro

Ackro aims to be a controller for (multiple) Tumblelogs Tumblogs or whatever, controlled entirely from commandline. Contents are simple to add in different ways, by mail (You need procmail), by $EDITOR or simple by commandline.

About

To add contents components are used. A component uses some field declarations to add simple contents to a post, for complex operations e.g. image creation a plugin may attached to a field. The basic component and each field can include CSS style definitions to make it glimmer.

Ackro can handle multiple Tumblogs, each of them are defined by a config file. In this file the output variants, basic content nodes and common settings are defined. In fact Ackro is used to create a static bunch of web pages, but its not that complicated to use it in other ways. There are 4 ways to publish contents yet: HTML, XML, RSS, and Plain. Other variants like pdf are imaginable.

Features

• Pure Ruby!
• Highly customizable, easy to add a publisher, plugins and components.
• Config files (tlogrc and components) are editable by non Ruby programmers and smart non programmers.
• Prototype support.
• No features required by the webserver, sync and upload! (but you dont need a webserver if you want to use it local)
• Add a component in 1 minute
• CSS is autogenerated by style definitions from tlogrc and components.
• Multible stylesheet support for more complex layouts.
• Permalinks, links to plugins, components and YAML sources (for sharing)
• View, add, edit, delete contents from commandline.

The Repository

The local repository has two levels. The top-level and a static level. For syncing you need to define a TITLE. On sync, all contents are published to the toplevel and to the static directory in TITLE. Targets for permalinks goes to the htdocs/static/TITLE.