I completely agree with what Jan said. Some additional thoughts: - You always have two forces, where you'll always have time effort on either one of them: designers - developers Every html change will need in any system a change of templates. So either the time effort is on designer side or developer side. The need of changing html on the fly is on designer perspective often from sticking on already known structures (html wise).
- As Jan said, the html of the prototype is very flexible and well optimized, for example for accessibility. It covers many need, but for sure not all of them. Depending on a specific project, out of my experience, it covers 80%-95%. So why inventing 100% of the html, when only 20%-5% need to be changed? Which leads to the next point - The prototype is the bases of STK, so the html rendered reflects 1:1 the prototype. Thats doesn't mean, you have to stick 1:1 to it. You can define for a project changes in the prototype (the 5-20% mentioned above), as additional divs and so on. Implementing them into STK is usually very easy and fast done. So your developers do not have ti implement 100% of all templates and paragraphs, but only the difference. -> you create your own static prototype of a project based on the STK prototype - Having such a project static prototype has many benefits: -- Common base for coordination between project leaders & developers & java coders & templaters -- Designers can change design, without the need of knowing Magnolia -> CSS & JS -- You can provide a clickable dummy for the customer, to have a first impression and discuss usability of the pages -- Project adaptions are always clear, because its the difference between the original STK prototype and your specific prototype Which leads to the next point - You can define you own company prototype which is the base of all of your projects. Possible reasons could be, that you need in most of your projects more 'areas' (configurable div elements which contain paragraph collections), more inner divs and so on. Then implementing such a prototype into Magnolia/STK is quite easy. STK doesn't narrow you in on just using its own prototype. So you would extend the STK for example with 'OurCompanyTemplateKit' STK was built exactly in a ideology, that such a need is easy to fulfill. - And not to forget, STK provides much more functionality than just the prototype STK has implemented a lot of useful and powerful functions such as Site Definitions, Template configurations site-wide&template-specific, Managing of Templates user-role based and so on. So even if you decide not to use the STK prototype, not to use STK at all you would loose many powerful benefits. I hope I could get you some more insight, of STK's ideology. Cheers Christian On Dec 16, 2010, at 11:07 AM, Jan Haderka wrote: > > On Dec 16, 2010, at 10:50 AM, Kareem Al Jabr wrote: > >> Ok I have another question. Our creative design team insists not using STK >> claiming that it will limit their work and let them only deal with CSS. They >> want to have the ability to edit the structure of HTML pages adding divs and >> other stuff which will be changing in a daily bases. Would that be possible? >> to keep changing the html structure when needed. I am not able to find a >> helpful and detailed documentation regarding this. > > Yes you can do this. BUT - having your design team changing html will make > for an extra work for developers who would need to put that html into > templates. > The STK templates and structures were designed with great care and focus on > cleanness in regard of accessibility and SEO and at the same time to allow > for maximum flexibility. > Do you have examples from them of what is not possible to do with the CSS and > for what they need to modify the HTML? > > Also the normal strategy is to develop the template and CSS for all the > variations of pages and paragraphs and then just have editors to pick the > right page and paragraph template rather then continuously changing the CSS > and HTML and re-deploying them together with the content (although it is > certainly possible with Magnolia). > >> >> For example if they want to redesign the section structure which is in the >> prototype of the STK, is there a way to move the new HTML structure into the >> STK template?! > > All STK templates are loaded to the repository. You can find them under > Templating Kit/Templates. If you modify them and want them to be loaded from > the repo, do not forget to enable modified template (at the bottom of the > dialog). > > HTH, > Jan > >> >> Thanks, >> Kareem >> >> On Thu, Dec 16, 2010 at 12:12 PM, Christian Ringele >> <christian.ring...@magnolia-cms.com> wrote: >> Hi Kareem, >> >> The only difference is, that you see the subtree of one site definiton, >> meaning: >> (You can have a look at EE on our demo too: >> http://demo.magnolia-cms.com/.magnolia/pages/adminCentral.html >> user: superuser >> pw: superuser) >> >> In EE you can see this: >> >> >> There are by default 4 site definitions, in which for example the default >> shows as sub-nodes templates, theme and so on. >> What you see in CE is the content/subtree a site definition as default >> (because you only have one). >> >> Cheers >> Christian >> >> On Dec 16, 2010, at 8:50 AM, Antti Hietala wrote: >> >>> Yes, site configuration is equivalent of (one) site definition. Go ahead >>> with the tutorial. >>> >>> >>> On Dec 16, 2010, at 8:47 AM, Kareem Al Jabr wrote: >>> >>>> Yes I am using the community edition. So do you mean site configuration is >>>> equivalent to site definition!? And I go ahead with the tutorial. >>>> >>>> Thanks Antti >>>> >>>> On Thu, Dec 16, 2010 at 11:40 AM, Antti Hietala >>>> <antti.hiet...@magnolia-cms.com> wrote: >>>> Hi Kareem, >>>> >>>> You are using the Community Edition. Community Edition does not have >>>> multisite support; it only supports a single site. That's why you see >>>> Templating Kit > Site Configuration as opposed to Templating Kit > Site >>>> Definitions. You basically have only one site definition (=site >>>> configuration) to work with. You can still complete the templating >>>> tutorial. However, if managing multiple sites (for campaigns, events, >>>> subsidiaries etc.) with different themes and domains is important to you, >>>> get the Enterprise Edition. >>>> >>>> --Antti >>>> >>>> >>>> On Dec 16, 2010, at 8:13 AM, Kareem Al Jabr wrote: >>>> >>>>> Hi Magnolians, >>>>> >>>>> I've built webapp war from source code, I have also added the STK module, >>>>> all is working fine except I cannot find site definition under templating >>>>> kit which is mentioned in the STK tutorial. Please see attached >>>>> screenshot. >>>>> >>>>> Thanks, >>>>> Kareem >>>>> <12-16-2010 11-10-50 AM.png> >>>> >>>> >>>> >>>> ---------------------------------------------------------------- >>>> For list details see >>>> http://www.magnolia-cms.com/home/community/mailing-lists.html >>>> To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> >>>> ---------------------------------------------------------------- >>>> >>> >>> >>> >>> ---------------------------------------------------------------- >>> For list details see >>> http://www.magnolia-cms.com/home/community/mailing-lists.html >>> To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> >>> ---------------------------------------------------------------- >> >> Best regards, >> >> Christian Ringele >> Magnolia International Ltd. >> >> Magnolia® - Simple Open Source Content Management >> >> >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> >> ---------------------------------------------------------------- >> > > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> > ---------------------------------------------------------------- Best regards, Christian Ringele Magnolia International Ltd. Magnolia® - Simple Open Source Content Management ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
