> Thanks for your responses.  I must admit I was hoping to hear that
> others had solved similar problems with a more robust solution.  I was
> starting to wonder if what I wanted to do was possible, and it sounds
> like it would be very difficult if even possible.

Well, what you'll got now actually is the most robust solution if you
ask me. Look at all the blogging sites out there (like mine at
http://chillenious.wordpress.com/): they typically provides a couple
of themes (akin to the templates I suggested) and for the more
advanced users, they provide *some* options of tweaking the CSS.
There's probably a lot to learn from how they do it, and it looks that
letting users only upload additions to a certain theme rather than
changing it as a big blob might be a smart idea.

> I've already designed the site with very clean and simple html with
> all layout/look/feel done in CSS.  So going that direction will not be
> difficult, except that getting the client up to speed on CSS seems
> like a daunting task.

But what would be more difficult? Asking your client to learn a
template language (like when you would have done it in JSP or such) or
to learn CSS. CSS is argueably easier to learn - at least for non
programmers I expect - and deals with *just* the layout.

> If I was to allow the client to customize and upload new CSS files,
> how would you suggest this be done?  Where would the CSS files be
> saved and how would the app know where to look for them?  How would
> the override the CSS files that are within the WAR file?

I would upload and serve those CSS files from either some special
directory you configure in your web server separately, or - more
expensive - serve it from a database. The latter is easy because you
don't need to do the extra configuration when deploying your
application. The first scales much better.

> Also, as far as static content management goes, I'm thinking of
> putting all the static stuff into the properties files and using
> labels for it.  Thus creating a very simple and cheap CMS.  Then it
> would be simply a matter of editing the properties files and uploading
> them.  But again, how would that work?  What would I do so that the
> app would read the uploaded files instead of the ones in the WAR?

Get them from a database. Don't know the details from the top of my
head, my it's easy to configure Wicket to look for properties files
from other locations - including a database - on top of the default
lookup.

Eelco

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to