Ola, I had not gotten so far as to consider building
support routines for persistent nav. I think it is useful
although I think in terms of returns the biggest win is
going to be simply cleaning up the existing markup and
documenting the classes that exist. certainly anything
that did persistent nav should work in conjunction with
theming...
I have been thinking
more about how to structure a theme package
so that it can be self contained, multiple themes can be
active on a given site, and it be reasonable for
designers to work with. (i.e. something that creates
a tarball of static html which is created from the master
templates and with the various widgets in it). I have
some of that done and have some thoughts about other issues
but its a long way from being concrete.
Mark, any help would be great. I will put what I have up
somewhere and we can start talking about more concrete things like class names and a basic design to start with.
I would love it if we could find some designers using
design tools (golive or dreamweaver or whatever it is
designers use now) and try
to make sure that what we do build does work well for
them.
You can look at the html demo pages and some
links on approaches to theming on my dev site
(note that I have ripped out a lot of the markup and made most of the dev site use css layout).
