Integrating Websites With TYPO3 Neos
•Als KEY, PDF herunterladen•
2 gefällt mir•3,835 views
Talk about TYPO3 Neos Websites at T3CON12DE in Stuttgart. Describes the technical foundations of Neos websites and how to start integrating.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Integrating Websites With TYPO3 Neos
Ähnlich wie Integrating Websites With TYPO3 Neos (20)
Mehr von Christian Müller
Mehr von Christian Müller (15)
Integrating Websites With TYPO3 Neos
- 1. Integrating Websites with TYPO3 Neos
- 2. Implementing a Website with TYPO3
- 5. 3 Ways to go on
- 6. 3 Ways to go on Classic Templating
- 8. 3 Ways to go on Templavoila
- 10. 3 Ways to go on Fluid Template
- 12. Write Typoscript
- 15. Create Pages
- 19. Folder Structure? ? fileadmin templates extension
- 20. TypoScript?
- 21. TYPO3 Neos
- 22. Installation
- 24. Site Package
- 25. Site Package Contents MyCompany.MySite Classes Configuration Resources
- 26. Resources Contents Resources Public Private
- 27. Public Resources Contents Public StyleSheets Images JavaScripts ...
- 28. Private Resources Contents Private Content Templates TypoScripts
- 29. Content/Sites.xml <node type="TYPO3.Phoenix.ContentTypes:Page" nodeName="anotherpage" locale=""> <properties> <title>Another Page</title> </properties> <node type="TYPO3.Phoenix.ContentTypes:Section" nodeName="main" locale=""> <node type="TYPO3.Phoenix.ContentTypes:Headline" nodeName="headline1" locale=""> <properties> <title><![CDATA[<h1>Want More?</h1>]]></title> </properties> </node> <node type="TYPO3.Phoenix.ContentTypes:Text" nodeName="text1" locale=""> <properties> <text><![CDATA[ Some content ]]></text> </properties> </node> </node> </node>
- 30. Content Model
- 31. Nodes
- 32. Node structure site root page content section content element representation of domain models
- 33. addressed by nodePaths /sites/typo3org/home/subpage/main/text1
- 34. are addressed by nodePaths /sites/typo3org/home/subpage/main/text1 site root
- 35. are addressed by nodePaths /sites/typo3org/home/subpage/main/text1 site root pages
- 36. are addressed by nodePaths /sites/typo3org/home/subpage/main/text1 site root section pages
- 37. are addressed by nodePaths /sites/typo3org/home/subpage/main/text1 site root section pages content
- 38. Private Resources Contents Private Content Templates TypoScripts
- 39. Page Template
- 40. Fluid Template
- 44. Private Resources Contents Private Content Templates TypoScripts
- 47. FE AT UR E Consistency
- 48. FE AT UR E Extensibility
- 49. FE AT UR E Simplicicy
- 50. TypoScript Objects • Template • Array • Collection • Case • Menu • (Page)
- 51. FE AT UR E Flexibility
- 52. TypoScripts Contents TypoScripts Library Nodes
- 53. TypoScripts Contents TypoScripts Library Root.ts2 Nodes
- 54. TypoScripts Contents TypoScripts Library Root.ts2 Nodes
- 55. RE M IN /sites/typo3org/home/subpage D ER site root page content section content element representation of domain models
- 56. RE M IN /sites/typo3org/home/subpage D ER site root page content section content element representation of domain models
- 57. TypoScripts Contents TypoScripts Library Root.ts2 Nodes Home Subpage.ts2
- 59. Prototypes
- 60. prototype(TYPO3.TYPO3:MenuRenderer).implementationClassName = ↵ 'TYPO3TYPO3TypoScriptMenuRenderer' prototype(TYPO3.TYPO3:Section) < prototype(TYPO3.TypoScript:CollectionRenderer) prototype(TYPO3.TYPO3:Section) { implementationClassName = 'TYPO3TYPO3TypoScriptSection' collection = ${context.children(this.getNodePath()).children()} }
- 61. EEL?
- 62. EEL? FlowQuery?
- 63. EEL? FlowQuery? Fizzle?
- 64. Lets take it apart ${q(node).children().filter('left').first()}
- 65. Simple Property Access ${q(node).property('text')}
- 67. Processors
- 68. Processors prototype(TYPO3.Phoenix.ContentTypes:TextWith Image).text << 1.wrap(prefix: '<header>', suffix: '</header>')
- 69. How that all comes together
- 70. Tips
- 71. Custom Content Elements
- 74. My Request
- 75. Please TRY AND GIVE FEEDBACK
- 76. Thank you for joining! Christian Müller Free Trainer and Developer TYPO3 Neos and Flow Core Team Member Book and Music Lover twitter: @daskitsunet christian.mueller@typo3.o rg
Hinweis der Redaktion
- \n
- \n
- \n
- \n
- Research about Presentations, Story?\nProblems for people learning TYPO3 ->\n- no predefined structure for templates (like other systems)\n- different templating systems\n- TypoScript\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- lets zoom in on that\n
- syntax differences\n
- \n
- \n
- \n
- Where are your Templates, CSS, Images?\n
- Where are your Templates, CSS, Images?\n
- \n
- How does it look like for Neos?\n
- \n
- simple\ndatabase -> admin user -> site package!? \n
- FLOW3 package!?\nDescribe FLOW3 packages\n\n
- Classes -> minimal Plugins / Services specific to the site, not portable\nConfiguration -> Content Type Configuration, Site specific FLOW3 configuration\nResources -> next\n
- quickly go further, Ordering, maybe joke about wrongness of slide\nPublic / Private -> same as other packages, access control. As in Extbase\n
- Why that in public and for example no Templates\nSass, Less Private!\nOther Folders -> Fonts, Downloads, Assets, Media\n
- Content -> contains XML file with nodes, quick look later\nTemplates -> name not fixed, but should be &#x201C;Templates&#x201D; -> subfolder Page with Fluidtemplate(s)\n\nTypoScripts -> name FIXED! Contains all TypoScripts, to be seen later in detail\n
- Sites.xml can contain full page + content structure\nExerpt\nImport and Export possible\nDefault / dummy content easily created\n
- \n
- actual content has a flexible schema depending on the content type\nrepresenting pages, content elements .....\nhierarchical\n\n\n
- Explain structure\nExplain Section!\n
- \n
- \n
- \n
- \n
- \n
- Content -> contains XML file with nodes, quick look later\nTemplates -> name not fixed, but should be &#x201C;Templates&#x201D; -> subfolder Page with Fluidtemplate(s)\n\nTypoScripts -> name FIXED! Contains all TypoScripts, to be seen later in detail\n
- \n
- \n
- \n
- coming back to the section\n
- coming back to sections and parts\n
- \n
- \n
- \n
- naming\ncasing\ndefinitions\nsyntax\n
- PHP Object Implementations\nContext stack\n
- very few TypoScript objects\nstill already lots of features and flexibility\n
- \n
- Processors\nEEL Expressions\n
- Library -> Root.ts2 BASE for the site\nNodes -> reflects structure of your node tree\n
- Library -> Root.ts2 BASE for the site\nNodes -> reflects structure of your node tree\n
- Library -> Root.ts2 BASE for the site\nNodes -> reflects structure of your node tree\n
- We are in a site package\n
- We are in a site package, so that part of the node path is known\nremember the rest\n
- Library -> Root.ts2 BASE for the site\nNodes -> reflects structure of your node tree\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- Selector syntax like jQuery for TYPO3\nworking with a context (usually a node)\n
- \n
- \n
- \n
- typoscript snippet from actual site\n
- \n
- \n
- \n
- Look at available examples\n
- \n
- \n
- \n