[ZWeb] volunteer for transforming ReST + templates into HTML

Darryl Cousins darryl at darrylcousins.net.nz
Wed Sep 20 08:15:51 EDT 2006


Hi All,

On Wed, 2006-09-20 at 11:47 +0200, Martijn Faassen wrote:
> Hey Darryl,
> 
> Darryl Cousins wrote:
> 
> > I've put everything you gave me `as is` into my little zpt/mod_python
> > application and this comes out:
> > 
> > http://zf.tfws.org.nz/
> 
> Great! Thank you very much!
> 
> > Notes:
> > 
> > Background logo image isn't lining up on firefox
> 
> cc-ing Tom Von Lahndorff. Darryl, which page does this occur on under 
> what circumstances? Which platform are you on?

Rain-check. I ran your template through `tidy`. Firefox1.5/Debian/Linux.

> > rest error on structure.html
> 
> Right, that should be easily fixed.
> 
> > 1. Directory and navigation structure for the site.
> 
> This needs to be generated; the toughest part of generating the layout. 
> I was hoping you'd take a look at it. :) We need to start generating 
> that based on our current structure, and instead of query (?foo=bar) 
> based links, just make them normal links. Base it on a structure of 
> nested directories, I'd say. Of course we don't have titles that way - 
> either we need a hack that lifts the title from the individual ReST 
> documents, or we need to provide the system with a list of titles for 
> the individual files somehow.

Yup,

index.html
- docs/
----index.html
----other-docs.html
- foo/
----index.html
----other-foo-docs.html
- other-home-directory-docs.html

Thats the structure we are aiming at?

I agree, titles we can lift from the rest text file.

> 
> > 2. How does 'upload to zope.org' work?
> 
> As to the ReST, I want to start maintaining that in the svn.zope.org 
> repository.

Yup. Some script could be run to synchronize the different components:

rest.svn.zope.org -> zf.www.rest --> zf.tfws.org.nz --> [wget?] -->
zope.org

Worst of the worse, we keep in touch and I syncronise it manually. Not a
big job.

And later, do it all with zope3   :-D  

> I'm trying to figure this out. On the near term, we may just upload all 
> of this into a plain zope on zope.org every time we make changes.

Unsure of meaning: `a plain zope`. ??

> I'm also investigating the use of Apache and just scp-ing it into an 
> Apache directory, but it appears the zope.org infrastructure needs work 
> to get there.

Keep me posted.

> Finally, eventually this should be converted into CMS content for one 
> CMS or another. That'll take a lot of hosting infrastructure work to get 
> done first, though.

Keep core/source data in directory/restfile then anything is possible.
Keep it simple. I think that any reasonable cms will be able to import
the structured data and generate a site using a given template.

Regards,
Darryl

> Regards,
> 
> Martijn



More information about the Zope-web mailing list