[TYPO3-ect] Template Structure
Jochen Rieger
j.rieger at connecta.ag
Tue Dec 27 14:07:36 CET 2005
Hi Jan-Hendrik @ others,
basically we are using a very similar structure. Directly under the root
page there is a bunch of sysfolders grouped by the parent folder called
'TS Templates'. This might explain it more easily:
- Project ROOTpage
-- TS Templates (sysfolder)
--- menus (sysfolder)
--- cObjects (sysfolder)
--- extensions (sysfolder)
--- functions (sysfolder)
-- Main Page 1
-- Main Page 2
--- Subpage 2.1
--- Suvpage 2.2
etc.
So, there is the main template in the root page that mainly includes all
the static and basis templates. Directly in 'TS Templates' you will find
two TS templates called 'PAGE' and 'CONFIG' where of cause all page and
config setup and constants are stored.
The other folders I think are self explaining. In 'menus' are GMENU and
TMENU templates as well es lib.naviRootline, lib.naviMeta and lib.naviLang.
In 'cObjects' are stored the modifications in tt_contens and cObjects in
general, for example to make the sitemap accessible etc.
'extensions' contains all the templates for plugin configuration.
And all other TS code that can be grouped together you will find in
'functions'. Like lib.mediapics for things like
file.import = uploads/media/
file.import.data = levelmedia: 1, slide
etc.
Everything is properly set up with constants so that our admins can
easily build up a new site mainly just by choosing and adjusting options
in the constant editor. This comes in very handy when somebody that is
not too much into TypoScript now is able to set up a fully accessible
GMENU or TMENU just by setting up color, font, font-size, rollover state
etc. in the constant editor.
Kind regards,
Jochen
--
:: innovative it-strategies ::
:: ::
:: www.connecta.ag ::
More information about the TYPO3-team-extension-coordination
mailing list