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

2. Apologies in advance; we have a lot of bullet-points to wade through

4. A huge collection (110+) of ViewHelpers divided into almost 20 areas

5. A collection of Extbase Services

6. A collection of built-in, general purpose content elements

7. A way to replace TemplaVoila with pure Fluid templates

9. Fluid Content Elements

10. Very flexible configuration

12. No extension config and almost no database

15. Fluid provides great templating

16. FED uses these to make TYPO3 pages and content elements render through Fluid.

17. FED enables you to do this with great ease and portability.

20. Resources can be placed in an extension

21. No need for database operations on installing new templates – can be moved/copied without database

23. Fluid renders FlexForms which configure the TYPO3 BE editing

24. Can use saved values to affect configuration – also in conditions, loops, etc.

25. Page content editing and access controlled by BE layouts

27. Supports all TYPO3 caching features, including disableNoCache

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

31. TemplaVoila is tried and trusted; FED is still beta software

32. FED has no supporting extensions

33. FED has, however, the combined power of Extbase, Fluid and barebone TYPO3 performance on its side

35. Fluid Content Elements work in TemplaVoila pages

36. TemplaVoila Flexible Content Elements work in Fluid pages

39. Elements can reference DomainObjects selected in FlexForm, ObjectStorage supported

40. Use DomainObjects' show/list templates as Content Elements with custom selections

42. Additional Structure ViewHelpers: Loop, Switch, If (extended), Hide and Comment

43. Resource ViewHelpers: Files, Images, SQL Queries, JSON sources etc.

44. Data Helpers: AJAX Form Validator, MultiUpload, DataSorter etc.

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.

48. Relations either cloned, referenced or ignored

49. Works recursively

51. Load files as Objects containing properties for paths, size, etc.

52. Copy, Move, Delete files or whole collections of files

54. Model Definitions can be rendered through Fluid using a custom template

55. Model Configuration can be shared between DomainObjects

58. Layouts and Partials supported

59. Select which Product(s) to display

60. Choose between List and Show, separate configuration

64. Selective product highlights

65. Time-limited displays which changes based on time settings from “access” tab

66. Entire pages which are specially rendered presentations of a single product

67. And that's just for a product-based extension...

69. Can skip work on controllers completely for display-only extensions

70. Especially good for imported display data

71. Very flexible; content editors decide what to show

72. Very extensible; developers or even designers can quickly add completely new content displays

75. Add this piece of TypoScript – you can do this from ext_localconf.php or Configuration/TypoScript/setup.txt:

76. (TS piece)

78. Example extension provided

79. Code Review

80. Live examples and dedicated documentation and guide web site

82. Developer contributions always welcome

83. Document and illustrate live all contributed ViewHelpers

84. Ideas, suggestions, comments...

86. Portable: no DB, pre-packaged config

87. Flexible: FlexForms to configure display

88. Developers: Contains many helpers for getting things done quickly

89. Designers: Easy to implement highly customizable templates

90. Open to contributions

92. Feedback from experienced TYPO3 users to further improve integration approaches

93. More devs to contribute ViewHelpers, Services and Fluid Content Elements

95. TCEFORM.pages.layout.removeItems = 0,1,2,3

96. And the only static template requirements: “FED” and “content”

97. Further TS setup 100% optional

98. The rest is entirely up to your Fluid templates and Backend Layouts