We use @tailwind/typography for most of
our design. This was fine as an Eleventy migratory step, but it’s been
years since then. Let’s do something fun with this.
Standardise fonts across containers (headings/article/p blocks). At
the moment, we have:
Bitter: headings
Noto Sans: everywhere else
If we decide to use a serif font for body text per the experimental
typography branch, we can copy Medium. If we want to stay
sans serif, there are lots of options.
We use @tailwind/typography for most of our design. This was fine as an Eleventy migratory step, but it's been years since then. Let's do something fun with this.
Standardise fonts across containers (headings/article/p blocks). At the moment, we have:
- Bitter: headings
- Noto Sans: everywhere else
If we decide to use a serif font for body text per the experimental `typography` branch, we can copy Medium. If we want to stay sans serif, there are lots of options.
We could also stand to clean up some design. See https://walnut356.github.io/posts/twovec-a-very-silly-container/
eggy
added the frontend label 2024-10-18 14:17:52 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We use @tailwind/typography for most of our design. This was fine as an Eleventy migratory step, but it’s been years since then. Let’s do something fun with this.
Standardise fonts across containers (headings/article/p blocks). At the moment, we have:
If we decide to use a serif font for body text per the experimental
typographybranch, we can copy Medium. If we want to stay sans serif, there are lots of options.We could also stand to clean up some design. See https://walnut356.github.io/posts/twovec-a-very-silly-container/