shuding/nextra

How to keep track of correct last modified times for pages

Open

Aperta il 13 giu 2023

Vedi su GitHub
 (3 commenti) (0 reazioni) (0 assegnatari)TypeScript (13.807 star) (1413 fork)user submission
good first issueupstream

Descrizione

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?

Guida contributor

Tech stack
typescriptreactnextjs
Dominio
documentationfull stack
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-2 days
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
fresh
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
Next.js basicsGit knowledge
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
60
Direzione di ricerca
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.