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 (13,807 stars) (1,413 forks)user submission
good first issueupstream

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

Tech stack
typescriptreactnextjs
Domain
documentationfull stack
Issue type
feature
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Next.js basicsGit knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Explore using Git commit history to extract last modified times for files. Check if Nextra or Next.js supports custom lastmod logic for sitemaps. Consider implementing a plugin that reads file modification times from Git log. Look at existing solutions like next sitemap integration with Git. Search for related discussions in the Nextra repository or community.