๐งฉ 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
GUI to Rewrite or Update Language String Context
centralized control over how your component communicates with usersโwhile helping you maintain clarity, accuracy, and internationalization-readiness
What Is Language String Context?
In Joomla, language strings (such as COM_EXAMPLE_HEADING_TITLE) represent translatable labels and messages used in the component. The โcontextโ refers to where and how these strings are usedโsuch as in forms, tooltips, views, or validation errors.
Why You Might Need to Rewrite Language Context
- You renamed a view or field, but its language keys are still using the old context.
- You want to consolidate similar language strings under a common prefix.
- You want to clarify vague strings (e.g., โLabelโ โ โItem Nameโ).
JCBโs GUI allows you to find and refactor these string references quickly and safely.
Key Features
- ๐ Visual Language String Management
The GUI presents all language strings defined in your component with:- Current key
- Current value
- Usage context
- Associated view/field/template (if applicable)
- ๐ Batch Rewrite and Reassignment
Quickly rename or remap language keys and valuesโeither one-by-one or in bulk. - ๐ Advanced Filtering
Search by string key, value, associated view, or language file (admin/site). Helps you locate orphaned or outdated strings. - โ๏ธ Inline Editing
Click and edit string values directly in the GUI, with live validation of key syntax and duplication. - ๐ฏ Context Correction
Automatically realign language keys to reflect updated view names, field names, or component namespaces. - ๐ ๏ธ Version Control Compatible
All changes are stored in your JCB blueprint and can be exported, versioned, or synced across projects.
Use Cases
- Refactoring legacy blueprints where string keys are poorly named.
- Aligning language strings with new branding or UX conventions.
- Preparing a component for multilingual translation.
- Correcting mismatches between field labels and their .ini values.
How to Use
- Navigate to the Language Strings section inside JCB.
- Use the filter/search options to locate the relevant string(s).
- Select a string and choose Edit or Rename.
- Apply your changes and save.
- Optionally run a โRecompile Language Stringsโ action to propagate the updates across templates and views.
Conclusion
The language context editor in JCB gives you centralized control over how your component communicates with usersโwhile helping you maintain clarity, accuracy, and internationalization-readiness. Whether youโre renaming fields or preparing your component for JED publication, this tool keeps your language strings perfectly aligned.
Summary
JCB provides a built-in GUI that allows you to easily search for, rewrite, and update the context of language strings across your entire component. This ensures that your component's interface remains consistent, clear, and user-friendlyโeven as your logic or field usage evolves.