๐งฉ 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
Track Last Build, Size, Line Count, Field Count
๐ Summary
JCB automatically records and displays key build metrics โ such as the most recent build time, total line count, field count, and compiled file size โ so you can monitor project complexity and performance at a glance.
๐งฎ What It Tracks
Every time you compile a component in Joomla Component Builder (JCB), the system logs build-related metadata that gives you insight into:
- โฑ๏ธ Last Build Timestamp โ when the component was last successfully compiled
- ๐ฆ File Size โ size of the generated ZIP package
- ๐ Line Count โ number of lines across compiled PHP/HTML/INI files
- ๐ง Field Count โ total number of custom-defined fields across Admin Views
- ๐งฑ View Count โ total Admin, Site, and Custom Admin Views used
- ๐ File/Folder Counts โ number of files and folders output during build
This helps you estimate the size, complexity, and growth of your component over time.
๐งญ Where It Appears
- ๐ At the bottom of the compiled
README
(if enabled) - ๐งฉ Inside the Compilerโs summary output screen
- ๐ In the Component metadata page inside JCB
- ๐ค Optional: exported via
metadata.json
file alongside builds
๐ Use Cases
- Track how your component grows in complexity over time
- Compare different blueprint versions to see what's changed
- Monitor field bloat or layout overuse during iterative development
- Debug performance issues (large views or excessive custom logic)
๐ Pro Tip
Pair this feature with version-aware changelogs to gain insight into what triggered increases in line count or file generation between versions.
โ Why It Matters
These metrics provide a lightweight yet powerful form of component observability. They help you answer questions like:
- โWhen did this component last compile?โ
- โHow big is the output ZIP?โ
- โHow many fields/views are we managing?โ
- โAre we trending toward over-complexity?โ
This fosters awareness and helps teams keep Joomla components lean, efficient, and well-structured.
๐ Conclusion
Component metrics arenโt just for curiosity โ they are essential for healthy long-term project maintenance. With JCBโs automated tracking of build statistics, you always know where your component stands.