๐งฉ Architecture & Core Logic
- Super Powers
- Joomla Powers
- Compile Native Components, Plugins & Modules
- Multi-Version Support
- Conditional Logic Injection
- Reusable Admin Views
- Dynamic GET Builder
- Round-Trip Code Integration
- Custom Admin Views
- Site Views
- Dynamic Dashboards
- Model Linking Between Views
- Shared Field Reuse Across Views
- Drag & Drop Field Mapping
- Dynamic Field Visibility
- Independent Packaging
๐ Joomla CMS Integration
๐งฑ Custom Code System (Powerful Dual Feature)
๐ Field Type System
๐ Snippets, Templates, Layouts, Libraries
- Snippets Reusable Html Blocks
- Layouts Reusable Php Render Templates
- Templates Page Level Views Linked To Custom Admin Site Views
- Libraries JS CSS Assets Linked To UI
- CDN Local Toggle For Library Delivery
- Media Folder Injection With Override Support
- Repository Push Pull Reset Workflow
- Init Snippets Layouts Templates Via Gui
๐ฆ Packages
๐งฉ Architecture & Core Logic
๐ File & Code Management
๐ง Code Reuse & Blueprints
๐ Joomla CMS Integration
๐จ Visual GUI & UX
๐ Internationalization
๐ฆ Packaging & Distribution
โ๏ธ Compiler Engine Features
๐งฑ Custom Code System
๐ Field Type System
๐ Dynamic GET (Visual SQL Engine)
๐ Snippets, Templates, Layouts, Libraries
๐ Documentation & Metadata
๐ Analytics & Insights
๐งฉ Architecture & Core Logic
- Super Powers
- Joomla Powers
- Compile Native Components, Plugins & Modules
- Multi-Version Support
- Conditional Logic Injection
- Reusable Admin Views
- Dynamic GET Builder
- Round-Trip Code Integration
- Custom Admin Views
- Site Views
- Dynamic Dashboards
- Model Linking Between Views
- Shared Field Reuse Across Views
- Drag & Drop Field Mapping
- Dynamic Field Visibility
- Independent Packaging
๐ Joomla CMS Integration
- Token Integration
- ACL Per View, Field, Item
- Field-Based Joomla Config Generation
- Support For Joomla Categories/Tags/Custom Fields
- CLI-Ready Components
- Joomla Update Server Integration
- Version-Aware Language String Compilation
- Remote Publishing to Custom Repo Update Streams
๐ Field Type System
- Field Types Define Templates And Data Types
- Gui Defined Rules Required Unique Nullable
- Save Get Hooks Per Field
- Database Schema Auto Generated From Field Settings
- Per Display Field Rendering Config List Edit
- Create Dynamic Models With Modals Selectors
- Conditional Js And Css Per Field
๐ Snippets, Templates, Layouts, Libraries
- Snippets Reusable Html Blocks
- Layouts Reusable Php Render Templates
- Templates Page Level Views Linked To Custom Admin Site Views
- Libraries JS CSS Assets Linked To UI
- CDN Local Toggle For Library Delivery
- Media Folder Injection With Override Support
- Repository Push Pull Reset Workflow
- Init Snippets Layouts Templates Via Gui
Layout Builder
Effortlessly structure how your Joomla views are rendered โ with reusable, PHP-based layouts that you control entirely via the JCB GUI.
What Is a Layout?
A layout in Joomla Component Builder (JCB) is a reusable PHP file that defines how a specific part of your componentโs output is rendered โ typically a list view, item view, or a custom interface section. Layouts serve as structural templates, separated from business logic, and are injected into Site Views, Custom Admin Views, and Templates via the JCB GUI.
Key Features
- ๐โGUI-Based Assignment
Easily assign layouts to views using a simple code snippet โ<?php echo LayoutHelper::render('layout_name', [?]); ?>
>. - ๐โReusable Structure
Create once, reuse anywhere: layouts can be used across multiple views and components. - ๐โSnippet Injection
Use Snippets (partial templates) inside layouts for modular, maintainable rendering. - ๐ง โDynamic Data Injection
Access Dynamic GET results or JCB placeholders directly in layout output. - ๐จโStylable & Extendable
Load JavaScript/CSS Libraries (like UIkit, Chart.js, Bootstrap) to extend your UI directly from JCB. - ๐ฆโGit-Friendly & Resettable
Layout definitions are versionable: pull updates, reset from source, or fork your own variants. - ๐โOverride-Compatible
Generated layouts support Joomlaโs native override system โ just like core components.
Typical Use Cases
- List views for custom admin views or site content
- Item detail renderers (custom profiles, logs)
- Dashboard layouts with charts or metrics
- Custom workflow or step-by-step UI interfaces
- Modular injection into Site or Custom Admin Templates
Layout vs Template vs Snippet
Entity | Purpose |
---|---|
Layout: | Renders a specific html layout with php injected data |
Template: | Groups layouts/snippets for whole views |
Snippet: | Reusable partial UI (e.g., button block) |
Layouts are injected into Templates. Snippets can be embedded in Layouts.
Workflow
- Go to Layouts in JCB.
- Create a new layout with a filename and description.
- Insert your PHP/HTML logic, placeholders, or snippet keys.
- Optionally attach libraries (JS/CSS).
- Compile โ the layout appears under
/layout
in your component. - Customize further with overrides, version control, or dynamic logic.
Why Use Layouts?
- Decouple logic from presentation
- Maintain reusable design patterns across projects
- Let non-developers adjust layouts visually in JCB
- Reduce complexity of frontend/backend view design
- Maintain DRY code through snippets and layout inheritance