These are practical compositions built from the same FG UI components. Use them as starting structures, not separate themes.
Dashboard hero, product actions, status and operational cards.
Health, actions and product status in one consistent surface.
For records, users, content, logs, transactions or any component list view.
Search, filter and act on records without changing the page language.
| Name | Status | Updated | |
|---|---|---|---|
| Primary record | Published | Today | |
| Secondary record | Review | Yesterday |
Main form with a compact metadata and actions sidebar.
Useful for large Joomla components with their own internal navigation.
One consistent component shell for multiple internal views.
Simple settings page for a plugin without inventing a different interface.
Configuration on one side and the actual frontend module pattern on the other.
Hero, proof, features and call to action without a separate theme system.
Use the same FG UI foundation for a public website, application and Joomla administration.
Shared tokens and components.
Designed for phone through desktop.
No outside UI framework.
For articles, documentation, Bible readers, blogs and knowledge bases.
Suitable for users, products, extensions, articles or any searchable directory.
Short description of the result.
Short description of the result.
Profile navigation with a settings workspace.
Login and registration patterns use the same form system.
Use your account details to continue.
Navigation, working area and contextual inspector for larger tools.
The centre pane can hold an editor, builder, table, canvas or workflow.
A full-width footer pattern using FG UI tokens without external template styling.
Use these as starting patterns. If a product needs a genuinely new structure, add the smallest reusable layout primitive to FG UI rather than creating a new theme.