shuding/nextra

How to keep track of correct last modified times for pages

Open

#1,966 opened on Jun 13, 2023

View on GitHub
 (3 comments) (0 reactions) (0 assignees)TypeScript (1,413 forks)user submission
good first issueupstream

Repository metrics

Stars
 (13,807 stars)
PR merge metrics
 (Avg merge 6d 16h) (3 merged PRs in 30d)

Description

We are using Nextra + Next Sitemap to update our sitemap, but noticed that the lastmod times are always the last time a deploy happened, rather than the last time the page really had any changes made to it. Apart from the sitemap, the pages themselves also say they were updated very recently, even when that's not truly the case.

I wanted to ask if the community has any solutions for dealing with this problem, other than manually updating it in each page's metadata? Is there a way to hook into Git commit history for example?

Contributor guide

Research direction
Investigate using git log at build time to extract last modified dates for each page file. Look into next sitemap custom transformers or pre processing scripts to inject those dates into page metadata.
Tech stack
typescriptreactnextjsnodejs
Domain
documentation
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNext.jsTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65