Hi Joe, Answers inline:
> -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:user-list-owner@magnolia- > cms.com] Im Auftrag von Joe Szurszewski (via Magnolia Forums) > Gesendet: Montag, 04. November 2013 21:28 > An: Magnolia User List > Betreff: [magnolia-user] How to build a site without modules > > We want to create a website for a client using Magnolia CE. This will be a > fairly large, but conceptually simple site that will not require any custom > Java > to be written. It will be static pages, built using existing components. > > However, we will need to do some custom templating and create a custom > theme. The documentation states that best practice is to put a theme into > it's own module, put templates into their own module, etc. The problem > with this for us is it appears that to create our own module(s), you have to > create a project, which means starting with a Maven archetype, then > bringing everything into an IDE. We'd like to avoid these extra layers of > complexity and not have to worry about Maven or using an IDE. > If you aren't Java-Coding, you don't really need your own module. Creating one may have some advantages: - you can make use of magnolia's module install mechanism to set everything up just the way you need it - you can easily install your stuff to new magnolia instances - you are forced to work in a cleaner way, avoiding hacks and bad practices It may have some disadvantages: - might take some time to get up and running - might not fit your development team (if you have more web-coders than java-coders) In the end I think it is much more important to find a way of working that suits your team and lets everyone be productive than to force some kind of paradigm for ideological reasons. So if you think you'll find it easier without a module or IDE, then go for it, it's definitely possible. > We just want to create some custom templates and a custom theme for the > new site. Is it possible to do this without an IDE, Maven, etc.? If so, how? > > Two possibilities spring to mind: > > 1) Can you create modules manually, without an IDE? If so, is there > documentation on how to do this? > Not really, I wouldn't recommend that. If you go the module way, then use eclipse. It will make life easier in the long run. > 2) Can you create custom templates and a new theme just as files in the file > system, not in the repository? Then deploy the new templates and theme > by just copying these files onto the production server? I remember reading > somewhere that Magnolia looks in the file system for templates. Again, if > this is viable, how to do it? > Yes, definately! You can put templates in the filesystem under docroot/templates, although I would say this isn't necessarily best practice anymore. An even better way is the following: - install the inplace-templating and webdav modules - create your templates in JCR (in the templates workspace) - edit them via webdav using your favourite text-editor - you can use XML import/export to copy templates and definitions between magnolia instances (development, production, etc...) Regards from Vienna, Richard > -- > Context is everything: http://forum.magnolia- > cms.com/forum/thread.html?threadId=dd34e252-b3ef-4548-9ec5- > abce35b013d1 > > > ---------------------------------------------------------------- > For list details, see http://www.magnolia-cms.com/community/mailing- > lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
