DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to switch the BoardUI app to Arabic or Hebrew layout with Boardui

Configure DirectionProvider and the document locale for a right-to-left interface.

Who it is forA developer building a product for Arabic or Hebrew speaking users who needs mirrored layouts and keyboard navigation.

The problemSetting CSS direction alone does not configure React Aria keyboard navigation, calendars, or portalled menus.

The outcomeAn app whose layout, navigation, and overlays follow right-to-left direction, with the provider set in the root layout.

What you need first

  • A model provider API key (OpenAI, Anthropic, Google, OpenRouter, Vercel AI Gateway, Groq, or xAI)
  • A GitHub account and a Vercel account for the one-click deploy
  • Node.js and npm for local runs or CLI installs
  • A Next.js project if you want to add components to existing code

Steps

  1. Run npx boardui@latest add direction in your existing project.
  2. Wrap the children in app/layout.tsx with DirectionProvider and set the document language, such as he for Hebrew.
  3. Replace physical left and right spacing with logical styles such as ps/pe and start/end.
  4. Translate labels and accessible names in your own translation layer and check the layout in the browser.

Prompt for your agent

In the repo BoardUI/boardui, follow the RTL setup in the README for my project at <project-path> with locale <locale>. Expected output: the root layout wrapped in DirectionProvider and the document set to the right language. Verify that keyboard navigation and the date picker still work in the target locale.

Caveat. The README says direction and translation are configured separately, so right-to-left layout alone will still show English text until you translate it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page