2012/5/8 Ioan Eugen Stan <[email protected]>: > The design is not done and there is much to be done but I wanted to > get some impressions before I continue. Some things that come to my > mind: > - integrate with Google search and analytics
Yes, this is important. Expecially the Analytics part, as we want to be able to measure things to understand if what we do works or not. > - finish integration with twitter > - design some aggregation pages similar to [2], [3] IMO it has a much higher priority to let the CMS skin and the maven skin to match their look. Once the pages can be mixed together we can go live, and after this we can start adding new docs/aggregation pages. Remember we have maven-generated docs that will probably have to be interlinked with CMS pages. This page, for example, is automatically generated by Maven using javadocs and source code, so I don't expect to be able to move that to CMS: http://james.apache.org/mailet/standard/mailet-report.html I prefer our current skin to the new one (as it is right now) because it is much more readable: http://james.apache.org/server/3/config-users.html http://james.staging.apache.org/server/config-users.html I don't see paragraph titles in the new pages. I'm not against moving to a new skin/layout, but we should keep consistency and readability. Also, make sure urls do not change, so in this case it is missing a "/3/" in the path. The idea is that you should just replace "james.apache.org" with "james.staging.apache.org" to see any page that we're going to move from maven to CMS. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
