flndrn
73d8aa9657
branding: finish Dolt→Briven rename, clean up studio/auth/CLI layers
|
il y a 2 mois | |
|---|---|---|
| .. | ||
| README.md | il y a 3 mois | |
| code.css | il y a 3 mois | |
| editor.css | il y a 3 mois | |
| focus.css | il y a 3 mois | |
| globals.css | il y a 2 mois | |
| graphiql-base.css | il y a 3 mois | |
| grid.css | il y a 3 mois | |
| markdown-preview.css | il y a 3 mois | |
| monaco.css | il y a 3 mois | |
| react-data-grid-logs.css | il y a 3 mois | |
| reactflow.css | il y a 3 mois | |
| storage.css | il y a 3 mois | |
| stripe.css | il y a 3 mois | |
| ui.css | il y a 3 mois | |
README.md
Styles
When to write custom styles
Tailwind should be sufficient to cover the majority of styling needs. We typically only write custom styles here in the event where we're working with an external library and we need to override some styles (e.g Monaco, or even our own UI library).
Ideally, keep custom styling here to a minimum, use tailwind directly in the pages and components where possible, so that we have less code to maintain.
If you're writing custom styles
Group custom styles into separate stylesheets based on their context. For styles which are generic and global, we can write them in main.scss.