๐งฉ 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
Reusable Admin Views
Across Multiple Components
Joomla! Component Builder (JCB) empowers developers to define admin views once โ and reuse them across multiple components in the same JCB instance. Instead of recreating views, fields, layouts, and logic repeatedly, you can blueprint reusable views that behave like shared templates, keeping your backend UI and logic consistent, DRY (Don't Repeat Yourself), and versionable.
This approach helps streamline large ecosystems where multiple components share the same data structure or UI functionality โ such as dashboards, logs, reports, or reusable CRUD interfaces.
What Is a "Reusable Admin View"?
Fields
Filters
Forms (edit view)
List view layout
Permissions
Custom logic
Templates
Language strings
Once defined, it can be linked into multiple components. This way, any improvements or logic changes to the original view can be reflected across all components that include it.
Benefits of Reusing Views
- Centralized updates: fix or improve once, apply everywhere
- Consistent interface and behavior across components
- Faster prototyping for new components
- Modular architecture: break down large systems into small, shared view units
Example Use Case
Imagine youโve built a component for managing support tickets (com\_support) and another for managing customer assets (com\_assets). Both need a "Logs" admin view showing action history.
With JCB, you can:
โ
Create a reusable admin view called "Action Log"
โ
Define its fields (date, user, action, context), permissions, and layout
โ
Link it into both components
โ
Optionally override certain behavior/context per component if needed
How to Reuse a View
- In Component A:
- Create a new Admin View
- Add fields, layout, filters, and logic as usual
- Mark it as reusable (by naming convention or tagging it)
- In Component B:
- Add a new Admin View
- Select a Existing View (select from existing blueprints)
- This will Reuse the view from Component A
- Customize the link:
- Set alias if needed
- Set permissions, menu entry, or view name
- Apply component-specific layout overrides if required
- Compile Component B โ the reused view will be included and scoped to it.
Whatโs Reused?
- Fields and filters
- Field settings and validation
- Layouts and templates
- Custom code blocks
- Language strings (auto-renamed per component context)
- View permissions and field ACL
Can You Sync Reused Views?
Are There Limitations?
View names must remain unique per component (Joomla requirement)
You cannot use views from a component that hasnโt been imported
Reused views cannot span database tables unless specifically designed to do so
Related Features
Summary
Reusable admin views in JCB help you:
- โ Reuse powerful interfaces across components
- โ Avoid duplication of effort
- โ Maintain UI/logic consistency
- โ Scale quickly across projects