Replace custom tailwindcss-typography with @tailwindcss/typography #32

New Issue

2026-10-05T05:10:32+02:00

adam commented

2026-10-05 05:10:32 +02:00

Now that there's an official Tailwind typography plugin, let's move the blog's current use of tailwindcss-typography over to the newer replacement. May not be necessary for initial site launch, but should definitely happen in conjunction with any visual rebranding work.

Now that there's an official [Tailwind typography plugin](https://github.com/tailwindlabs/tailwindcss-typography), let's move the blog's current use of `tailwindcss-typography` over to the newer replacement. May not be necessary for initial site launch, but should definitely happen in conjunction with any visual rebranding work.

adam closed this issue

2026-10-05 05:10:32 +02:00

adam commented

2026-10-05 05:10:33 +02:00

@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?

@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?

adam commented

2026-10-05 05:10:34 +02:00

@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.

@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.

adam commented

2026-10-05 05:10:34 +02:00

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

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

adam commented

2026-10-05 05:10:35 +02:00

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.

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.

adam commented

2026-10-05 05:10:36 +02:00

Sounds good.

Sounds good.

adam commented

2026-10-05 05:10:37 +02:00

Yep agree, the tailwind switch can come later +1

Yep agree, the tailwind switch can come later +1

adam commented

2026-10-05 05:10:37 +02:00

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.

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.

adam commented

2026-10-05 05:10:38 +02:00

Ref https://github.com/ipfs/ipfs-blog/pull/257.

Ref https://github.com/ipfs/ipfs-blog/pull/257.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/ipfs-blog#32