Use the new logo #750
Use the new logo #750
Conversation
vladmoroz
commented
Oct 21, 2024
•
vladmoroz
commented
- New logo and favicons
- Tweaked homepage
Netlify deploy preview |
github-actions
bot
added
the
PR: out-of-date
github-actions
bot
removed
the
PR: out-of-date
| :root { | ||
| --color-content: #fff; | ||
| --color-background: oklch(98% 0.25% 264); | ||
| --color-foreground: oklch(21% 2% 264); | ||
| --color-selection: oklch(80% 0.2 264 / 60%); | ||
| --color-gray: oklch(12.7% 6% 264 / 67%); | ||
| --color-link: oklch(47% 50% 264); | ||
| --color-border: oklch(20% 12% 264 / 25%); | ||
| --color-gridline: oklch(91.6% 1% 264); | ||
|
|
||
| @media (prefers-color-scheme: dark) { | ||
| --color-content: #000; | ||
| --color-background: #000; | ||
| --color-foreground: oklch(90% 2% 264); | ||
| --color-selection: oklch(50% 0.2 264 / 80%); | ||
| --color-gray: oklch(90% 6% 264 / 70%); | ||
| --color-link: oklch(69% 50% 264); | ||
| --color-border: oklch(90% 12% 264 / 35%); | ||
| --color-gridline: oklch(24% 1% 264); | ||
| } | ||
| } |
There was a problem hiding this comment.
The functional colours are provisional, it's likely I'll end up doing a normal Radix-style palette once there is a bit more interactive UI to work with
| @@ -38,6 +38,9 @@ module.exports = { | |||
| }, | |||
| ], | |||
| '@typescript-eslint/no-redeclare': 'off', | |||
|
|
|||
| // We LOVE non-breaking spaces here | |||
| 'no-irregular-whitespace': 'off', | |||
There was a problem hiding this comment.
Wouldn't setting { skipJSXText: true, skipStrings: true } be enough?
| {description} | ||
| </h1> | ||
| <p className="text-color-gray mb-4 text-pretty 2xl:text-lg"> | ||
| From the creators of Radix, Floating UI, and MUI. |
There was a problem hiding this comment.
| From the creators of Radix, Floating UI, and MUI. | |
| From the creators of Radix, Floating UI, and Material UI. |
| import { Metadata } from 'next'; | ||
| import { GoogleAnalytics } from 'docs/src/components/GoogleAnalytics'; | ||
| import * as React from 'react'; |
There was a problem hiding this comment.
We have a convention to import React first.
| @@ -0,0 +1,19 @@ | |||
| @layer components { | |||
There was a problem hiding this comment.
So what's wrong with CSS modules after all? Are we going to have plain CSS, CSS modules, and Tailwind at the same time, or do you want to get rid of modules completely?
|
Side note: could you prefix your PR titles with the main tag ( |
