Increase collaboration and boost productivity in your TYPO3 projects by using encapsulated Fluid Components.
The Fluid Components ecosystem enables new ways of collaboration in TYPO3 projects. When applied to your project, it decouples frontend development from backend development, which has some clear advantages. Not only can frontend developers take responsibility for their part of the project, but they can also work on frontend tasks independently of backend development.
Easy to learn and accessible for new team members.
Streamlined communication between Frontend and Backend.
Proven and tested in small and big TYPO3 projects.
Well documented TYPO3 extensions with excellent support.
Enforced design system guidelines give developers better orientation.
Reusable components for high consistency across the project.
Highly modular based on the principles of Atomic Design.
Maintainable, scalable and consistent code base.
Isolated development of frontend components.
Clear interface prevents misusage of elements.
Encapsulated components avoid side effects on other parts of the website.
Fluid Styleguide visualizes which components already exist and which have yet to be built. It shows all variants of a component and is by definition up-to-date, in contrast to static styleguide documents.
Isolated Development of Components
Fluid Styleguide can serve as an independent frontend workshop. Components can be developed when the backend hasn't even started with the implementation.
Easy and Flexible Configuration
Fluid Components and Fluid Styleguide have an easy setup process which is based on established TYPO3 standards, such as AssetCollectors.
Components can be tested in a configurable set of viewport sizes as well as multiple languages. With live editing in the styleguide, design edge cases can be discovered early in the development process.
The ecosystem is always evolving and comes with dedicated developer tools, such as a linter for automatic code quality checks and integrations for popular development IDEs.