usually writing CSS or listening to prog (or both).
they/them
unlike a transpilation approach, these custom "units" would work at runtime and be more powerful, e.g. type safety and can tap into media queries
unlike a transpilation approach, these custom "units" would work at runtime and be more powerful, e.g. type safety and can tap into media queries
```
--color-bg: --themes(…);
--space-1: --densities(…);
```
and there was something about component states too.
```
:host {
color: --states(…);
}
```
```
--color-bg: --themes(…);
--space-1: --densities(…);
```
and there was something about component states too.
```
:host {
color: --states(…);
}
```
i guess i could use Nova for personal projects and VSCode for work 🤔
i guess i could use Nova for personal projects and VSCode for work 🤔
same goes for `add_image` and `add_script`
same goes for `add_image` and `add_script`
the best place for authoring CSS continues to be a `.css` file
the best place for authoring CSS continues to be a `.css` file
i've been obsessed with this band for the last few months
i've been obsessed with this band for the last few months
i think we're still in early stages with containers, despite good support for the base feature set
i think we're still in early stages with containers, despite good support for the base feature set
these containers get shuffled around depending on the viewport size.
individual components have no knowledge of the overall page layout. no media queries inside components.
these containers get shuffled around depending on the viewport size.
individual components have no knowledge of the overall page layout. no media queries inside components.
can't imagine going back to pen & paper. i don't think i even own a notebook (or a pen 😂)
can't imagine going back to pen & paper. i don't think i even own a notebook (or a pen 😂)
i'm aware that navigation is a totally different thing from a "menu"
i'm aware that navigation is a totally different thing from a "menu"