jondaley wrote:It sounds like a good idea. The thing I've never been sure about is you can't do all of the hundred or so templates that we have in this format, can you? And if you can't do that, what good is having some of the templates done? Or would a blog host just install the "zen/css" templates and not use the rest?
Zen' garden don't have templates available par-se. Basically, what they tried to show [when css was in its infancy] was just how powerful a framework in terms of styling it was.
Essentially, when you land on there main page or when you apply a 'Style' from any of the links, the html never changes, only the css/images are changed.
obviously with the diverse range of templates that LT has and the fact that a stricter html framework wasn't applied [Although I do remember reading in the wiki that it was requested - maybe Oscar already had ideas along these lines??] .In that respect then it would be the choice of the host but certain existing templates would have to be either edited [quite a lot of them can be] and some removed as incompatible or used as strictly 'Custom' templates.
thats not to say that if someone was capable and wanted to make there own more advanced template - that they couldn't but it would be for them alone which is part of the unique aspect of LIfetypes template system as you know. My thoughts are for the in-experienced no html knowledge user, who are essentially restricted to what we or the community give them. Here I'm looking at an option where they can safely style there own template set, allow them to have some control over the look and feel of there blog.
I think thats where Reto was going when he suggested the Yaml system which is essentially a css based template system, though I have looked at it and on another system [a cms that Lifetype actually integrates into - I think I mentioned it a while ago] and it is kinda complicated to use. I'm thinking along the lines of something simple - literally a point, click and save and your done type approach....
So here we are looking at the ability to edit a css file directly but also disallowing any js or php or messing to happen in there, allow the ability to upload images in the .jpg, .gif or .png format to an images folder which can be sourced as background/s in the css and then saved for the individual user.
how difficult this would be to implement I dunno - I'm stlll playing with it and ideas but I have some of the ground work done and it seems to work fine. Hopefully I'll get mor etime soon to be able to look at it a bit more again....