I mentioned this in a previous post, but I don't believe I gave enough details to make what I was thinking clear. I'll try to explain here in more detail.
Blog and CMS software such as wordpress is great for getting a site up and running and managing content. However there are a few things I don't like about wordpress (and similar software). 1) Page content is often generated every page view, taking more time and taxing server resources. There are plugins that provide caching but then you need to trust 3rd party code, and I've definitely run into problems setting it up and using it all consistently. 2) Many 3rd party plugins and themes buggy, slow, and/or vulnerable to exploitation. Wordpress itself is vulnerable to some clever clickjacking which can be used to install and enable a 3rd party plugin with a known exploit, which can then be further exploited to get a shell on the server. 3) Using wordpress requires that you have access to database software and PHP. Although these things are fairly easy to get, not everybody has or wants them. You can support more users, more securely, with a static website (or at least mostly html files). There are a few site generators out already (Jekyll and Hakyll to name a few), but they are a bit clunky in my opinion. I've tried both and just barely got my site working before I got frustrated and stopped trying to use them. This is where Leo can help I think. The main problem with a static site generator is deciding how to organize data while retaining flexibility. Since they are both based on files and not clone-able nodes, they are clunky. I'm thinking Leo's structure will benefit this type of application greatly. To give you an idea of what I'm picturing on the grand scale, I would like Leo to produce a site like http://greynode.org using an outline similar to http://i.imgur.com/zaqcI.png >From what I can tell there are maybe 4 main elements that would be different. You would have: 1. Data Nodes - These are nodes where you would organize your page content, blog posts, watever 2. Template Nodes - These are nodes where you would store HTML required to generate portions of pages, of the site, and the site as a whole 3. Media Nodes - These nodes would represent various media the site requires like CSS and images. These particular nodes I'm feeling iffy about. 4. Generator Nodes - These would consist of logic that would take Data Nodes + Template Nodes + Media and produce the resulting website I hope this gives a clearer idea of what I was picturing. --Jeff Aigner -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
