๐งฉ 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
Repository Push/Pull/Reset Workflow
This workflow promotes reuse, collaboration, updates, and rollback in a structured and scalable way.
๐ฆ What Is the Repository Workflow?
Joomla Component Builder provides a Git-based mechanism for syncing JCB entities between your local instance and remote repositories. This allows you to:
- Pull (import) prebuilt or updated entities from a source (official or custom)
- Push (export) your local changes to a Git repo
- Reset (sync) your entity to match the latest upstream version
This makes your JCB development process modular, collaborative, and easy to maintain.
๐ ๏ธ Supported Entity Types
Repository workflows are available for many JCB entities:
- Blueprints (components)
- Field types
- Admin views, site views, custom admin views
- Dynamic GETs
- Layouts, templates, snippets
- Custom code entries
- Menus, permissions, dashboards
- Documentation blocks
Each type can be linked to a shared Git-based package to allow cross-project syncing.
๐ How to Use Push, Pull, Reset
- Connect your JCB installation to a Git-based package repository (e.g., official JCB repo, your own Git remote).
- Open an entity and choose:
- Push โ Export your changes to the repository
- Pull โ Import changes or new items from upstream
- Reset โ Force your local entity to match the upstream version
- Youโll see update logs and confirmation prompts before changes are applied.
๐ Benefits
- Share reusable elements across projects or teams
- Keep blueprints up to date with central definitions
- Fork and customize only what you need
- Roll back unwanted changes using reset
- Track version history of every synced item
- Keep consistent data structures across environments (dev/stage/prod)
๐ Secure by Design
JCB only allows updates from known and configured repositories. You can control:
- Which entities sync with which sources
- Whether auto-push/pull is allowed per item
- Whether to allow overwrite/reset of local changes
๐ง Common Use Cases
- Sync a custom Admin View across multiple components
- Fork and evolve a community-maintained blueprint
- Pull the latest Dynamic GET queries into a dashboard view
- Reset an entity after unwanted modifications
- Push a layout/snippet to a design teamโs shared repo
๐ Conclusion
The Repository Push/Pull/Reset workflow transforms JCB from a local builder into a distributed development platform. Whether you're managing one project or dozens, this version-controlled flow brings consistency, reusability, and teamwork to Joomla component developmentโright from inside the GUI.