Repository navigation
feat: add a blog, with "How to name design tokens" as its first post - #94
Merged
Merged
Conversation
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>
Replace the stub with the post: six steps, each with its reason, its rule ID and a link to the Design Tokens section it comes from, then worked examples and how to check names. The Design Tokens page links to it under its intro. Co-authored-by: multica-agent <github@multica.ai>
Co-authored-by: multica-agent <github@multica.ai>
alexgrozav
marked this pull request as ready for review
November 18, 2026 14:53
alexgrozav
marked this pull request as draft
November 19, 2026 06:21
Rename one stylesheet, a theme and a tooltip, a step at a time, so each rule comes with its reason and the names improve as the post goes. Drop the rule IDs in brackets, the sentence about the post and the tables copied from the Design Tokens page. Co-authored-by: multica-agent <github@multica.ai>
alexgrozav
marked this pull request as ready for review
November 19, 2026 06:49
Both headers, and the docs header's menu below 768px, now list the blog first, then the changelog and the docs. A test keeps the homepage's links and docsTheme.headerLinks in that order. Refs UXF-803 Co-authored-by: multica-agent <github@multica.ai>
Clarified the naming convention for design tokens and explained the use of token paths in CSS.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
/blogand 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 hasBlogPostingstructured data, a place in the sitemap andllms.txt, and a Markdown copy at/raw/blog/<slug>.md, served from its source so its tables stay tables.pnpm check-seonow checks all of this. A content check inserver/lib/blog.test.tsreads every token name in a post against the pattern on the Design Tokens page, so the two can't drift apart..github/CONTRIBUTING.mdandAGENTS.mddescribe the blog.Merging this publishes the blog and its first post.
Checklist
feat(docs): add the focus guideline.pnpm check-typespasses. (Run on each part, feat: add the blog, its pages and its header links #92 and feat(docs): write the how to name design tokens post #93, along withpnpm test,pnpm check-reference,pnpm build,pnpm check-seo,pnpm build:mcpandpnpm check-mcp.)pnpm dev. (Checked on the built site, in screenshots of the listing and the post at 375px and 1280px, in light and dark mode.)pnpm build, thenpnpm lighthouse, still scores 100 in every category. (The homepage gains only the Blog link. Lighthouse passed on each part.)