From fceaae301209c695844f988e7ab6344842c62d50 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 13 Aug 2026 23:48:11 +0000 Subject: [PATCH 1/4] docs: document lastUpdatedDate frontmatter for last modified footer --- es/organize/pages.mdx | 11 +++++++++++ fr/organize/pages.mdx | 11 +++++++++++ organize/pages.mdx | 11 +++++++++++ organize/settings-reference.mdx | 2 ++ zh/organize/pages.mdx | 11 +++++++++++ 5 files changed, 46 insertions(+) diff --git a/es/organize/pages.mdx b/es/organize/pages.mdx index 89229b8ea7..717e1bc888 100644 --- a/es/organize/pages.mdx +++ b/es/organize/pages.mdx @@ -275,6 +275,17 @@ Muestra una marca de tiempo «Última modificación el [fecha]» en todas las p En despliegues respaldados por GitHub o GitLab, la fecha mostrada es la del último commit de Git que modificó el archivo de origen de la página. Si no hay una fecha de commit de Git disponible, se usa la marca de tiempo del despliegue más reciente. Esto ocurre, por ejemplo, en despliegues que no están conectados a GitHub o GitLab. +Para establecer la fecha mostrada de forma explícita, usa el campo `lastUpdatedDate` del frontmatter. Esto resulta útil cuando el historial de commits de Git no refleja cuándo se actualizó realmente el contenido, por ejemplo, en documentación sincronizada desde otro sistema. Usa un valor de solo fecha o una marca de tiempo ISO 8601. + +```yaml +--- +title: "Título de la página" +lastUpdatedDate: 2026-07-22 +--- +``` + +La fecha mostrada sigue esta precedencia: el frontmatter `lastUpdatedDate`, luego la fecha del último commit de Git y, por último, la marca de tiempo del despliegue más reciente. Los valores `lastUpdatedDate` no válidos o vacíos se reemplazan por la fecha del commit de Git. + Para anular la configuración global de la marca de tiempo en una página individual, usa el campo `timestamp` del frontmatter. Usa este campo para mostrar u ocultar las marcas de tiempo en páginas específicas. ```yaml diff --git a/fr/organize/pages.mdx b/fr/organize/pages.mdx index d67761b939..c076ef1f9c 100644 --- a/fr/organize/pages.mdx +++ b/fr/organize/pages.mdx @@ -274,6 +274,17 @@ Affichez la mention « Dernière modification le [date] » sur toutes les pages Pour les déploiements adossés à GitHub ou GitLab, la date affichée correspond à celle du dernier commit git ayant modifié le fichier source de la page. Si aucune date de commit git n’est disponible, par exemple sur des déploiements qui ne sont pas connectés à GitHub ou GitLab, l’horodatage du dernier déploiement est utilisé par défaut. +Pour définir explicitement la date affichée, utilisez le champ de frontmatter `lastUpdatedDate`. Cela est utile lorsque l’historique des commits git ne reflète pas la date réelle de mise à jour du contenu, par exemple pour de la documentation synchronisée depuis un autre système. Utilisez une valeur date seule ou un horodatage ISO 8601. + +```yaml +--- +title: "Titre de la page" +lastUpdatedDate: 2026-07-22 +--- +``` + +La date affichée suit l’ordre de priorité suivant : le frontmatter `lastUpdatedDate`, puis la date du dernier commit git, puis l’horodatage du dernier déploiement. Les valeurs `lastUpdatedDate` non valides ou vides sont ignorées au profit de la date du commit git. + Pour remplacer le paramètre global d’horodatage pour une page individuelle, utilisez le champ de frontmatter `timestamp`. Utilisez ce champ pour afficher ou masquer les horodatages sur des pages spécifiques. ```yaml diff --git a/organize/pages.mdx b/organize/pages.mdx index 8fefcc647e..ea7d3a607a 100644 --- a/organize/pages.mdx +++ b/organize/pages.mdx @@ -247,6 +247,17 @@ Show a "Last modified on [date]" timestamp on all pages by enabling `metadata.ti For deployments backed by GitHub or GitLab, the displayed date is the date of the last Git commit that modified the page's source file. If a Git commit date isn't available, the date falls back to the most recent deployment timestamp. +To set the displayed date explicitly, use the `lastUpdatedDate` frontmatter field. This is useful when the Git commit history doesn't reflect when the content was actually updated, such as for docs synced from another system. Use a date-only value or an ISO 8601 timestamp. + +```yaml +--- +title: "Page title" +lastUpdatedDate: 2026-07-22 +--- +``` + +The displayed date uses the following precedence: `lastUpdatedDate` frontmatter, then the last Git commit date, then the most recent deployment timestamp. Invalid or empty `lastUpdatedDate` values fall through to the Git commit date. + To override the global timestamp setting for an individual page, use the `timestamp` frontmatter field. Use this field to show or hide timestamps on specific pages. ```yaml diff --git a/organize/settings-reference.mdx b/organize/settings-reference.mdx index bba26a987b..1e4defea10 100644 --- a/organize/settings-reference.mdx +++ b/organize/settings-reference.mdx @@ -709,6 +709,8 @@ Global page metadata settings. Display a last-modified date on all pages. For deployments backed by GitHub or GitLab, the date reflects the last Git commit that touched a page's source file. It falls back to the most recent deployment timestamp if a Git commit date isn't available. +Set the `lastUpdatedDate` frontmatter field on a page to override the automatic date. See [Pages](/organize/pages#last-modified-timestamp) for details. + **Type:** boolean **Default:** `false` diff --git a/zh/organize/pages.mdx b/zh/organize/pages.mdx index 2384f6c4e4..b107876d13 100644 --- a/zh/organize/pages.mdx +++ b/zh/organize/pages.mdx @@ -274,6 +274,17 @@ keywords: ['配置', '设置', '入门指南'] 对于由 GitHub 或 GitLab 支持的部署，显示的日期是最后一次修改页面源文件的 Git 提交日期。如果无法获取 Git 提交日期（例如部署未连接到 GitHub 或 GitLab），日期将回退为最近一次部署的时间戳。 +若要显式设置显示的日期，请使用 frontmatter 中的 `lastUpdatedDate` 字段。当 Git 提交历史无法反映内容的真实更新时间时（例如从其他系统同步而来的文档），这一字段非常有用。可使用纯日期值或 ISO 8601 时间戳。 + +```yaml +--- +title: "页面标题" +lastUpdatedDate: 2026-07-22 +--- +``` + +显示日期的优先级如下：先使用 frontmatter 中的 `lastUpdatedDate`，其次使用最后一次 Git 提交日期，最后使用最近一次部署的时间戳。当 `lastUpdatedDate` 的值无效或为空时，会回退为 Git 提交日期。 + 你可以在单个页面上使用 frontmatter 中的 `timestamp` 字段来覆盖全局时间戳设置。使用该字段可在特定页面上选择性地显示或隐藏时间戳。 ```yaml From 233220b8fa752000982cf50101b48fcf8e35ee38 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 13 Aug 2026 23:50:04 +0000 Subject: [PATCH 2/4] docs: mirror lastUpdatedDate override note to translated settings reference --- es/organize/settings-reference.mdx | 2 ++ fr/organize/settings-reference.mdx | 2 ++ zh/organize/settings-reference.mdx | 2 ++ 3 files changed, 6 insertions(+) diff --git a/es/organize/settings-reference.mdx b/es/organize/settings-reference.mdx index 213dd11b7a..5be3d04b01 100644 --- a/es/organize/settings-reference.mdx +++ b/es/organize/settings-reference.mdx @@ -713,6 +713,8 @@ Configuración global de metadatos de página. Muestra una fecha de última modificación en todas las páginas. En despliegues respaldados por GitHub o GitLab, la fecha refleja el último commit de git que modificó el archivo de origen de cada página, y recurre a la marca de tiempo del despliegue más reciente cuando no hay una fecha de commit de git disponible. +Establece el campo `lastUpdatedDate` en el frontmatter de una página para anular la fecha automática. Consulta [Páginas](/es/organize/pages#last-modified-timestamp) para más detalles. + **Tipo:** boolean **Predeterminado:** `false` diff --git a/fr/organize/settings-reference.mdx b/fr/organize/settings-reference.mdx index 12261e67d4..bc00e2f8e2 100644 --- a/fr/organize/settings-reference.mdx +++ b/fr/organize/settings-reference.mdx @@ -713,6 +713,8 @@ Paramètres globaux de métadonnées de page. Affiche une date de dernière modification sur toutes les pages. Pour les déploiements adossés à GitHub ou GitLab, la date reflète le dernier commit git ayant modifié le fichier source de chaque page, et utilise par défaut l’horodatage du dernier déploiement lorsqu’aucune date de commit git n’est disponible. +Définissez le champ `lastUpdatedDate` dans le frontmatter d’une page pour remplacer la date automatique. Voir [Pages](/fr/organize/pages#last-modified-timestamp) pour plus de détails. + **Type :** boolean **Défaut :** `false` diff --git a/zh/organize/settings-reference.mdx b/zh/organize/settings-reference.mdx index 88fff90c64..4378b6cb9d 100644 --- a/zh/organize/settings-reference.mdx +++ b/zh/organize/settings-reference.mdx @@ -478,6 +478,8 @@ keywords: ["docs.json", "schema", "参考", "配置", "所有设置", "属性", 在所有页面上显示最后修改日期。对于由 GitHub 或 GitLab 支持的部署，日期反映最后一次修改页面源文件的 git 提交时间；当无法获取 git 提交日期时，将回退为最近一次部署的时间戳。 +在页面 frontmatter 中设置 `lastUpdatedDate` 字段可覆盖自动获取的日期。详情请参见[页面](/zh/organize/pages#last-modified-timestamp)。 + **类型：** boolean **默认值：** `false` From 310da1c2354916f72469194c2c9d6fec7e8761ba Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Fri, 14 Aug 2026 09:41:05 -0700 Subject: [PATCH 3/4] Apply suggestions from code review Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> --- organize/pages.mdx | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/organize/pages.mdx b/organize/pages.mdx index ea7d3a607a..722ef57027 100644 --- a/organize/pages.mdx +++ b/organize/pages.mdx @@ -247,16 +247,8 @@ Show a "Last modified on [date]" timestamp on all pages by enabling `metadata.ti For deployments backed by GitHub or GitLab, the displayed date is the date of the last Git commit that modified the page's source file. If a Git commit date isn't available, the date falls back to the most recent deployment timestamp. -To set the displayed date explicitly, use the `lastUpdatedDate` frontmatter field. This is useful when the Git commit history doesn't reflect when the content was actually updated, such as for docs synced from another system. Use a date-only value or an ISO 8601 timestamp. +To set a specific date, use the `lastUpdatedDate` frontmatter field. This is useful when the Git commit history doesn't reflect when the content was updated. Use a date-only value or an ISO 8601 timestamp. -```yaml ---- -title: "Page title" -lastUpdatedDate: 2026-07-22 ---- -``` - -The displayed date uses the following precedence: `lastUpdatedDate` frontmatter, then the last Git commit date, then the most recent deployment timestamp. Invalid or empty `lastUpdatedDate` values fall through to the Git commit date. To override the global timestamp setting for an individual page, use the `timestamp` frontmatter field. Use this field to show or hide timestamps on specific pages. From d0e82b625da3790463ac2307653968a9764e7112 Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Fri, 14 Aug 2026 10:14:35 -0700 Subject: [PATCH 4/4] =?UTF-8?q?=F0=9F=92=85?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- organize/pages.mdx | 24 +++++++++++------------- 1 file changed, 11 insertions(+), 13 deletions(-) diff --git a/organize/pages.mdx b/organize/pages.mdx index 6901aef455..94a09ce608 100644 --- a/organize/pages.mdx +++ b/organize/pages.mdx @@ -237,7 +237,7 @@ keywords: ['configuration', 'setup', 'getting started'] ## Last modified timestamp -Show a "Last modified on [date]" timestamp on all pages by enabling `metadata.timestamp` in your [global settings](/organize/settings-seo#metadata). +To display a "Last modified on [date]" timestamp on all pages, enable `metadata.timestamp` in your [global settings](/organize/settings-seo#metadata). This timestamp uses the date of the last Git commit that modified the page's source file. ```json docs.json "metadata": { @@ -245,31 +245,29 @@ Show a "Last modified on [date]" timestamp on all pages by enabling `metadata.ti } ``` -Mintlify determines the displayed date in the following order: - -1. The `lastUpdatedDate` frontmatter field, if set on the page. -2. For deployments backed by GitHub or GitLab, the date of the last Git commit that modified the page's source file. -3. The most recent deployment timestamp. - -To display a specific date instead of the Git commit date, set the `lastUpdatedDate` frontmatter field. Use this field when your Git history doesn't reflect when the content changed, such as content imported or synced from another system. +To override the global timestamp setting for an individual page, use the `timestamp` frontmatter field. Use this field to show or hide timestamps on specific pages. ```yaml --- title: "Page title" -lastUpdatedDate: "2026-08-13" +timestamp: false --- ``` -To set a specific date, use the `lastUpdatedDate` frontmatter field. This is useful when the Git commit history doesn't reflect when the content was updated. Use a date-only value or an ISO 8601 timestamp. +If you set `timestamp: true`, the page always shows the timestamp even if the global setting is `false`. If you set `timestamp: false`, the page hides the timestamp even if the global setting is `true`. +To display a specific date instead of the Git commit date for an individual page, use the `lastUpdatedDate` frontmatter field. Use this field when your Git history doesn't reflect when the content changed, such as content imported or synced from another system. Use a date-only value or an ISO 8601 timestamp. -To override the global timestamp setting for an individual page, use the `timestamp` frontmatter field. Use this field to show or hide timestamps on specific pages. ```yaml --- title: "Page title" -timestamp: false +lastUpdatedDate: "2026-08-13" --- ``` -If you set `timestamp: true`, the page always shows the timestamp even if the global setting is `false`. If you set `timestamp: false`, the page hides the timestamp even if the global setting is `true`. +Mintlify determines the displayed date in the following order: + +1. The `lastUpdatedDate` frontmatter field, if set on the page. +2. For deployments backed by Git, the date of the last commit that modified the page's source file. +3. The most recent deployment timestamp.