Add lastUpdated frontmatter to comparison pages

Open Beginner friendly
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
markdown
Domain
documentation

Research direction

Open src/content/docs/vs/hasura.mdx and src/content/docs/vs/postgrest.mdx and inspect their frontmatter and manual pricing-date disclaimers. Add the lastUpdated field to both pages, refresh the body dates, and confirm the dates are consistent with the updated frontmatter.

Written by the indexing model from the issue text.

Description

The comparison pages (vs/hasura.mdx, vs/postgrest.mdx) have manual date disclaimers in the body text (e.g. "Pricing information accurate as of February 2026") but no lastUpdated frontmatter field.

Adding lastUpdated to frontmatter would:

  • Enable Starlight's automatic "Last updated" footer
  • Make staleness visible at a glance
  • Be sortable in content collections

Also a good time to refresh the dates since they're now 1-2 months old.

Files: src/content/docs/vs/hasura.mdx, src/content/docs/vs/postgrest.mdx
Effort: ~10 minutes

Dominant language
MDX
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fraiseql/fraiseql-docs

All issues in fraiseql/fraiseql-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.