Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Emerging TypoScript Best Practices - InspiringC...
Search
Sebastian Kurfürst
April 23, 2016
Technology
3
260
Emerging TypoScript Best Practices - InspiringCon 2016
This presentation has been held by Sebastian Kurfürst @InspiringCon 2016 in Kolbermoor.
Sebastian Kurfürst
April 23, 2016
Tweet
Share
More Decks by Sebastian Kurfürst
See All by Sebastian Kurfürst
How To Write Unmaintainable Code - PHPDD 2024
skurfuerst
0
67
How To Write Unmaintainable Code
skurfuerst
0
58
PHPDD23: Practical Debugging and Performance Profiling
skurfuerst
0
63
Neos Con 2023: Migrating a Project to Neos 9
skurfuerst
0
31
Neos Con 2022: The New Content Repository
skurfuerst
0
31
Neos Conference 2021: Event Sourced Content Repository - the current status
skurfuerst
0
32
2020: Sandstorm Technology Radar
skurfuerst
0
12
Neos Conference 2020: Event Sourced Content Repository - the current status
skurfuerst
0
20
Plone-Tagung Dresden 2020 - Patterns und Best Practices für die Entwicklung erweiterbarer und leistungsstarker React SPAs am Beispiel der Neos CMS-Benutzeroberfläche
skurfuerst
1
200
Other Decks in Technology
See All in Technology
ZOZOTOWNの大規模マーケティングメール配信を支えるアーキテクチャ
zozotech
PRO
0
290
Bet "Bet AI" - Accelerating Our AI Journey #BetAIDay
layerx
PRO
4
1.7k
Claude CodeでKiroの仕様駆動開発を実現させるには...
gotalab555
3
1k
データモデリング通り #2オンライン勉強会 ~方法論の話をしよう~
datayokocho
0
160
Kiroでインフラ要件定義~テスト を実施してみた
nagisa53
3
350
はじめての転職講座/The Guide of First Career Change
kwappa
0
780
Infrastructure as Prompt実装記 〜Bedrock AgentCoreで作る自然言語インフラエージェント〜
yusukeshimizu
1
110
マルチプロダクト×マルチテナントを支えるモジュラモノリスを中心としたアソビューのアーキテクチャ
disc99
1
520
大規模イベントに向けた ABEMA アーキテクチャの遍歴 ~ Platform Strategy 詳細解説 ~
nagapad
0
230
生成AIによるデータサイエンスの変革
taka_aki
0
3k
事業特性から逆算したインフラ設計
upsider_tech
0
100
AIのグローバルトレンド 2025 / ai global trend 2025
kyonmm
PRO
1
140
Featured
See All Featured
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
16k
Build The Right Thing And Hit Your Dates
maggiecrowley
37
2.8k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
126
53k
GraphQLとの向き合い方2022年版
quramy
49
14k
Code Reviewing Like a Champion
maltzj
524
40k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
36
2.5k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
Art, The Web, and Tiny UX
lynnandtonic
301
21k
Agile that works and the tools we love
rasmusluckow
329
21k
Designing for Performance
lara
610
69k
Product Roadmaps are Hard
iamctodd
PRO
54
11k
Practical Orchestrator
shlominoach
190
11k
Transcript
Best Practices about TypoScript
Sebastian Kurfürst @skurfuerst
Emerging Best Practices about TypoScript
Why TypoScript?
http://www.sxc.hu/browse.phtml?f=view&id=956017 TypoScript as View Coordinator
Extensibility Planned Extensibility Unplanned Extensibility Supported during updates Own Risk
Planned Extensibility prototype(TYPO3.Neos:ContentCase) < prototype(TYPO3.TypoScript:Case) { default { @position =
'end' condition = TRUE type = ${q(node).property('_nodeType.name')} } }
Unplanned Extensibility # custom TypoScript prototype(TYPO3.Neos.NodeTypes:Image)
[email protected]
= false
# custom TypoScript prototype(TYPO3.Neos.NodeTypes:Image)
[email protected]
= false # Default definition of
Image TS Object prototype(TYPO3.Neos.NodeTypes:Image) { ...
[email protected]
= TYPO3.Neos:ConvertUris { forceConversion = true } } Dependency Ordering crucial!
Dependency Ordering crucial! TYPO3.Neos.NodeTypes My.Site # composer.json { "require": {
"typo3/neos-nodetypes": "*" } }
cat Configuration/PackageStates.php | grep composerName
None
Files and Folder Structure
• one TypoScript object per file • subfolders according to
your domain
Embrace TypoScript Prototypes
prototype(Acme:Slideshow) < prototype(TYPO3.Neos:Content) { .... } # Instantiation mySlideshow =
Acme:Slideshow
class Slideshow extends Content { } $mySlideshow = new Slideshow();
Explicit Names!
TypoScript prototypes for page objects page = Page { ....
} Old # COPY (bad!) specialPage < page { .... } root.special { condition = ${....} renderPath = '/specialPage' } prototype(Site:MyObject) < prototype(Page) { .... } page = Site:MyObject Recommended prototype(Site:Special) < prototype(Site:MyObject) { .... } root.special { condition = ${....} type = 'Site:Special' }
Composition vs Inheritance
MyTextWithImage MySpecialText Inheritance MyImage MyText
MyTextWithImage Composition MyImage MyText
Try to use composition!
How? prototype(MyTextWithImage) < prototype(TYPO3.Neos:Content) { image = MyImage { image
= ${q(node).property('image')} } ... same for text element }
One Content, Multiple Output Formats
prototype(TYPO3.Neos:ContentCase) < prototype(TYPO3.TypoScript:Case) { default { @position = 'end' condition
= TRUE type = ${q(node).property('_nodeType.name')} } }
prototype(Flowpack.SearchPlugin:SingleResult) < prototype(TYPO3.TypoScript:Case) { default { condition = Flowpack.SearchPlugin:CanRender {
type = ${node.nodeType.name + 'SearchResult'} } type = ${node.nodeType.name + 'SearchResult'} } fallback { condition = TRUE type = 'TYPO3.Neos:DocumentSearchResult' } } Product Product ProductSearchResult
Fluid vs TypoScript
TypoScript Fluid rendering controller extensible declarative no loops simple templates
imperative
<f:for each="{items}" as="item"> <li{ts:render(path:'{item.state}.attributes', context: {item: item}) -> f:format.raw()}> <neos:link.node
node="{item.node}">{item.label}</neos:link.node> <f:if condition="{item.subItems}"> <ul> <f:render section="itemsList" arguments="{items: item.subItems}" /> </ul> </f:if> </li> </f:for> Fine to use e.g. for menus!
None
The Content Cache
Page Menu ContentCollection Text Plugin Image cached embed embed embed
embed embed Page Cache Record
prototype(Page) { @cache { mode = 'cached' } }
Page Menu ContentCollection Text Plugin Image cached embed embed embed
embed embed Page Cache Record
Page Menu ContentCollection Text Plugin Image cached embed embed embed
cached embed Page Cache Record Plugin Cache Record
Page Menu ContentCollection Text Plugin Image cached embed embed embed
uncached embed Page Cache Record always rendered dynamically
cached uncached embedded part of outer cached element store in
cache render dynamically
Page Menu ContentCollection Text Plugin Image cached embed embed embed
uncached embed always rendered dynamically What is currently being rendered? What is in the (TypoScript) context?
What is currently being rendered? What is in the (TypoScript)
context? prototype(Page) { @cache { mode = 'uncached' context { 1 = 'node' 2 = 'documentNode' } } }
cached embedded part of outer cached element store in cache
uncached render dynamically
Basic Idea of caching Calculate Cache Entry Identifier Does Entry
Identifier Exist In Cache? expensive calculation (such as rendering a page) Page Cache Record store in cache e.g. URL
Configuring the Entry Identifier prototype(Page) { @cache { mode =
'cached' entryIdentifier { // parts of the entry identifier node = ${node} editPreviewMode = ${node.context.currentRenderingMode.name} } } }
Configuring the Entry Identifier prototype(Page) { @cache { mode =
'cached' entryIdentifier { // parts of the entry identifier fixedIdentifier = 'Hello World' } } }
Done!
There are only two hard things in Computer Science: cache
invalidation and naming things. -- Phil Karlton
Not Quite!
Core Question When should the cache be flushed?
When should the cache be flushed? Page Cache Record Everything
Node_A.B Everything Node_A.B DescendantOf_A NodeType_X
Confused?
Neos has sane defaults!
None
None
Existing Packages
Flowpack.Listable
None
Neos.MarketPlace neos.io
None
Neos.NeosIo
https://github.com/psmb/
TYPO3.Neos TYPO3.Neos.NodeTypes
Experiment, Share, Discuss, Iterate!
None