You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
With the current implementation with the tailwind utility classes attached to the elements, it is quite a challenge to override the default properties with custom styles. While the default styles are really nice already, I personally feel like it would be a better developer experience if there would be an easy way to edit the styles. While Tailwind is cool for individual implementations, it has limits, if used as a template.
Describe the solution you'd like
I would recommend adding custom nextra pre-fixed class names to all components and remove the tailwind classes. So each element should have only one instead of many CSS classes (in some case might also have more than only one but it should be generic classes and not utility classes)
Describe alternatives you've considered
The implementation could use the Tailwind CSS variables for the styling (to be discussed) so it would integrate well with current implementations with possible modifications.
Additional context
Would be a breaking Change. Possibly could be first integrated as a separate Theme, but should soon be merged to be the main theme again to reduce double maintenance efforts.
The text was updated successfully, but these errors were encountered:
With the current implementation with the tailwind utility classes attached to the elements, it is quite a challenge to override the default properties with custom styles.
While Tailwind is cool for individual implementations, it has limits, if used as a template.
nextra-theme-docs / blog are not a template but themes
So each element should have only one instead of many CSS classes (in some case might also have more than only one but it should be generic classes and not utility classes)
Sorry, but I am not interested in spending developer hours on these refactoring, you can always copy official themes and fully override them on your needs
Hey @dimaMachina, thank you so much for your answer!
That seems absolutely reasonable. I was wondering, if someone would do such a refactoring (replace Tailwind utility with nextra CSS selectors) would you accept it as a PR?
Is your feature request related to a problem? Please describe.
With the current implementation with the tailwind utility classes attached to the elements, it is quite a challenge to override the default properties with custom styles. While the default styles are really nice already, I personally feel like it would be a better developer experience if there would be an easy way to edit the styles. While Tailwind is cool for individual implementations, it has limits, if used as a template.
Describe the solution you'd like
I would recommend adding custom
nextra
pre-fixed class names to all components and remove the tailwind classes. So each element should have only one instead of many CSS classes (in some case might also have more than only one but it should be generic classes and not utility classes)Describe alternatives you've considered
The implementation could use the Tailwind CSS variables for the styling (to be discussed) so it would integrate well with current implementations with possible modifications.
Additional context
Would be a breaking Change. Possibly could be first integrated as a separate Theme, but should soon be merged to be the main theme again to reduce double maintenance efforts.
The text was updated successfully, but these errors were encountered: