Skip to content

810: update styleguide #832

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
luoh00 merged 1 commit into from
Mar 5, 2026
Merged

810: update styleguide #832

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions STYLEGUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -384,6 +384,7 @@ export const router = createBrowserRouter([

- Regular ts files can be named in camelCase (ex. `customTypes.ts`)
- React files (.tsx) must be named in PascalCase (ex. `DashboardPage.tsx`)
- Page files should end in `*.page.tsx` file and should be named as `XyzPage`
- If a file doesn't need to be .tsx, then it should be a .ts file

### Function Naming
Expand Down Expand Up @@ -467,6 +468,8 @@ If the styling is very complicated, you may reach for CSS files, but only if you

Tailwind is inside this project due to the ease of prototyping during development, but you shouldn't have to use it in production. Thereby, it is HIGHLY discouraged but not banned.

Avoid hard-coded / magic styles - reach for Mantine’s theme, which can be imported and used as an object as `{ theme }` from `@/src/lib/theme`.

[Mantine docs](https://mantine.dev/core/package/)

## Typesafety
Expand Down
Loading