Uh oh!
There was an error while loading. Please reload this page.
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. |
atinux
commented
Jun 23, 2022
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 |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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>
Tahul
commented
Jun 23, 2022
yaaaay! 🚀 Pushing that really soon! |
Tahul
commented
Jun 23, 2022
@atinux ; I renamed WDYT about merging this feature? |
atinux
commented
Jun 23, 2022
I would like to have also a review from @farnabaz |
atinux
commented
Jun 23, 2022
I think you can also rename the composable filename @Tahul |
…into feat/document-driven
…#1279) Co-authored-by: Sébastien Chopin <seb@nuxtjs.com>
❓ Type of change
📚 Description
This PR adds
documentDrivenas 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: