[TYPO3-english] Templates of Collections of Pages?

bernd wilke t3ng at bernd-wilke.net
Thu Mar 13 09:10:31 CET 2014


Am 13.03.14 00:32, schrieb windy player:
> Just heard about Typo3 and had a look at the template system. Still a
> noob and a little confused.
> A friend is working on a large website for an agency where they
> represent musicians.
> Each sub-site is built by hand using HTML editing, but each sub-site is
> a common pattern.
>
> Can Typo3 help with such sites?
> The requirement would be to build a template not of a single page type,
> but of a collection of pages - some singlets and some that can be
> duplicated - and then to build a sub-site, one would select a template
> and fill in the content including the place holders for titles, body
> text, and graphic elements. If the template changed all sub-sites built
> from that template would change with constant elements like agency
> branding etc. changing in synch across all the sub-sites.
>
> One can imagine an agency that represents single musicians, song
> writers, duets, rock bands, folk groups etc each having different
> templates.
>
> Or alternatively, an artists' agency or portal that had templates for
> photographers, painters, 3D artists, print artists, etc. each with
> different, but similar templates.
>
> A template might contain the following pages:
> [For Music Group]
> Group Home Page.
> Up coming Gig schedule.
> Appearance request form page.
> Music Samples Page.
> Album sales page.
>
> [For Photographer]
> Home Page with branding / samples.
> Gallery of samples of work.
> Page of models that the photographer has worked with with a head shot
> and link to model website.
> Schedule of photo workshops with sign-up form for workshops.
> Gallery of works for sale from website.
>
> You get the idea I think?
> Can Typo3 help easily build such agency portal sites?
> Thanks,
> wp

that feature is the core function of any CMS: having one template and 
fill it with mutiple content.

in fact TYPO3 has multiple ways to realise this templating.

the basic way is not used very often as it is very abstract: define all 
your elements in typoscript, including all the HTML-markup as wraps.
doing this recursive you get your DOM build up. not easy to debug, but 
very flexible about variants.

the oldest way may be the HTML-templating with markers: you take a 
HTML-page and inserts some HTML-comments which define blocks (start- and 
end-marker) or placeholder (just one singel marker) where content may be 
replaced by the CMS.
This may be supported by extensions which insert the markers interactive 
(automaketemplate, templa voila, ...) in HTML-Tags identified by ID or 
similar.

the newest way are fluid-templates. a more flexible way of templeting 
with 'logic' inside the templates (something like SMARTY).


in TYPO3 you have multiple ways to select a template/layout for each 
single page, so you may define a set of page types with according 
templates to get similar pages with individual content.


you may copy an empty subtree for each artist, or do the management by 
some extensions.


bernd
-- 
http://www.pi-phi.de/cheatsheet.html


More information about the TYPO3-english mailing list