Make theming friendlier about graphql-markdown

[edno]

Hi @timuric

Thanks for the feedback.

I 100% agree with you, we need more theming options with less inline CSS.
On the long term roadmap, I am considering a custom Docusaurus plugin that would come with its own theme, offering the swizzling benefits from Docusaurus.

In the meantime, a PR would be very very welcome and appreciated 🙏

[edno]

Hi @timuric

I have time to pick up this request. But before starting working on it, let's clarify the solution.

I can easily add semantic CSS classnames to allow quick customization, eg .type, .argument, .scalar, .nonnull, .list, .enum, .directive, etc. This would allow to fine select eg .badge .nonnull --> badge non-null or a .argument .type --> the link type of arguments.

What do you think?

[edno]

I am thinking about moving away from classname that can quickly become messy. Instead, I'll add a new data attribute like data-gqlmd allowing one to quickly access entities generated by GraphQL-Markdown without messing with other part of Docusaurus.

Possible data attributes:

• data-gqlmd-badge
• data-gqlmd-type
• data-gqlmd-link
• data-gqlmd-deprecated

[edno]

No activity. Closing the issue.