Skip to content

feat: add the blog, its pages and its header links - #92

Merged
alexgrozav merged 1 commit into
blog-uxf-803from
blog-uxf-871
Nov 18, 2026
Merged

alexgrozav merged 1 commit into
blog-uxf-803from
blog-uxf-871

Conversation

@alexgrozav

Copy link
Copy Markdown
Contributor

What changed

This adds a blog to opencomponents.dev, built the way the changelog is, so we have somewhere to write about building components beyond what the standard says. It targets the blog-uxf-803 integration branch, not main, and its first post is a stub until the real one is written. Here's what it adds:

  • The blog. A blog collection in content.config.ts holds one post per file in content/blog/. /blog lists them newest first, a row each with the date, title, standfirst, author and reading time, and /blog/<slug> shows each one: a large headline, the standfirst, a byline and the body in a column of about 32em, some 65 characters a line. Both are prerendered, in the Docus shell, with the site's own colours, fonts and components.
  • The header links. "Blog" comes after Documentation and Changelog in both headers. The docs header marks it aria-current="page" on the blog's pages, and lists it in its menu below 768px. On the homepage it hides below 640px with Changelog.
  • Search and agents. Each post has its own head tags and a BlogPosting, without the Article Docus's useSeo() would add, and an Open Graph image. The sitemap lists the blog and its posts, llms.txt lists every post, and each post has a markdown copy at /raw/blog/<slug>.md, served from its source like the docs pages' copies, with a canonical Link header. pnpm check-seo now checks all of this for the blog too.
  • The content gate. server/lib/blog.test.ts checks every token name in a post's code against the pattern on the Design Tokens page, read from the page itself, apart from the names a post lists in counterExamples. It checks the syntax only, so a reviewer still checks that each counter-example is really wrong.
  • Docs. "The blog" in .github/CONTRIBUTING.md, its lines in "Keeping 100s as the site grows", and content/blog/ in AGENTS.md.

Checklist

  • The title follows Conventional Commits, as in feat(docs): add the focus guideline.
  • pnpm check-types passes.
  • Docs changes: the pages read well on pnpm dev. (Checked on the prerendered dist/ instead, in light and dark mode at 375px and 1280px.)
  • Homepage changes: pnpm build, then pnpm lighthouse, still scores 100 in every category.

The blog follows the changelog: a `blog` collection of one post per file
in content/blog/, a listing at /blog and a page per post, both prerendered
in the Docus shell, and a "Blog" link after Changelog in both headers.

Each post writes its own head tags and a BlogPosting, rather than the
Article Docus's useSeo() would add, and has a markdown copy at
/raw/blog/<slug>.md, served from its source with a canonical Link header.
The sitemap, llms.txt and check-seo cover the blog, and a content gate
checks every token name in a post against the Design Tokens page.

The first post is a stub, which its writer replaces.

Co-authored-by: multica-agent <github@multica.ai>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://blog-uxf-871.opencomponents.dev, https://blog-uxf-871-opencomponents.blue-water-0397.workers.dev (commit 481a337)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status Deployment URL Commit Updated (UTC) See this deployment's details
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://89f226f0.opencomponents.dev, https://89f226f0-opencomponents.blue-water-0397.workers.dev 481a337 2026-11-18T13:57:26.326Z Visit the dashboard ↗

@alexgrozav
alexgrozav merged commit cd83247 into blog-uxf-803 Nov 18, 2026
5 checks passed
@alexgrozav
alexgrozav deleted the blog-uxf-871 branch November 18, 2026 14:07
alexgrozav added a commit that referenced this pull request Nov 19, 2026
…94)

## What changed

opencomponents.dev gets a blog at `/blog`, and its first post is "How to
name design tokens". People search for that question, and the answer is
on the Design Tokens page, spread across a reference. The post walks
through it step by step and sends readers back to the page. Posts aren't
part of the standard, so the MCP server doesn't read them.

The branch brings together three pull requests:

- #92 adds the blog. It's a Nuxt Content collection built like the
changelog, with a listing at `/blog` and a page per post laid out like a
long-form article: a large headline, the standfirst, the author, date
and reading time, then a narrow column of body text. Both headers link
to it after Changelog. Each post has `BlogPosting` structured data, a
place in the sitemap and `llms.txt`, and a Markdown copy at
`/raw/blog/<slug>.md`, served from its source so its tables stay tables.
`pnpm check-seo` now checks all of this. A content check in
`server/lib/blog.test.ts` reads every token name in a post against the
pattern on the Design Tokens page, so the two can't drift apart.
`.github/CONTRIBUTING.md` and `AGENTS.md` describe the blog.
- #93 writes the post. Its first sentence answers the question on its
own. Six steps follow, each with its reason, its rule ID and a link to
the section of the Design Tokens page it comes from, then worked
examples. The Design Tokens page gains one sentence that links to the
post, and nothing else on it changes.
- #95 rewrites the post in the voice of the docs. One example, a theme
and a tooltip, is renamed a step at a time, and each step gives its
reason. Links to the Design Tokens page sit where a reader would want
the detail, in place of a rule ID after every claim. It's shorter, and
only the post's file changes.

Merging this publishes the blog and its first post.

## Checklist

- [x] The title follows [Conventional
Commits](https://www.conventionalcommits.org), as in `feat(docs): add
the focus guideline`.
- [x] `pnpm check-types` passes. (Run on each part, #92 and #93, along
with `pnpm test`, `pnpm check-reference`, `pnpm build`, `pnpm
check-seo`, `pnpm build:mcp` and `pnpm check-mcp`.)
- [x] Docs changes: the pages read well on `pnpm dev`. (Checked on the
built site, in screenshots of the listing and the post at 375px and
1280px, in light and dark mode.)
- [x] Homepage changes: `pnpm build`, then `pnpm lighthouse`, still
scores 100 in every category. (The homepage gains only the Blog link.
Lighthouse passed on each part.)

---------

Co-authored-by: multica-agent <github@multica.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant