First of all, congratulations to the Magnolia team for getting RC1 out the door. I've been playing around with some of the things like the filters and dropping in my own servlets and I like the way it is laid out.
The question that I have in my mind, currently being a 2.1.6 user and starting a new site in what will be 3.5, is what the recommended practice is by the team for the custom code and templates? It looks like everything is moving to modules, which is nice, but I haven't seen anywhere stating a best practice for implementing a site with magnolia. In the past we've just imported the magnolia war file into eclipse and added our own code and other files into that project. We don't use maven currently nor do we have anyone in house who is comfortable using it, and it appears that the maven archetype example on the wiki http://www.magnolia.info/wiki/Wiki.jsp?page=ModuleQuickStart is for 3.0. Does that still work properly for 3.5 then or are there new pieces that need to be put in place? If the best practice is to create a module of our site implementation that we put into the war should we just take the samples module jar and base our own module off of that? Thanks, Tom ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
