Has anyone used traversal over a filesystem for non-static content? I'm thinking of putting my HTML content in files to get Git versioning and text-editor friendliness, so that each file would represent a URL but not be served as-is (you'd still put a site template around it and plug in metadata). Interspersed there would be true static files (e.g., images), although I'd like to have dynamic thumbnails. This suggests a traversal structure with objects for directories and different file types, like Kotti but with the nodes in the filesystem rather than in a database. (Without through-the-web editing.)
My primary issue is how to structure the files. In the past I've used email-message format, with the metadata in headers and the HTML body in the content, and a script that applies a template to generate a static HTML page. That's OK for editing, although if you view the raw file in a browser it formats all the metadata into a paragraph. Another approach I'm considering is to put the metadata in a TOML file per directory. That would allow for expansion and automatically parse data types, and be more human-readable than JSON, but it would separate the metadata from the content. Has anyone done anything similar? Also, have people used the Python thumbnail-management libraries? Is there a lightweight one you'd recommend? My past practice is to pregenerate the thumbnails as static files next to the originals, but I want to get away from that. -- Mike Orr <[email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
