FED – Fluid Extbase Development Framework <ul><li>TYPO3 Content Development powered by Fluid and Extbase
Apologies in advance; we have a lot of bullet-points to wade through </li></ul>
What is FED? <ul><li>Based on Extbase and Fluid
A huge collection (110+) of ViewHelpers divided into almost 20 areas
A collection of Extbase Services
A collection of built-in, general purpose content elements
A way to replace TemplaVoila with pure Fluid templates </li></ul>
Feature Highlights <ul><li>Fluid Page Templates
Fluid Content Elements
Very flexible configuration
Extremely light-weight </li><ul><li>Runs on just one TypoScript template and the “content” static template included
No extension config and almost no database </li></ul></ul>
How does it work? <ul><li>Uses TypoScript and TYPO3 hooks
Is The Missing Link </li><ul><li>Extbase provides great MVC
Fluid provides great templating
FED uses these to make TYPO3 pages and content elements render through Fluid.
FED enables you to do this with great ease and portability. </li></ul></ul>
Sneak Peek <ul><li>(Screenshots, BE editing and FE result) </li></ul>
Benefits <ul><li>Extreme portability. </li><ul><li>Page and Content Element templates can be packaged as extensions
Resources can be placed in an extension
No need for database operations on installing new templates – can be moved/copied without database </li></ul></ul>
Benefits <ul><li>Flexible Configuration </li><ul><li>The power of FlexForms and Fluid combined
Fluid renders FlexForms which configure the TYPO3 BE editing
Can use saved values to affect configuration – also in conditions, loops, etc.
Page content editing and access controlled by BE layouts </li></ul></ul>
Benefits <ul><li>Lightning Fast and Light Weight </li><ul><li>New Fluid compiles and caches templates to PHP which execute...
Supports all TYPO3 caching features, including disableNoCache
Supported by Extbase object caches </li></ul><li>Fluid based </li><ul><li>Templating engine from the future </li></ul></ul>
Feature Comparison Feature TV FED Replaces TYPO3 Backend Editing experience YES NO Supports standard TYPO3 content render ...
Summary:  <ul><li>TemplaVoila good for mass editor environments; FED good for individual web sites with one or few content...
TemplaVoila is tried and trusted; FED is still beta software
Upcoming SlideShare
Loading in...5
×

FED presentation

2,997
-1

Published on

T3CON11 Presentation of the TYPO3 community project FED - Fluid Extbase Development Framework.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,997
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
17
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

FED presentation

  1. 1. FED – Fluid Extbase Development Framework <ul><li>TYPO3 Content Development powered by Fluid and Extbase
  2. 2. Apologies in advance; we have a lot of bullet-points to wade through </li></ul>
  3. 3. What is FED? <ul><li>Based on Extbase and Fluid
  4. 4. A huge collection (110+) of ViewHelpers divided into almost 20 areas
  5. 5. A collection of Extbase Services
  6. 6. A collection of built-in, general purpose content elements
  7. 7. A way to replace TemplaVoila with pure Fluid templates </li></ul>
  8. 8. Feature Highlights <ul><li>Fluid Page Templates
  9. 9. Fluid Content Elements
  10. 10. Very flexible configuration
  11. 11. Extremely light-weight </li><ul><li>Runs on just one TypoScript template and the “content” static template included
  12. 12. No extension config and almost no database </li></ul></ul>
  13. 13. How does it work? <ul><li>Uses TypoScript and TYPO3 hooks
  14. 14. Is The Missing Link </li><ul><li>Extbase provides great MVC
  15. 15. Fluid provides great templating
  16. 16. FED uses these to make TYPO3 pages and content elements render through Fluid.
  17. 17. FED enables you to do this with great ease and portability. </li></ul></ul>
  18. 18. Sneak Peek <ul><li>(Screenshots, BE editing and FE result) </li></ul>
  19. 19. Benefits <ul><li>Extreme portability. </li><ul><li>Page and Content Element templates can be packaged as extensions
  20. 20. Resources can be placed in an extension
  21. 21. No need for database operations on installing new templates – can be moved/copied without database </li></ul></ul>
  22. 22. Benefits <ul><li>Flexible Configuration </li><ul><li>The power of FlexForms and Fluid combined
  23. 23. Fluid renders FlexForms which configure the TYPO3 BE editing
  24. 24. Can use saved values to affect configuration – also in conditions, loops, etc.
  25. 25. Page content editing and access controlled by BE layouts </li></ul></ul>
  26. 26. Benefits <ul><li>Lightning Fast and Light Weight </li><ul><li>New Fluid compiles and caches templates to PHP which executes even faster
  27. 27. Supports all TYPO3 caching features, including disableNoCache
  28. 28. Supported by Extbase object caches </li></ul><li>Fluid based </li><ul><li>Templating engine from the future </li></ul></ul>
  29. 29. Feature Comparison Feature TV FED Replaces TYPO3 Backend Editing experience YES NO Supports standard TYPO3 content render hooks NO YES Supports Fluid and ViewHelpers NO YES Extbase DomainObject aware NO YES FlexForm Content Element / Page Template config NO YES Access Control to templates YES NO Access Control to content areas YES YES(1) Requires database to store configuration YES NO Has extensions which add new features or changes behavior YES NO Page Templates and Content Elements in extensions NO YES Page Templates and Content Elements as database content YES NO
  30. 30. Summary: <ul><li>TemplaVoila good for mass editor environments; FED good for individual web sites with one or few content editors
  31. 31. TemplaVoila is tried and trusted; FED is still beta software
  32. 32. FED has no supporting extensions
  33. 33. FED has, however, the combined power of Extbase, Fluid and barebone TYPO3 performance on its side </li></ul>
  34. 34. Can be mixed <ul><li>You don't have to leave TemplaVoila behind; you can have subsections of your web site use FED and others TemplaVoila
  35. 35. Fluid Content Elements work in TemplaVoila pages
  36. 36. TemplaVoila Flexible Content Elements work in Fluid pages </li></ul>
  37. 37. Feature Walkthrough <ul><li>A few slides to explain just a handful of the features FED enables </li></ul>
  38. 38. Content Elements <ul><li>FED Includes generic elements which can be easily copied and modified or used as-is
  39. 39. Elements can reference DomainObjects selected in FlexForm, ObjectStorage supported
  40. 40. Use DomainObjects' show/list templates as Content Elements with custom selections </li></ul>
  41. 41. ViewHelper Collection <ul><li>Massive library
  42. 42. Additional Structure ViewHelpers: Loop, Switch, If (extended), Hide and Comment
  43. 43. Resource ViewHelpers: Files, Images, SQL Queries, JSON sources etc.
  44. 44. Data Helpers: AJAX Form Validator, MultiUpload, DataSorter etc. </li></ul>
  45. 45. Service Collection <ul><li>DomainObjectInfo </li><ul><li>Quickly access information about DomainObjects: repository class names, extension name, controller name, etc.
  46. 46. Read values based on special, custom annotations, like @mobile or @print. For example, can be used to generate limited sets of JSON data for mobile agents or disable fields in a print view by hiding certain properties. </li></ul></ul>
  47. 47. Service Collection <ul><li>Cloning Service </li><ul><li>Copy DomainObjects
  48. 48. Relations either cloned, referenced or ignored
  49. 49. Works recursively </li></ul></ul>
  50. 50. Service Collection <ul><li>File Service </li><ul><li>Automatically upload files from Extbase forms, compatible with TYPO3 BE editing
  51. 51. Load files as Objects containing properties for paths, size, etc.
  52. 52. Copy, Move, Delete files or whole collections of files </li></ul></ul>
  53. 53. Service Collection <ul><li>ExtJS </li><ul><li>Automatically generates ExtJS4 models based on Extbase DomainObjects
  54. 54. Model Definitions can be rendered through Fluid using a custom template
  55. 55. Model Configuration can be shared between DomainObjects </li></ul></ul>
  56. 56. Enough feature descriptions <ul><li>Now for something completely different </li></ul>
  57. 57. An integration example <ul><li>Selective Product Listing Extension </li><ul><li>Has Controller with show and list actions but no defined plugins </li></ul><li>Products / Lists as Content </li><ul><li>Path to “Templates” folder used as path
  58. 58. Layouts and Partials supported
  59. 59. Select which Product(s) to display
  60. 60. Choose between List and Show, separate configuration </li></ul></ul>
  61. 61. Product List Template <ul><li>Still to come </li></ul>
  62. 62. Product Show Template <ul><li>Still to come </li></ul>
  63. 63. Purpose Ideas <ul><li>Custom top-five lists
  64. 64. Selective product highlights
  65. 65. Time-limited displays which changes based on time settings from “access” tab
  66. 66. Entire pages which are specially rendered presentations of a single product
  67. 67. And that's just for a product-based extension... </li></ul>
  68. 68. Integration Summary <ul><li>Replaces many controller actions
  69. 69. Can skip work on controllers completely for display-only extensions
  70. 70. Especially good for imported display data
  71. 71. Very flexible; content editors decide what to show
  72. 72. Very extensible; developers or even designers can quickly add completely new content displays </li></ul>
  73. 73. Fluid Page Templates <ul><li>Source code is worth 1,000 pictures </li></ul>
  74. 74. Integrating Content Elements and Pages <ul><li>Create your extension and Fluid Content Element / Page template folders and files
  75. 75. Add this piece of TypoScript – you can do this from ext_localconf.php or Configuration/TypoScript/setup.txt:
  76. 76. (TS piece) </li></ul>
  77. 77. Documentation <ul><li>Pride taken in full documentation
  78. 78. Example extension provided
  79. 79. Code Review
  80. 80. Live examples and dedicated documentation and guide web site </li></ul>
  81. 81. Community Goal <ul><li>Contributions of repeatedly used ViewHelpers and Services wanted
  82. 82. Developer contributions always welcome
  83. 83. Document and illustrate live all contributed ViewHelpers
  84. 84. Ideas, suggestions, comments... </li></ul>
  85. 85. In summary <ul><li>Lightweight, Fluid-based TYPO3 sites
  86. 86. Portable: no DB, pre-packaged config
  87. 87. Flexible: FlexForms to configure display
  88. 88. Developers: Contains many helpers for getting things done quickly
  89. 89. Designers: Easy to implement highly customizable templates
  90. 90. Open to contributions </li></ul>
  91. 91. Future Plans <ul><li>Even better configuration options for FCEs and Pages. Additional field types, wizards, configuration options – help wanted!
  92. 92. Feedback from experienced TYPO3 users to further improve integration approaches
  93. 93. More devs to contribute ViewHelpers, Services and Fluid Content Elements </li></ul>
  94. 94. I leave you with this image <ul><li>Only bit of TSconfig (optional!) for a TYPO3 site on FED and Fluid/Extbase:
  95. 95. TCEFORM.pages.layout.removeItems = 0,1,2,3
  96. 96. And the only static template requirements: “FED” and “content”
  97. 97. Further TS setup 100% optional
  98. 98. The rest is entirely up to your Fluid templates and Backend Layouts </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×