Hi Andy, On Jan 13, 2011, at 10:05 PM, Andreas Schaefer wrote:
> > Hi > > I do understand that Magnolia company wants to promote the EE version because > we all want to earn our living. That said I had to drop using STK because > I could not create a module based deployment (could not update the Prototype > through a module) You are absolutely free to update prototype setting via Module Version Handler. Could you please describe what kind of problems you ran into? Maybe you forgot to declare dependencies in module descriptor to ensure your module is installed only after the prototype is bootstrapped by STK? > as well as being limited to one type of site per instance and I also don't > need to attribute Magnolia on page itself. > > But I am really wondering if limiting the CE to one site is such a good idea. > Having worked a core developer on JBoss and XDoclet we never though of > limiting our code for the community edition but rather try to be distributed > as far as we could to try selling add-one values like support and other > services down the road. Therefore I would think that it would be better to > let people use the STK with as many sites as possible because sooner or later > people will need support. If someone starts up a business he/she cannot > afford the licensing fee but as soon as he has some success the fee shouldn't > be a problem but if he/she decided at the beginning to use Drupal etc instead > of Magnolia then they probably don't go back. This is something we can discuss at length and never come to conclusion that would satisfy both sides. To answer at least some of your concerns: - when you start a business and don't have money for the support fee, you would hardly need more then one site. - If you are building business that requires multiple sites, you would be better off spending your valuable resources on the support fee in exchange of getting your multiple sites up and running faster and focusing on building the business rather then wasting your even more valuable time building multiple sites. - Attribution required by STK is just one badge on the site. You are free to choose the visual form of it to fit your site design so it is not limiting you in any way really, except for saying that you use free software to power your site. Cheers, Jan > > Cheers - Andy > > On Jan 11, 2011, at 11:46 PM, Philipp Bärfuss wrote: > >> >> For the clarification. The site concept works the same for CE and EE with >> the restriction that EE is supporting multiple sites. That this is labeled >> "Site Configuration" in the CE and "Site Definitions" in the EE is a rather >> stupid mistake and a ticket has been opened: >> --> http://jira.magnolia-cms.com/browse/MGNLSTK-732 >> >> The resulting template definition is: current site prototype overlaid with >> the concrete template (stkHome for instance). Each of the configuration can >> be done in the prototype (site wide) or in the specific template. >> >> --> chapter "Template prototype" in >> http://documentation.magnolia-cms.com/technical-guide/stk.html >> >> The clue is that all templates use the same template script (main.ftl) which >> by default is configured in the prototype. The differences between the >> templates are achieved with dynamic includes (different templates for areas >> as like the extras area, ....). This allows adaption of a STK website at any >> degree and with as little of copy paste as possible. >> >> --> chapter "Template inclusion" in >> http://documentation.magnolia-cms.com/technical-guide/stk.html >> --> >> http://documentation.magnolia-cms.com/templating/stk/templating.html#mainftl >> >> Cheers >> - Philipp >> >> On 06.01.2011, at 19:46, Jörg Schaible wrote: >> >>> >>> Hi Andreas, >>> >>> On Donnerstag, 6. Januar 2011, Andreas Schaefer wrote: >>>> Hi Joerg >>>> >>>> For CE the Site Definition is rename to 'Site Configuration' under the >>>> 'Templating Kit' tab. Also note that you cannot create your own custom >>>> Home template even though you can create your own Section template etc. In >>>> addition keep in mind that many settings (for example the location of the >>>> Home FreeMarker template) is set inside the Templating Kit -> Site >>>> Configuration -> templates / prototype (the path for the Home FreeMarker >>>> template is set there inside the 'templatePath' node). >>> >>> Hmm. I already tried that by taking a copy of stkHome, but I wondered where >>> the mapping between the assigned "home" template and stkHome is and how I >>> can >>> remap this :-/ >>> >>> - Jörg >>> >>> >>> ---------------------------------------------------------------- >>> For list details see >>> http://www.magnolia-cms.com/home/community/mailing-lists.html >>> To unsubscribe, E-mail to: <[email protected]> >>> ---------------------------------------------------------------- >> >> >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- >> > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
