New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(document-driven): add document-driven as a @nuxt/content feature #1279
Conversation
✅ Deploy Preview for nuxt-content ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Beautiful work @Tahul ❤️ I think we could go with const { page, navigation, surround, globals } = useContent() And warn to say that this composable is available only with |
Co-authored-by: Sébastien Chopin <seb@nuxtjs.com>
Co-authored-by: Sébastien Chopin <seb@nuxtjs.com>
Co-authored-by: Sébastien Chopin <seb@nuxtjs.com>
yaaaay! 🚀 Pushing that really soon! |
@Atinux ; I renamed WDYT about merging this feature? |
I would like to have also a review from @farnabaz |
I think you can also rename the composable filename @Tahul |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
…into feat/document-driven
…#1279) Co-authored-by: Sébastien Chopin <seb@nuxtjs.com>
❓ Type of change
📚 Description
This PR adds
documentDriven
as a new feature for the module.This feature basically is a more generic approach than
@docus/base
.It offers more flexibility while preserving the same features as a default.
Here is a preview from the config object:
These datas becomes globally available via the
useDocumentDriven()
composable:I updated the documentation with new pages:
This PR also deeply refactors the
playground/
andtest/
directories.You can now run scoped playground with these commands:
Same applies to test:
Any feedback to the API or implementation is more than welcome!
📝 Checklist
TODO: