[
https://issues.apache.org/jira/browse/JSPWIKI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716906#action_12716906
]
Dirk Frederickx commented on JSPWIKI-504:
-----------------------------------------
Simplification of the css is something to be worked on for v3.0 as it blocks
the development of new skins.
I've have been looking into the work of OOCSS
[http://wiki.github.com/stubbornella/oocss] which promotes the reuse of
css-classes as if it were reusable components. This is similar to the
proposal of Goran, but ... I'dont think we need css-classes for the headers.
(styling of the h1/h2/h3 tags should suffice)
But probably much less unique #block-id's and much more reusable .css-classes.
Additionally, I'm considering to rename some of the main css-elements to align
with eg Wordpress template, so we can easy the porting of new templates/skins.
(eg 'pageactions' should become 'menu'; 'favorites' should become 'sidebar',
etc.)
Finally, I've been working to add lots of inline documentation to the css
style; to simplify the future maintenance.
Also commonly used colors, border-styles etc. should be documented
consistently, to ease skinning.
dirk
> New default look for 3.0
> ------------------------
>
> Key: JSPWIKI-504
> URL: https://issues.apache.org/jira/browse/JSPWIKI-504
> Project: JSPWiki
> Issue Type: Improvement
> Components: Default template
> Reporter: Janne Jalkanen
> Priority: Blocker
> Fix For: 3.0
>
>
> Folks, I'm kinda tired of our old look. I would like to propose that we
> retire the old, plain look (which looks very HTML 2.0) to an optional skin,
> and adopt a completely new default look to signify the milestone marker to a
> new life under Apache.
> However, we *do* need the hand of a capable graphic designer on this one.
> Any volunteer helpers? Feel free to attach your skins as proposals to this
> issue ;-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
