Weave Code
Gloss Laravel Package
leanadmin/gloss
Gloss is a Laravel package for adding a searchable glossary to your app. Define terms and definitions, manage entries in LeanAdmin, and automatically highlight matching words in your content with tooltips.
Brilliant localization for Laravel
Frequently asked questions about Gloss
- What is leanadmin/gloss used for in Laravel?
- Gloss is a Laravel package for managing translation strings in the database instead of scattering them across flat PHP language files. It is aimed at multi-language apps and admin panels that need a simple in-app way to edit and organize translations.
- How do I install leanadmin/gloss?
- Install it with Composer using composer require leanadmin/gloss, then follow the package README for service provider registration, migrations, and configuration. Check your Laravel and PHP versions first, because v0.1.11 drops Laravel 6 and 8.
- Which Laravel versions does Gloss support?
- Gloss v0.1.11 adds Laravel 10 support and drops Laravel 6 and 8, and the assessment indicates Laravel 9 and 10 are the target versions. Apps on Laravel 6 or 8 should stay on the latest compatible release, such as v0.1.10, or upgrade Laravel first. Laravel 10 also requires PHP 8.1 or newer.
- Does Gloss work with Laravel __() and Blade @lang?
- Yes, Gloss is designed to work with Laravel's __() helper and Blade @lang so existing translation calls can resolve database-backed strings. You still need to verify your app's translation loader and cache behavior in staging.
- How does Gloss store and retrieve translations?
- Gloss stores translations in database tables and exposes a simple API for reading and writing strings. Runtime lookups can use the package cache, while your app can continue using normal Laravel translation helpers.
- Does Gloss cache translations?
- Yes, Gloss includes caching for fast runtime lookups. After editing translation strings, make sure the relevant cache is cleared or refreshed so the new values are served.
- Can I use Gloss in production, and how should I secure editing routes?
- Gloss can be used in production, but it is often best treated as a development or small-team admin convenience rather than a core runtime dependency. If you expose the editing UI in production, put its routes behind Laravel authentication and authorization middleware and never leave translation editing publicly accessible.
- Does Gloss handle nested translation arrays and JSON translations?
- Gloss is built around Laravel's standard translation structures, but complex nested arrays and JSON translations are areas to test carefully before relying on the editor. Validate representative strings in staging and confirm that edits round-trip correctly in your app.
- What are alternatives to Gloss for Laravel translations?
- Dedicated localization platforms such as Crowdin or Lokalise, or Laravel's native PHP and JSON language files, are common alternatives. Gloss is a lighter in-app editor and is best for small teams that want direct database-backed translation management.
- Is Gloss maintained, and how should I handle v0.1.11 upgrades?
- Gloss is pre-1.0 and maintained by a small team, so expect occasional breaking changes and pin the version in Composer. For v0.1.11, apps on Laravel 6 or 8 must stay on v0.1.10 or upgrade Laravel before updating Gloss. Apps on Laravel 9 or 10 can usually bump Composer and test translation editing and file writes in a non-production branch first.
Weaver
How can I help you explore Laravel packages today?