LinkForge supports translations via lang/*.json, but not every UI string is wrapped yet — only some Blade views use Laravel's __() helper, so the rest stay English regardless of locale.
Help us make the whole UI translatable. This is a friendly, incremental task — one view per PR is perfectly welcome.
How to help
- Pick a Blade view under
resources/views/ that still has hardcoded English.
- Wrap user-facing strings in
__():
- before:
<h1>Dashboard</h1>
- after:
<h1>{{ __('Dashboard') }}</h1>
- Add the new key/value to
lang/en.json (and lang/es.json if you can translate it).
- Run
vendor/bin/pint and php artisan test, then open a PR.
Tips
- Only wrap visible UI copy — not code, routes, or logs.
- Use the English sentence as the key, matching the existing style.
- Small PRs are great — even one view helps!
LinkForge supports translations via
lang/*.json, but not every UI string is wrapped yet — only some Blade views use Laravel's__()helper, so the rest stay English regardless of locale.Help us make the whole UI translatable. This is a friendly, incremental task — one view per PR is perfectly welcome.
How to help
resources/views/that still has hardcoded English.__():<h1>Dashboard</h1><h1>{{ __('Dashboard') }}</h1>lang/en.json(andlang/es.jsonif you can translate it).vendor/bin/pintandphp artisan test, then open a PR.Tips