A static site generator
A static site generator, powers marcyes.com
You run bang from the command line:
$ bang command --project-dir=...
A bang site can have any folder structure and bang will check each folder for a markdown (extension .md) file, if it finds one named index.md it will not treat it like a blog post but just compile the folder to an index.html file. If it finds a markdown file with any other name, then it is considered a blog post with the file’s name being the title. So, it basically uses this structure for its posts, so if you have this file structure:
project-dir/ input/ 2014/ 001-this-is-the-slug/ This is the title of the blog post.md
It would compile down to a blog post with a title This is the title of the blog post available at the uri:
Any other files (images or whatnot) will just be copied over to their respective locations.
Your project directory is where all the magic happens. It has to contain a few folders:
This is where all your blog posts go.
This is where all your Jinja templates go, they are used to compile your blog posts to their final form.
This is the default output directory when the compile command is used with no --output-dir option set.
Use this to compile your project-dir/input directory to the final form in the output-dir directory.
Compile your site using the default output directory:
$ bang compile --project-dir=...
That will place the compiled output to project-dir/output, you can also move the output directory to another location:
$ bang compile --project-dir=... --output-dir=...
Use this to fire up a local server so you can see your compiled site. You can set the port with the --port flag.
$ bang server --project-dir=... --port=8000
This is designed to be used on the remote server that will host your site in a cron job, it will try and pull down the code using a git repo, if there are changes, then it will compile the new changes, since it is run in cron, you should include the full path:
$ /usr/local/bin/bang watch --project-dir=...
pip install bangtext
The folders should allow tagging with #hashtags
a project should be able to include a plugins directory (python module) that will allow customization, there should be events added around all the major things during execution (eg, a post_compiled event, a pre_compile event) that the plugins module the user adds can hook into.
There should be a few default plugins, a sitemap plugin that takes the posts_compiled event and creates a sitemap.xml file, and an rss plugin that also takes posts_compiled and produces an rss feed of the last 10 posts or something.