Closed kelvinsjk closed 2 years ago
Hey @kelvinsjk!
When you say expose it what you do you mean exactly? You can pull the tailwind.config.cjs
file into your own config and re-export it like so:
// tailwind.config.cjs
const config = require('@svelteness/kit-docs/tailwind.config.cjs');
module.exports = {
...config,
content: [
"src/**/*.svelte",
"./node_modules/@svelteness/kit-docs/client/kit-docs/**/*.svelte",
// Add this instead if you're using the default theme.
"'./node_modules/@svelteness/kit-docs/client/**/*.svelte'"
]
};
Make sure to remove this following lines from your main layout file:
- import '@svelteness/kit-docs/client/styles/normalize.css';
- import '@svelteness/kit-docs/client/styles/theme.css';
Docs mentions this at the following links:
Did I misunderstand the question?
It seems like kit-docs is using tailwind under the hood.
Is it be possible to expose it so that custom svelte components get tailwind classes support out of the box (and we are able to add tailwind plugins like using markdown-it plugins via the
configureParser
option inkitDocsPlugin
)?Or is it something we should configure on top of kit-docs?
P.S.: Love the project, keep up the great work.