๐งฉ 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
Field-Based Joomla Config Generation
Automatically generate your componentโs configuration form based on field definitions.
What Is It?
In Joomla Component Builder (JCB), you can define global component settings using standard JCB Fields. These fields are rendered in the Joomla Component Options screen (accessible via the Options button in Joomlaโs backend Components menu).
Instead of manually writing XML config forms, you:
- Use JCBโs Field system to define parameters
- Select which fields should appear in the Options screen
- Let JCB generate the config XML and backend logic during compile
This aligns with Joomlaโs native component configuration API, ensuring consistent structure, validation, and ACL support.
Key Benefits
- Reusable Fields
Use any JCB field type (text, list, toggle, etc.) โ including shared field types with validation and logic. - No Manual XML Required
Fields marked for configuration are compiled automatically intoconfig.xml
. - ACL-Aware Fields
Apply access/view/edit control to fields using JCBโs GUI-based ACL rules. - Consistent Display & Validation
Support for labels, descriptions, tooltips, required state, and custom validation. - Round-Trip Capable
Updates in JCB update the compiled XML โ no need to manually maintain config.
How It Works
- Go to Fields in JCB and create a new field (e.g., text, textarea, toggle, list).
- In the Component โ Component Config set the fields and their tab name.
- On compile:
- JCB generates the
config.xml
with proper fieldsets/fields. - Values are stored in Joomlaโs component
params
.
- JCB generates the
Use Cases
- API keys or tokens
- Default permissions or toggles
- Feature switches (e.g., enable/disable email)
- Default values used across the component
- Branding settings (logo, footer text, etc.)
Version Control & Sharing
- Config fields can be shared across components
- Changes to shared fields update all connected components
- Tracked via reset/push/fork logic in JCB
Why It Matters
- Save time by reusing validated field types
- Create fully integrated Options screens with no manual XML
- Prevent config drift by tying UI directly to logic
- Ensure consistent validation and ACL everywhere
Conclusion
With Field-Based Joomla Config Generation, you bring consistency, security, and scalability to your componentโs configuration screen. It saves time, reduces human error, and ensures your global settings evolve alongside the rest of your JCB-powered component.