Fluid Components in Production
summary
A TYPO3 extension called fluid_components provides encapsulated, Fluid-written UI components with strict FC param APIs, used across sitegeist projects for about a year and running in production. It introduces typed data objects for images and links (including a typoLink converter that turns integers or arrays into page/link objects), removes view logic from markup, and supports nested components. Production works but tricky cases remain—complex Fluid viewhelpers and form handling—and a fluid style guide prototype for living documentation is in progress.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:49About the speaker
- 3:55What are fluid components
- 6:46How fluid components work
- 9:13Development workflow example
- 16:13Challenges in production
- 25:47Current state and next steps
- 27:15Living style guide plans
- 30:24Resources and Q&A
related talks
44mIt’s all about components
41mWeb Components en 2019, on en est où ?
28mSchema-Driven UI Components: Innovating Headless ERP
51mWebcomponents & lit-element in production
43mBe the Browser's Mentor, not its Micromanager
17mBeyond Components: Designing Generative UI for MCP Apps
42mMoving towards web components
24mFluent 2: Designing Teams apps that seamlessly integrate experiences across