The document discusses developing a standard for themes in TYPO3 CMS. It proposes storing themes in extensions for easy maintenance and use. The goals of the workshop are to discuss a theming standard, usability, and how to deploy themes. Ideas for a standard include using Neos or Extbase package structures and providing theme metadata. Technically, themes could register in a themes extension and be selected from the template module, including necessary TypoScript, constants, and page TS. The discussion covers theme registration and content elements.

1. Themes in TYPO3?!
Montag, 8. Juli 13

2. Why?
Good for getting
started
Provide solutions for
typical layouts Show best practices
Store Themes in
Extensions
easy maintainable byreplacing some files
Easy to use
Montag, 8. Juli 13

3. Why?
Good for getting
started
Provide solutions for
typical layouts
Show best practices
Store Themes in
Extensions
easy maintainable by
replacing some files
Easy to use
Montag, 8. Juli 13

4. Why?
Good for getting
startedProvide solutions for
typical layouts
Show best practicesStore Themes in
Extensionseasy maintainable by
replacing some files
Easy to use
let the community grow
by lowering the barrier
less boring work for
developers
Montag, 8. Juli 13

5. Other CMS Systems are extremly
successful by providing easy to use
themes.
Montag, 8. Juli 13

6. Wordpress
Montag, 8. Juli 13

7. Drupal
Montag, 8. Juli 13

8. TYPO3?
Montag, 8. Juli 13

9. TYPO3!
Montag, 8. Juli 13

10. TYPO3!
Montag, 8. Juli 13

11. TYPO3!
Montag, 8. Juli 13

12. Goals of the workshop
Montag, 8. Juli 13

13. • Development of a TYPO3-Template-
Standard
• Discuss usability and compatibility of
theming for TYPO3 CMS & TYPO3 Neos
• Discuss and decide how to deploy
templates
Goals of the workshop
Montag, 8. Juli 13

14. What do you expect
from a „theme“?
Montag, 8. Juli 13

15. Montag, 8. Juli 13

16. Standardization
Montag, 8. Juli 13

17. Standardization ideas
• use neos package structure?
• use extbase extension structure?
• provide some more information in special
files?
Montag, 8. Juli 13

18. example structure
Montag, 8. Juli 13

19. Collecting data about a
theme
• can be done from ext_emconf.php
• can be done like in NEOS with a file called
ext:theme_name/Meta/theme.yaml
Montag, 8. Juli 13

20. Technical Idea
Ext:THEMES
Montag, 8. Juli 13

21. Theme registers in
theme repository
theme can be
selected in
sys_template
TypoScript,
Constants and
PageTS get included
Theme Registration
Montag, 8. Juli 13

22. Sys-Template with selected theme from Ext:THEMES
Extension
Templates
Static
Templates
Hook, which includes TypoScript based on
value in sys_template.tx_themes_theme
news, dialog, fluidcontent, ...
Theme Rendering
Montag, 8. Juli 13

23. Sys-Template with selected theme from Ext:THEMES
Extension
Templates
Static
Templates
Hook, which includes TypoScript based on
value in sys_template.tx_themes_theme
news, dialog, fluidcontent, ...
Theme Rendering
PageTS
Until 6.2 use an XClass to inject PageTS
Since 6.2 use a hook to include PageTS
Montag, 8. Juli 13

24. Sys-Template with selected theme from Ext:THEMES
Extension
Templates
Static
Templates
Hook, which includes TypoScript based on
value in sys_template.tx_themes_theme
news, dialog, fluidcontent, ...
Theme Rendering
PageTS
Until 6.2 use an XClass to inject PageTS
Since 6.2 use a hook to include PageTS
BEFE
Montag, 8. Juli 13

25. Theme Registration
• can be done in various ways
• theme registry class with adapters
• extension dependencies
• extension naming scheme
• pure TS is silly, because of the overhead if you
would provide many themes in one installation
Montag, 8. Juli 13

26. Theme Registration
• can be done in various ways
• theme registry class with adapters
• extension dependencies
• extension naming scheme
• pure TS is silly, because of the overhead if you
would provide many themes in one installation
Montag, 8. Juli 13

27. Content Elements
Montag, 8. Juli 13

28. gridelements
templavoila
fluidcontent
dce
NEOS cce
Montag, 8. Juli 13

29. gridelements
templavoila
fluidcontent
dce
NEOS cce
Montag, 8. Juli 13