> I **know already** that "Leo can do this" - but that just means **you** can
> do this in Leo+Python, and I'm not going with "cloned snippets for
> templating" which would have been my approach a few weeks ago.
>
> I have a real project starting this week, but I'll be too busy resurrecting
> the HTML/CSS segments of my poor old brain to start learning Python
If you scroll down on this page
http://wiki.python.org/moin/WebFrameworks
you come to "Basic Frameworks Providing Templating"
I'm not familiar with any of them, I maintain one site using Leo +
Genshi, one of the Python templating systems, but you do need to supply
some python glue for that approach.
Cheers -Terry
> I'm looking to locally generate static HTML+CSS - maybe some javascript for
> stuff like analytics but that's all - that can be uploaded to a
> plain-vanilla Apache host.
>
> I realize that you (sing + most of you plural) wouldn't do things this way,
> but just in case these details jogs anyone else's memory.
I don't think that's a bad way to do small sites. I've done 3-4 that
way including the one currently working with Leo + Genshi, but there's
ad hoc Python in the mix, which seems like it might not work for you.
Although the Python tutorial's not bad once you get in to it ;-)
Cheers -Terry
A little indirect but here is one idea: run bloxsom locally, capture
the result with httrack and then sync to web host. Httrack can be run
in a refresh mode that only captures changes, which in turn means you
can use a syncing tool that only bothers itself with new and changed
files.
Substitute whatever you like for bloxsom, such as Leo's own rst export.
[1] http://muli.cc/, http://pyblosxom.bluesock.org/
[2] http://www.httrack.com/
--
-matt
and substitute pyblosxom for httrack!
http://pyblosxom.bluesock.org/1.5/deploy_staticrendering.html
(So yes, I haven't used it for a very long time. I've always been
enamoured of the ideals it comes from though.)
--
-matt
the second link is for a python-blosxom spin off. I included the
original as well so as to be faithful to the source. My apologies for
the confusion.
--
-matt
> best to keep my focus on python (or maybe haskell due to my interest in pandoc ATM).the second link is for a python-blosxom spin off. I included the original as well so as to be faithful to the source. My apologies for the confusion.
Yes that's correct. If you take it for a spin or two I'm interested in
your thoughts on the experience, regardless of whether it finds a
place in your toolbox or not.
cheers,
--
-matt