Dave wrote:
On 3/1/07, Allen Gilliland <[EMAIL PROTECTED]> wrote:
new 4.0 proposal to provide stylesheet overrides for weblogs ...
http://cwiki.apache.org/confluence/display/ROLLER/Proposal+Stylesheet+Overrides+for+Weblogs
basically a way to allow weblogs to do stylesheet customizations without
having to customize their theme and hack the templates, and instead
provides a way to simple define a stylesheet page which overrides the
default styles for the theme.
please review and send your comments.
-1 on this proposal as written.
I don't think editing a CSS style sheet is the UI we want to enabling
theme customization. We can't expect users to know CSS. And there is
no standard set of CSS styles for each theme, so users will have to
examine HTML to figure out what styles can be set.
Okay, that's a valid point and on some level I agree that we can't
expect users to be CSS wizards, but lets step back for a second and at
least agree that we need some sort of strategy for allowing styling
customizations of themes. And by styling customizations I mainly mean
choosing a different color palette and possibly some font changes.
"We can't expect users to know CSS."
To be honest I don't think that is true, and to an even larger degree I
don't think that users will need to know CSS. First off, in my mind
this is a proven approach when you consider that very large and popular
sites like WordPress and even MySpace allow custom styling in this exact
way, so if it works for them then I think it can work for us. Second,
and like the WordPress and MySpace examples, users wouldn't necessarily
have to code CSS themselves, they could share it, and that's a large
part of the benefit.
In fact, we have this exact use case in development right now. Some
members of the sun.com design team have offered to develop some new
themes for Roller and we specifically took the approach that each theme
would have a default design and then provide various alternate versions
simply by plugging in a new stylesheet. This was much more useful than
actually creating XX themes which are effectively the same but with
different styling. It would then be very easy to have users simply copy
and paste the alternate stylesheets into their custom stylesheet to
allow them to change to a new palette if they wanted.
"there is no standard set of CSS styles for each theme"
True, but this is just a ramification of the way that Roller is
designed, we will never be able to enforce something like that in our
themes. However, the truth is that anyone running a Roller installation
could very easily enforce a standard set of CSS styles on all themes if
they wanted to. All you have to do is disable custom themes and then
make sure that the themes you provide do conform to any standards you
want to set. From James' response to this thread in another email it
sounds like he is planning to do this exact thing ...
"For a variety of reasons (e.g. security, accessibility standards,
branding, etc), we intend to lock down a users ability to reskin their
blog template and instead focus on the selection of customizations from
a preselected catalog."
And finally, I think it is also important to remember that this solution
is not mutually exclusive. This can be one part of multiple options the
user may have for customizing a shared theme and it does not preclude
other options from being present.
"-1 on this proposal as written."
So based on my response, what is it that you think needs to change in
the proposal to make it valid?
-- Allen
- Dave
