Proposal to change @tailwindcss/typography configuration from JS definition to CSS declaration

[jubalm]

I'm really glad to see TailwindCSS shifting from JavaScript-based configuration to more CSS-driven declarations in v4. I have notice that some plugins may not be on the same spirit (yet) and it would, especially for official plugins, make sense to follow suit.

In particular, I’d love to see @tailwindcss/typography eventually support configuration via CSS variables. I don't think i've seen it in the roadmap, but I think it could be a great improvement, especially for projects already adapting their design systems around v4.

Use-case example:

@theme {
  --color-foreground: oklch(0.51 0 0 / 1);
  /* Allow prose styles to inherit from existing design tokens */
  --tw-prose-body: var(--color-foreground);
}

[craigrileyuk]

Why post an issue for a different repo and even include a link to the repo you should have posted on in the first place?

[wongjn]

Feature requests are redirected to this repo's discussions, as a centralized place. See the .github/ISSUE_TEMPLATE/config.yml file in the tailwindcss-typography repo:

- name: Feature Request
  url: https://github.com/tailwindlabs/tailwindcss/discussions/new?category=ideas
  about: 'Suggest any ideas you have using our discussion forums.'

[jubalm]

Wes this response directed at me or @wongjn? If I recall correctly, I was in the @tailwindcss/typography repository when I created the issue. I selected "Feature Request" from the popup, but it ended up creating a discussion in this repo instead. Apologies for the confusion

[wongjn]

I think you're fine @jubalm, I believe this feature request is in the right place. There just seems to be some slight misunderstanding :)