I have just landed a bunch of new code in the blogofile plugins branch
and the blogofile_blog master branch on github. Most of the code is
unit tests for the blogofile.main module, but the big functional
change is that the blogofile init command works differently now. It's
new syntax is:
blogofile init SRC_DIR [plugin]
Without a plugin, a bare site is created - just a _config.py file with
a few comments in it in the specified SRC_DIR. The user is free to
take things from there to create any kind of blogofile static site
they wish.
Of more interest to most users, I think, is initialization from a
plugin. This replaces initialization from the zip files in the
site_init directory. That's where the changes to blogofile_blog come
in. That plugin now contains (in addition to the _controllers,
_filters, and _templates/blog files that were already there) the
static and site template files from the
blogofile/site_init/simple_blog_html5/ directory. So,
blogofile init my_blog blog
will create an example blogofile site with a blog as its central
feature, and users can customize from there.
When 0.8 is released I intend to include blogofile_blog as a
dependency in blogofile, so both are installed automatically. For now
you need to clone both repos and do python setup.py develop (or your
favourite pip or easy_install version of that incantation) on both.
I haven't deleted blogofile/site_init yet, but it will go away before
the 0.8 release. If nothing else, the jinja2 template based site
that's in there should perhaps be turned into a plugin.
As for the warning - I'm seeing some weirdness when I build my
douglatornell.ca site with the latest blogofile_blog plugin installed.
The sidebar template from the plugin overrides the one from my site
source for some, but not all of the generated pages. I'm not sure if
this is a bug in blogofile, the plugin, or my site.
I'm giving this warning because I don't want to be the guy who breaks
your blog. On the other hand, I figure that if I put this code out now
there are potentially more eyes and brains on it to find that and the
other inevitable bugs. And it is
0.8.DEV, right?!
So, there it is, my first big step toward getting 0.8 released. I look
forward to feedback from those brave enough to test it :-)
Doug