- How do I install pishran/nova-rtl-theme in Laravel Nova?
- Install it as a Composer dependency with composer require pishran/nova-rtl-theme. The service provider is auto-discovered, so you typically do not need to register it manually. Make sure Laravel Nova is already installed, run the asset publication step, and enable the theme in your Nova configuration.
- Which Laravel Nova versions does this RTL theme support?
- The package is a presentation-layer theme tightly coupled to Nova's Blade and CSS asset structure. Compatibility depends on the Nova major version pinned in each application, so verify the supported Nova version before adopting it. A Nova major upgrade is the most likely source of theme breakage.
- Does pishran/nova-rtl-theme support Persian, Arabic, Hebrew, and Urdu?
- Yes. The theme flips the Nova admin layout to right-to-left for RTL locales such as Persian, Arabic, Hebrew, and Urdu. It adapts the dashboard, forms, tables, and navigation for a more natural RTL experience.
- Do I need to publish assets or configure anything after installing the RTL theme?
- Adoption is typically a Composer require, an asset publication step, and a Nova config toggle. You generally do not need bespoke application code beyond ensuring Nova is installed. If you plan locale-based theme switching, introduce that logic alongside the package rather than retrofitting it later.
- Will the RTL theme break my Nova forms, tables, or modals?
- Failure modes are cosmetic rather than functional, such as misaligned form fields, inverted chevrons, flipped modal layouts, or broken responsive breakpoints. The v1.5.13 release was a targeted RTL-correctness patch for issue #24, which is typical of this package's minor visual defect risk. Run a short manual visual QA pass after installation and on every Nova upgrade.
- How do I switch between RTL and LTR layouts based on locale in Laravel Nova?
- Theme selection is typically governed by locale, so use Nova's configuration toggle alongside your locale detection logic. Introduce locale-based theme switching when you first adopt the package rather than adding it later. This keeps RTL and LTR admin experiences consistent for mixed-locale teams.
- Can I remove pishran/nova-rtl-theme easily if it does not work out?
- Yes. Because the package is presentation-only, rollback is trivial: remove the Composer dependency and restore Nova's default theme. There is no data migration, cutover window, dual-write, or backfill concern.
- Is pishran/nova-rtl-theme actively maintained, and what happens if it is abandoned?
- This appears to be a small community project with a narrow user base and no commercial SLA. The real operational risk is maintainer responsiveness to Nova version drift, which can cause lag between a Nova release and a compatible theme release. If the project goes dormant, the fallback is to vendor or fork the CSS yourself.
- Does this package affect my database, routes, authentication, or business logic?
- No. It registers CSS overrides and asset bindings for the Nova admin UI and does not touch application domain logic, database schema, routes, or auth. That confines the blast radius of adoption to the presentation layer.
- How should I test the RTL theme before promoting it to production?
- Pilot it in one non-critical admin environment with an RTL locale, then run a visual QA checklist across core Nova screens. Check form fields, modals, tables, date pickers, nested layouts, and mobile breakpoints. Promote to production only after that pass, and re-run the same checklist on every Nova upgrade as a standing gate.