>
> If you ask me, I don't think that template system would actually work.
> In my opinion it underestimate the complexity of the process. Setting
> up Drupal, GlassFish, Gallery2 or RedMine is fairly simple for a
> person, but it can be basically be impossible to do with a plain
> template.
So the template needs a different format to the config. I've already
explained how you could get around the vserver number and if bits and bobs
need filling in, why can't there be a syntax for specifying that in the
template code?
For example a value could be $ASK{"Which information source is responsible
for PHP?",infosource}
Whatever parses the template at the admin end would know to give the user a
choice of information sources and fill that value with it. The same could be
done for paths (using "path" instead of "infosource").
It's very much going back to the idea of wizards, but making them so people
can edit, customise and publish them without waiting for them to be brought
in via the main release system. You don't need to ask the user's shoe size
to get the bare minimum information down. Document root (taken care of
already) and information source. Done. They can fiddle the nuts off it if
they want to later on. You're worrying about obscure cases too much.
What I'm suggesting isn't a complete replacement to the tutorial system --
people still need to know how information sources work and set them up --
but something to replace all the repetative rule-adding.
It's *still* a million times simpler to give people a block of text to paste
in and telling them to edit the paths to customise things. And it's still
handy for support.
There have been several calls for a "click it and it installs" style
template. I think the closest you could ever get to this is by having a
browsable template directory *inside* the admin. It would connect to the
real website and show the latest templates/wizards. It would need to be
inside the admin to automate because the remote site can't know where the
users admin is or even if it's running at that time.
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
