Add ability to disable prerender of content
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.7k
- Forks
- 746
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe
I'm trying to make a website that can be modified without rebuilding the project.
Describe the solution you'd like
A way to define that the content should be lazily parsed and cached instead of statically prerendered.
As an example have the markdown content in a database and cache the parsed version in redis.
Describe alternatives you've considered
I didn't find any up to date libraries as alternatives that would let me do something like this. So the only alternative would be to write it myself.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how this Nuxt Content module currently prerenders and parses Markdown content; the issue names no specific files, tests, or entry points. Define what configuration should disable static prerendering, how content is loaded and lazily parsed, and how a parsed result could be cached in Redis, then verify that database-backed content can change without rebuilding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown, nuxtjs, redis, typescript
- Domain
- backend, content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100