vercel / vercel/next-learn

Docs- Chapter 8: No explanation of how dashboard is dynamic

Open
#910 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
4.8k
Forks
2.2k
PR merge metrics
No merged PRs in 30d

Description

In Chapter 7, there is a concern highlighted:

"By default, Next.js prerenders routes to improve performance; this is called Static Rendering. So if your data changes, it won't be reflected in your dashboard."

However, in Chapter 8, it suddenly states:

"The dashboard application we're building is dynamic."

There is no explanation provided on why or how the dashboard is dynamic.

At the beginning of Chapter 8, the topics listed are supposed to cover "different approaches to make your dashboard dynamic." However, I couldn't find this explanation anywhere in the chapter.

Note: I last tried with "next": "15.0.0-canary.56", where the dashboard was not dynamic. I haven't checked the current behavior yet, but prior to the merge of pull request #764, it was dynamic since noStore() was used in the database query function. This was removed in that merge.

Could you please clear that?
Thank you!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Chapter 7 and Chapter 8 documentation linked in the issue, then review pull request #764 and the referenced noStore() change. Confirm the dashboard's current rendering behavior and update Chapter 8 so it explains why the dashboard is dynamic and how the listed approaches affect it.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.