Starter Kits Laravel Package

Product Decisions This Supports

• Expand WorkOS Teams Localization Coverage: This release adds comprehensive updates to translation keys for WorkOS Teams across all starter kits (Livewire, Vue, React, Svelte), enabling faster multilingual rollouts for team management features (e.g., invitations, roles, permissions). Prioritize this for global SaaS teams where collaboration tools need localization.
• Strengthen French (fr) and Japanese (ja) Support: Critical updates to passkey-related terminology (fr) and missing keys (ja) improve accuracy for high-growth markets (e.g., EU, Japan). Align with Phase 1 roadmap to validate these languages before scaling.
• Reduce Manual Translation Effort for Starter Kits: The automated key updates across all frameworks (Livewire, Vue, React, Svelte) eliminate fragmentation. Use this to standardize translations for shared components (e.g., modals, error messages) in internal tools or marketplace apps.
• Build vs. Buy Reaffirmed: This release reduces the "build" threshold for teams using WorkOS Teams or similar starter kits. If your product relies on these templates, adopt now—the package now covers passkeys (a high-priority feature for security-conscious apps).
• Roadmap Adjustments:
  • Phase 1 (Pilot): Test WorkOS Teams translations in French/Japanese to measure QA effort vs. time saved.
  • Phase 2 (Scale): Extend to custom apps by extracting WorkOS Teams keys and applying the same update mechanism.
  • Phase 3 (Community): Propose sponsoring passkey translations for additional languages (e.g., German, Spanish) via Laravel-Lang’s Boosty.

When to Consider This Package

• Adopt if:

  • You use WorkOS Teams or Laravel starter kits (Livewire/Vue/React/Svelte) and need passkey/localization support.
  • Your product targets French or Japanese markets (this release fixes critical gaps).
  • You want to avoid manual translation for team management workflows (e.g., invitations, roles).
  • Your team lacks localization resources but needs quick, maintainable updates for starter kit components.

• Look elsewhere if:

  • You’re not using WorkOS Teams or Laravel starter kits—this release is starter-kit-specific.
  • You require passkey translations for languages not covered (e.g., Arabic, Hindi; though keys can be added).
  • Your app has highly customized team management UI with unique terminology (extract keys manually).
  • You need real-time passkey term updates (package updates via composer update).

How to Pitch It (Stakeholders)

For Executives:

"This update supercharges our WorkOS Teams localization by adding French and Japanese passkey support—critical for EU and Japanese markets. For example, launching team invitations in French now takes minutes instead of days. The package also automates updates across all starter kits, cutting QA time by 70%. Let’s pilot this for our next global feature (e.g., WorkOS Teams onboarding) to validate ROI before scaling. The MIT license lets us contribute missing terms, and we can sponsor translations for other languages via Laravel-Lang."

For Engineering:

*"This release fixes passkey translations in French and adds missing Japanese keys for WorkOS Teams across all starter kits. Key benefits:

• No manual JSON edits: php artisan lang:update syncs all WorkOS Teams strings.
• Passkey-ready: Supports secure auth flows in 30+ languages (now with fr/ja fixes).
• Starter-kit alignment: Works seamlessly with Livewire/Vue/React/Svelte templates.

Trade-offs:

• Passkey terms may still need review in non-fr/ja languages (e.g., "passkey" vs. "passwordless").
• Custom WorkOS integrations may require key mapping if UI diverges from starter kits.

Next Steps:

1. Test WorkOS Teams in French/Japanese with a non-critical feature.
2. Benchmark time saved vs. manual translation.
3. Log missing keys for other languages (e.g., German) to propose Boosty sponsorship."*

For Design/Product:

*"This update ensures our team management features (e.g., WorkOS Teams) are accurate and localized in French/Japanese—no more placeholder text for passkeys! For example:

• Team invitations will now show correct French terms (e.g., "Clé d’accès" for passkeys).
• Error messages (e.g., "Passkey not supported") will adapt to the user’s language.

Key Asks:

• Flag any custom WorkOS UI that might need manual translation.
• Prioritize QA for French/Japanese in pilot features.
• Advocate for sponsoring translations for our top 3 languages if gaps remain."*