Skip to content

docs: add timestamp metadata - #3118

Open
BrendanBondurant wants to merge 2 commits into
mainfrom
brendan/cs-1141-standardize-frontmatter-fields-globally
Open

docs: add timestamp metadata#3118
BrendanBondurant wants to merge 2 commits into
mainfrom
brendan/cs-1141-standardize-frontmatter-fields-globally

Conversation

@BrendanBondurant

@BrendanBondurant BrendanBondurant commented Jul 27, 2026

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • Documentation
    • Added guidance for using sparse, consistent frontmatter in documentation pages.
    • Documented required and optional metadata fields, timestamp handling, and page-specific exceptions.
    • Enabled timestamp metadata across the documentation site.

Checklist

Open Source AI Manifesto

This project follows the principles of the Open Source AI Manifesto. Please ensure your contribution aligns with its principles.

@mintlify

mintlify Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
wundergraphinc 🟢 Ready View Preview Jul 27, 2026, 4:51 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@coderabbitai

coderabbitai Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

The documentation site now enables timestamp metadata, and its authoring guide documents frontmatter requirements, timestamp handling, and optional fields.

Changes

Documentation timestamp metadata

Layer / File(s) Summary
Enable documentation timestamps
docs-website/docs.json
Adds top-level metadata configuration with timestamps enabled.
Document frontmatter rules
docs-website/CLAUDE.md
Adds guidance for required frontmatter, timestamp behavior, and optional frontmatter fields.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly reflects the main change: adding timestamp metadata to the documentation setup.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs-website/CLAUDE.md`:
- Around line 92-99: Update the frontmatter template in the authoring guidance
so content pages require only title and description; remove icon from the
required fields or clearly label it optional, consistent with the existing
optional-icon guidance.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1ce099e6-9a38-4e3d-99d9-9cf7e787f7fe

📥 Commits

Reviewing files that changed from the base of the PR and between 6d7687e and 1bb0333.

📒 Files selected for processing (2)
  • docs-website/CLAUDE.md
  • docs-website/docs.json

Comment thread docs-website/CLAUDE.md
Comment on lines +92 to +99
Keep frontmatter sparse. Every content page should include:

```yaml
---
title: "..."
description: "..."
icon: ...
---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Do not require icon on every content page.

The existing authoring guidance treats icon as optional, but this template says every page must include it. Remove icon from the required template or explicitly mark it as optional.

Proposed fix
 Keep frontmatter sparse. Every content page should include:

 ---
 title: "..."
 description: "..."
-icon: ...
 ---
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Keep frontmatter sparse. Every content page should include:
```yaml
---
title: "..."
description: "..."
icon: ...
---
Keep frontmatter sparse. Every content page should include:
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs-website/CLAUDE.md` around lines 92 - 99, Update the frontmatter template
in the authoring guidance so content pages require only title and description;
remove icon from the required fields or clearly label it optional, consistent
with the existing optional-icon guidance.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BrendanBondurant I think that's a fair comment

Comment thread docs-website/CLAUDE.md
Comment on lines +92 to +99
Keep frontmatter sparse. Every content page should include:

```yaml
---
title: "..."
description: "..."
icon: ...
---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BrendanBondurant I think that's a fair comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants