Skip to content
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.

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

feat(ui): add theming #1998

Draft
wants to merge 16 commits into
base: main
Choose a base branch
from
Draft

feat(ui): add theming #1998

wants to merge 16 commits into from

Conversation

RichardKruemmel
Copy link
Contributor

No description provided.

Copy link

vercel bot commented May 7, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
langfuse-cloud ✅ Ready (Inspect) Visit Preview May 17, 2024 3:04pm
langfuse-cloud-us 🔄 Building (Inspect) Visit Preview May 17, 2024 3:04pm

web/src/pages/_app.tsx Show resolved Hide resolved
CONTRIBUTING.md Outdated

At Langfuse, we utilize CSS variables to manage our theme settings across the platform.

Our theming approach is utilizing separate CSS variables for background (--background) and foreground (--foreground) colors. We recommend using HSL values for these colors to enhance user interface consistency and customization capabilities.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd directly reference the color palette used by shadcn/ui as we probably fully rely on that naming/convention. What do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. I added a change explicitly mentioning and linking shadcn theming docs.

Co-authored-by: Marc Klingen <git@marcklingen.com>
- Primary Color: `primary`
- Accents: `primary-accent`
- Selectable Items: `input`
- Link Background: `muted-indigo`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we switch to some template here as well? I though we use some [template]\80 for these

also, other colors (red, yellow, green) missing

1. Global Definitions: Add new CSS variable definitions in the global.css file.
2. Tailwind Configuration: Reflect these new colors in the tailwind.config.js to maintain alignment with Tailwind's utility classes.

### Utility Classes
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd add a couple of more words to each with examples, to me it is not 100% clear what accent, main content etc means. All contributors need to easily understand which colors to apply to which parts of their components

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants