Fredrik Lundh wrote: >Tim Parkin wrote: > > > >>It sounds very similar to what we have already built!! What we have also >>parses yaml files, rest files, inline rest content, has special >>renderers for navigation and breadcrumbs and handles cacheing of built >>data to speed generation. >> >> > >except that it isn't: you're talking about a modernized version of >the current HT2HTML/make system, we're talking about a purely >wiki-driven system. > > Fred, It's not a updated ht2html, just as it's not a web framework and it's also not a database backed content management system. It is what it is, text files with content on disk that get delivered as flat css/xhtml files (via a simple xml based templating system) and stored in a subversion repository.
The way people edit content can be via any tool capable of editing text files. That includes, but is not limited to, textareas (via a wiki if you will) or gedit or vim or notepad. I would like your help, if you are willing, to suggest ways of parsing wiki markup into valid, semantic html that can be used on the website. I would also like you help in integrating the documentation into the website. If you want to help, send me an email, if you don't want to help but would like to continue the discussion, I'm happy to do so in private and then we can both come back and post our conclusions on the mailing list. Thanks Tim Parkin -- http://mail.python.org/mailman/listinfo/python-list
