Replace custom tailwindcss-typography with @tailwindcss/typography about ipfs-blog HOT 8 CLOSED

@jdiogopeixoto Makes sense. Let's make sure the main ipfs.io replatform uses the latest tailwind version and we can backfill it from there?

from ipfs-blog.

@zebateira @jdiogopeixoto Do we want to take care of this pre-launch, or backfill it as part of work on the main ipfs.io replatform?

from ipfs-blog.

@jessicaschilling I don't think we should do this pre-launch. We need to update the tailwind version to do this and I'm afraid that some things might break.

from ipfs-blog.

Quick update on this one, I managed to upgrade the tailwind version in the #99. I still think that we should delay this because it requires some changes. It's better to do this with time so we can guarantee that everything works/looks as expected.

from ipfs-blog.

Sounds good.

from ipfs-blog.

Yep agree, the tailwind switch can come later +1

from ipfs-blog.

As discussed sync today — @jdiogopeixoto and @zebateira are working on this with an aim to create as much consistency between the blog and the main IPFS website as possible.

from ipfs-blog.

Ref #257.

from ipfs-blog.