๐งฉ 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
Per-Entity README Auto-Generation
JCB can automatically generate documentation for any entity (like views, models, fields, templates, and more) in Markdown format
๐ What Is It?
Every major entity in Joomla Component Builder (JCB) โ including Admin Views, Fields, Snippets, Templates, Layouts, Field Types, and more โ supports automated README generation.
These READMEs are created dynamically by the compiler based on the entity's properties, configuration, links, and associated metadata.
You can configure this behavior via:
- Entity settings โ Enable README output
- Compiler settings โ Output directory & format
- Snippet or template injection for custom content blocks
๐ Whatโs Included in Each README?
The generated README will usually contain:
- ๐ Title and description of the entity
- ๐ Last modified timestamp
- ๐งฑ Linked entities (fields, snippets, templates, layouts, dynamic GETs)
- โ๏ธ Settings used in the build
- ๐ Usage examples or developer notes (if present)
- ๐ Auto-generated tables for clarity (e.g., field mappings, config)
This makes every component of your project independently understandable.
๐ฏ Why Use It?
- โ For documentation automation
- โ For onboarding other developers faster
- โ For self-documenting large components
- โ For generating shareable GitHub/Gitea/GitLab-level docs
- โ For syncing component logic to wikis or support pages
You can even export the whole docs folder for integration into your website, GitHub Pages, or internal portals.
๐ฅ Output Format
By default, these README files are:
- Markdown (.md)
- Placed in the /docs or /readme folder of your component source
- Optionally compiled into the output zip package
You can customize this path per project in the global or compiler configuration.
๐งฉ Integration With Other JCB Features
- Combine with Custom Code tags for personalized doc snippets
- Append changelog data using version metadata
- Add PHPDoc blocks in templates to enrich the final README
๐ฆ Use Cases
- Add per-view README files in Git-based component blueprints
- Export documentation during nightly or CI builds
- Sync to GitHub Pages or readthedocs using your JCB component output
- Inject custom branding or usage tips directly into each README
๐ง Conclusion
JCB's per-entity README auto-generation brings self-documenting software into Joomla development. Every feature, field, and view you create can now explain itself โ reducing friction, improving onboarding, and boosting maintainability across teams or long-term projects. It's documentation without the extra work.