Make Nuxt/Content Available in Production
See original GitHub issueIs your feature request related to a problem? Please describe.
No way to edit content in production without another CMS based project.
Describe the solution you’d like
- Login using repository credentials (oauth)
- Edit in preview/edit mode. E.g. reload the page if
?edit=true
- Make a commit/PR
Describe alternatives you’ve considered
Netlify CMS does some really cool things here.
Additional context
Preview and edit API for nuxtjs isn’t clearly documented as of writing. So maybe that can be extended before doing this.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
npm - @nuxt/content pages not found in production mode
Hello, I got a problem with nuxt/content on my project when i run npm run build && npm run start . You have...
Read more >Configuration - Nuxt Content
Enables the surround binding, making it globally accessible. globals, Object | Boolean, A list of globals to be made available globally. layoutFallbacks, string ......
Read more >Content directory - Nuxt
Empower your Nuxt application with @nuxt/content module where you can write in a content/ directory and fetch your Markdown, JSON, YAML and CSV...
Read more >uil:moon - Nuxt Content
Write pages in markdown, use Vue components and enjoy the power of Nuxt with a blazing fast developer experience.
Read more >Commands and Deployment - Nuxt
nuxt dev - Launch the development server. · nuxt build - Build and optimize your application with webpack for production. · nuxt start...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Spunkie thank you for your feedback, we are actually in the process with @Atinux of defining the roadmap for V2. I reopened the issue so we can keep discussing about the implementation 😊
Ya, I don’t see a reason this issue should be closed. The code’s not done or implemented publicly on any branch or pr. The publicly accessible roadmap does not mention this issue anywhere, and seems semi abandoned in general.
From the public’s perspective this comes off as sweeping this issue under a rug.