2012/5/10 Ioan Eugen Stan <[email protected]>: > 2012/5/10 Stefano Bagnara <[email protected]>: >> 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 > > If one tool can do that, means another one will be able to do so, but > I'm looking for ways to avoid it. Thanks for mentioning the page is > generated.
Sure, but it will take much more time to recreate this tool outside maven (and expecially outside java) than to create 20 skins :-) Please note that this tool have a lot of knowledge right now and uses both the sources and javadocs and the compiled classes and also instantiate mailets to ask their names: you don't want to do this in perl, i'm sure. >> 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. > > You are right. Readability will be excellent, I probably should have > made it more clear that I concentrated on "general shape" / CSS and > not content looks. Most pages are auto-converted from xdoc to mdtext, > but not a very good conversion. Now I'm looking into xdoc -> html > conversion directly. The idea is to keep our current pages in xdoc, > use svn:externals to bring them into site-cms/content space and apply > XSLT transformations (in the perl scripts) to build html out of them > on the CMS side. > This way we will have no conversion errors and keep the docs with the > code. Any help with this step is welcomed. Don't we loose the CSM "browser-based" editing this way? > I've put some examples from openejb. Did you took a look at them? We > can make our pages look like that too, and it's not hard as you can > see from the mdtext sources. You can read them as text with ease. As I wrote, my main concern is that maven generated stuff will looks like ASF generated stuff. I don't see major issues in the current (old) look, but I'm happy to move to a more modern look. The opebejb skin "as is" is not too good to accept our big main menu as it goes multiline and very high when you have narrow screens (tablet/phones). > Moving to Apache CMS means a consistent view across all components of > the project and across all website. It's very easy to do actually, but > requires some familiarity with the technology. I don't understand this sentence: we already have a consistent view in our website. My understanding is that we are evaluating CMS so to be able to have some website/docs separated from the code and editable without using svn. > We can bring the existing docs with svn:externals so the urls will > remain untouched. Old docs will still be available, but with the old > view. In time, we can move them to the new look or phase them out and > replace them with a link to the full archive. I don't think this is a good plan. We need a new maven skin that resemble the new look *before* we can mix the environments. I don't like having some pages with a skin and some other pages with another skin: we already have this "difference" between website and wiki and we want to fix this, not to make the issue bigger. I explained this also in IRC, but I didn't understand the feeling of the other people from that meeting, so I can't tell you if this will be a blocker or not. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
