I love how you've kept this setup very vanilla, it was useful to cross-reference my setup. I'm just leaving this as a piece of learning, and not really as a feature request.

One thing I've learnt is that JIT won't pick up my classes in WYSIWYG by default, it might be a interesting to add a basic src/ckeditor.css and then add this:

# tailwind.config.js
module.exports = {
  content: [
    "**/*.twig",
    "src/ckeditor.css",
   ...

Or otherwise i'm interested to see how you approach this situation.

Comments

sime created an issue. See original summary.

sime’s picture

sime
any/any
Location Melbourne
commented
Title: Thoughts on JIT scanning » Thoughts on JIT scanning ckeditor
opdavies’s picture

opdavies
He/him
Primary language English
Location Wales
commented
Status: Active » Postponed (maintainer needs more info)

Hi @sime.

Thanks for the suggestion, but what would you add to the src/ckeditor.css file to make it work with Tailwind?

If it's custom styling for that theme, people can add that themselves when they create their theme.

If it's something generic, it could be added to this starter kit, but I don't see how at the moment.

sime’s picture

sime
any/any
Location Melbourne
commented

I wanted to use classes in CKEditor which were not being used in the theme. Tailwind never saw these classes and would not compile them. So I'm wondering how other people deal with this.

andreas schwarz’s picture

andreas schwarz commented

Hello @sime,

One solution is to work with Storybook and pre-design and test the styles outside of Drupal.
So Tailwind can compile them and the Tailwind classes you want to make available to CKEditor are available.