Translations
Manage local Bible translations and their availability.
This page puts similar FG Bible, frontend, installer and GetBible styles next to each other. The selector shown on each specimen is only the source of the style. When we build lib_fgui, the winning visual will receive a clean reusable name such as .fgui-card, .fgui-tabs or .fgui-loader.
Choose the overall heading language future FG Tools screens should use.
Manage local Bible translations and their availability.
A complete local Bible experience built for Joomla.

Use remote translations while keeping FG Bible independent and locally resilient.
These are the main competing surface styles currently used across FG Bible and the provider.
The shared admin stylesheet already normalises ordinary Joomla cards.
WEB and KJV are stored locally and available to the reader.
ReadyLocal Scripture package
Serve cached Scripture locally and request missing chapters according to the selected mode.
Choose the core action language that should eventually become the FGUI button family.
Several status languages currently exist. Pick the one you want to become consistent.
Compare the different ways FG currently communicates information and warnings.
All modes share the same local cache, request locking and last-known-good Scripture.
Pick the control language you want reused in settings, filters and frontends.
Remote requests happen only after an explicit action.
This is a key choice for the future FGUI navigation language.
Standard administrator tab language.
How administrators manage the Bible.
Compare dense administrator data with provider and frontend result presentation.
| Translation | Status | Verses |
|---|---|---|
| World English Bible | Ready | 31,102 |
| King James Version | Ready | 31,102 |
| Mode | Cached | Missing |
|---|---|---|
| Local Only | Local | Blocked |
| Manual | Local | Load button |
What should an FG Tools screen look like when there is nothing to show yet?
Create your first note and it will appear here.
Save a verse and it will be available in My Bible.
Add a highlight from any verse and it will appear here.
This includes your example: selecting a whole loader style as the source for the future reusable FGUI loader.
Choose the dialog language for destructive actions, providers and frontend tools.
This cannot be undone.
The provider can fetch missing Scripture again later.
These should also become part of FGUI so every future FG extension has the same professional lifecycle experience.
Remove FG Bible plus all component-owned local data.
Pick the language that should guide reusable frontend controls in future FG extensions.
These do not currently exist as a complete reusable FG component. I designed them from the dominant language already present: #1991ee, white surfaces, subtle blue-grey borders, 9–14px controls, 14px cards, low shadows and clear status colour.
The board above focuses on reusable visual families. This searchable inventory makes sure the source classes are not lost while we curate the system.