Since Richard and Antti already replied to the reasons why there are not more "free" templates. I would love to comment on the "how easy" part of your question.
>From my own experience I can only say that it is pretty easy to create a >proper theme for your site. Once you have modified the static prototype with >your own CI, it is very easy to transform it into a theme module. My biggest >challenge while creating the blue theme was actually deciding on color >schemes. Not every shade of a color fits into a scheme and will most likely >create eye cancer :p but there's a few great palette generators out there that >can help you with that [1]. It is very easy to work with the static prototype, it helps you in many ways. There's a file called nav.html for example, which will help you style the standard navigation quickly. It displays the navigation in all its possible variations on 1 single site, so just by working on this 1site you can be sure that your navigation will look like that on all sites and all depths of levels, expanded or not. Even if you need to add or modify templates that have a different HTML output, it is easy to insert this into a static file and style it accordingly. If you reference the image files relatively to your css for example, you can be sure that this will work the same from a proper theme module, no further adjustment needed. Once you have the static equivalent, it is very straight-forward to generate a theme module. You can use the maven archetype [2] to generate a skeleton module and then transfer your images/js/css from the prototype into the correct places (you will notice that the skeleton will have the same places for all of these folders as the static prototype). Copy the pop theme configuration, adjust it to your paths and export it into your theme (as described in the documentation article mentioned a few posts up [3]). Unless you need special installation or update tasks, you can even use the standard theme installer. I would say it's only a matter of a few hours to do an own and simple design implementation - if you can decide on colors and styling unlike me.... The more you cannot use from STK templates, the more time you will have to invest into styling. But STK already covers a lot of day-to-day use-cases imho. [1] http://slayeroffice.com/tools/color_palette/ [2] http://wiki.magnolia-cms.com/display/WIKI/Module+QuickStart [3] http://documentation.magnolia-cms.com/use-cases/creating-a-custom-theme.html On Feb 10, 2012, at 9:55 AM, Magnolia Forums (on behalf of Frederic Close) wrote: > I'm also a bit surprised to find only one alternate Theme for the STK. > > Is this a sign that it's not so easy to create ? > > -- > Context is everything: > http://forum.magnolia-cms.com/forum/thread.html?threadId=0ed96574-6e80-4d2f-b660-2b7bec5ded7d > > > ---------------------------------------------------------------- > 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]> ----------------------------------------------------------------
