Disable CSS reset via config or other means #1518
Replies: 2 comments 3 replies
-
I'm not 100% certain it's only, the CSS reset, but what lead me to believe it was the reset was that I could add the following styles to get my inputs looking how they did in 0.22.4 and in other applications. input {
border: solid;
} Whereas if I add the same for inputs within vp-doc, I get a result that requires a bit more styling to get back to the same result: .vp-doc input {
border: solid;
} I have found myself needing to target selectors within vp-doc as well though, so it really could be a mix of both. @brc-dd also mentioned https://whyframe.dev/docs/integrations/vitepress earlier in Discord, so that could be a solid solution. |
Beta Was this translation helpful? Give feedback.
-
I came here looking for a fix, and stumbled upon this thread, I'm having the exact same issue, it would be amazing to be able to pass a class or attribute to a wrapper for my lib demos, rather than overriding vitepress styling on every component :) |
Beta Was this translation helpful? Give feedback.
-
I've recently been documenting a UI library using Vitepress and have found myself having to override a number of styles so that my components look the same as in the rest of my applications. I also noticed this only occurred after switching from 0.22.4 to 1.0.0-alpha.21.
It would be extremely useful to be able to either disable the CSS reset via a config property, or even by wrapping sections with a particular tag. Is that something that would be possible?
That aside, it's an awesome tool for documentation.
Beta Was this translation helpful? Give feedback.
All reactions