feat: add settings page

[saboooor]

will allow us to add more settings without adding yet another nav button, will later be populated with user settings, mascot settings, etc.

Summary by CodeRabbit

• New Features
  • Added a dedicated Settings page accessible from the navigation menu
  • Introduced language selection functionality in Settings
  • Moved theme toggle to the Settings page for centralized preference management

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

📝 Walkthrough

Walkthrough

This change relocates theme toggle and settings functionality from inline navigation components to a dedicated settings page. The navigation and profile layout components now display a Settings icon linking to /settings, where users can control language selection and theme preferences.

Changes

Cohort / File(s)	Summary
Navigation Updates src/components/Elements/Nav.tsx, src/routes/profile/layout.tsx	Replaced ThemeToggle component with a Settings icon link to /settings. Updated imports to include Link from qwik-city and Settings icon from lucide-icons-qwik. Removed ThemeToggle imports.
Settings Page src/routes/settings/index.tsx	New settings route component featuring language selection via SelectMenu, ThemeToggle component, page metadata via generateHead, and translation utilities for localized UI.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 A settings home, oh what a sight!
No more toggles scattered left and right,
One cozy place for themes and tongues,
Where preferences dance on everyone's rungs,
Settings gathered, neat and bright! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat: add settings page' directly and clearly summarizes the main change: a new settings page is being added.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch unified-settings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	birdflop-com	c1fabe1	Feb 06 2026, 03:10 AM

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@src/components/Elements/Nav.tsx`:
- Around line 101-103: The Settings icon Link currently has no accessible name,
so update the Link (the element with q:slot="end" wrapping the <Settings />
component) to include an accessible label—e.g., add an aria-label="Settings" or
include visually hidden text inside the Link—so screen readers announce the
link; ensure the label is added on the Link element that contains the <Settings
/> icon in Nav.tsx.

In `@src/routes/settings/index.tsx`:
- Around line 53-55: The page metadata for the Settings route is still using the
Resources copy; update the export const head that calls generateHead to use a
Settings-appropriate title and description (e.g., "Settings - [site name]" and a
short description about user account/preferences) so SEO/UX are correct; locate
the generateHead invocation in export const head and replace the title and
description strings accordingly to reflect the Settings page.

[cloudflare-workers-and-pages]

Deploying web with    Cloudflare Pages

Latest commit:	c1fabe1
Status:	⚡️  Build in progress...

View logs