MKT-66: Add blog MVP specification document

[ghost]

Related GitHub Issue

Linear issue: MKT-66

Roo Code Task Context (Optional)

View task on Roo Code Cloud

Description

This PR adds a comprehensive specification document for the blog MVP at roocode.com/blog. The spec captures all confirmed product decisions to enable implementation without further clarification.

Key decisions documented:

• Routes: /blog index and /blog/[slug] post pages
• Content source: Markdown files in content/blog/ directory
• Frontmatter schema: Required fields including publish_date (YYYY-MM-DD) and publish_time_pt (h:mmam/pm format)
• Publish gating: Time-based visibility using Pacific Time, no deploy required for scheduled posts
• Rendering: Dynamic SSR on Node.js runtime (required for request-time gating)
• Display: Date-only display (no time shown to users)
• Markdown: Standard Markdown only, no raw HTML
• Slug rules: ^[a-z0-9]+(?:-[a-z0-9]+)*$ with uniqueness validation
• Substack syndication: Checklist for syndicating to blog.roocode.com
• Containment rules: Changes scoped to /blog routes + minimal nav/sitemap glue

Test Procedure

1. Review the spec document at apps/web-roo-code/docs/blog.md
2. Verify all decisions from MKT-66 are captured
3. Confirm the spec is clear enough for implementation without ambiguity

Pre-Submission Checklist

• Issue Linked: This PR is linked to Linear issue MKT-66
• Scope: Changes are focused - adds only the spec document
• Self-Review: Reviewed content against all confirmed decisions in MKT-66
• Testing: N/A - documentation only
• Documentation Impact: This IS the documentation
• Contribution Guidelines: Reviewed

Screenshots / Videos

N/A - documentation only

Documentation Updates

• This PR IS the documentation update (spec document for blog implementation)

Additional Notes

This spec document is a prerequisite for implementation issues. Once approved, implementation can proceed without further product clarification.

Get in Touch

Via Roo Code Cloud task link above

---

Important

Adds a comprehensive specification document for the blog MVP, detailing routes, content source, frontmatter schema, publish gating, rendering strategy, and more.

• Specification Document:
  • Adds blog.md in apps/web-roo-code/docs/ detailing the blog MVP specification.
  • Covers routes (/blog, /blog/[slug]), content source (content/blog/), and frontmatter schema (required fields like publish_date, publish_time_pt).
  • Describes publish gating using Pacific Time, dynamic SSR rendering, and slug rules.
• Rendering and Display:
  • Specifies dynamic SSR on Node.js for request-time gating.
  • Date-only display rules, no time shown to users.
• Markdown and Slug Rules:
  • Only standard Markdown allowed, no raw HTML.
  • Slug pattern ^[a-z0-9]+(?:-[a-z0-9]+)*$ with uniqueness validation.
• Substack Syndication and Containment:
  • Checklist for syndicating to Substack.
  • Changes scoped to /blog routes, minimal nav/sitemap updates.

^{This description was created by for 210f91a. You can customize this summary. It will automatically update as commits are pushed.}

[ghost]

Rooviewer   See task on Roo Cloud

Review complete. No issues found.

This is a well-structured specification document that is internally consistent, accurately references existing codebase elements, and provides clear implementation guidance.

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[github-actions]

🚀 Preview deployed!

Your changes have been deployed to Vercel:

Preview URL: https://roo-code-website-81ywga0me-roo-code.vercel.app

This preview will be updated automatically when you push new commits to this PR.

[ghost]

Rooviewer   See task on Roo Cloud

Review complete. No issues found.

This is a well-structured specification document that is internally consistent, accurately references existing codebase elements, and provides clear implementation guidance.

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[mp-roocode]

This was a Linear test, no need to merge