๐งฉ 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-Field Language Control
Enable multilingual capabilities per field, ensuring localized content across your component.
What Is Per-Field Language Control?
Per-Field Language Control means you can:
- Flag individual fields as multilingual
- Automatically create language strings for those fields
- Ensure field values are rendered appropriately in Joomla's frontend/backend based on active language
- Integrate with Joomla's native language system and .ini files
This gives full control over which parts of your component content are static, dynamic, or multilingual.
How It Works in JCB
When editing a field:
- Go to the field's configuration.
- Enable the "Multilingual" or "Language Constant" option (exact label may vary by version).
- JCB will:
- Generate a language key for the field
- Place its value in the correct .ini file for each language
- Use
JText::_()
in output code to retrieve the localized value
- During compile, all such fields are processed automatically.
- You can also manually override or extend the generated keys using the language string interface or Excel import/export.
Key Benefits
- ๐ Multilingual Compatibility
Aligns fully with Joomlaโs multilingual system โ no hacks or workarounds required. - ๐งพ Field-Specific Customization
Only the fields you mark for translation are affected, giving you optimal performance and clarity. - ๐ Language Constants per Field
Great for UI labels, descriptions, button text, instructional messages, etc. - ๐ ๏ธ Editable via Excel Import/Export
Manage translations across all languages via spreadsheet. - ๐ No Hardcoding
Avoid static values in templates โ use language strings for better portability and flexibility.
Common Use Cases
- Component UI with multilingual buttons and labels
- Dynamic field titles in forms or lists
- SEO-friendly multilingual content (titles, slugs, etc.)
- Admin backends for international teams
Best Practices
- Keep translations updated via JCBโs export/import tools
- Combine with language string auto-indexing for easier tracking
- Only enable for fields that need localization โ not every field
Summary
JCB supports fine-grained language management by allowing developers to specify which fields in their components should be translatable. This ensures that fields such as titles, descriptions, labels, or any other dynamic text can adapt to each Joomla-supported language via the native language system.