Add new blog post + visual polish across the blog (blockquotes, callout boxes, collapsible FAQ) - #238
Merged
Merged
Conversation
added 6 commits
August 10, 2026 10:02
New post at /blog/episodic-vs-semantic-memory. Uses the site's existing visual language throughout rather than introducing new patterns: - Collapsible FAQ via native <details>/<summary>, same markup and style as the home page's FAQSection — added a small plain-CSS rule (.blog-faq-chevron) in src/index.css since Tailwind's group-open: variant needs a literal `group` class, which is fragile to ask of hand-authored MDX; :where([open]) is more robust for that context. - Two blockquotes (an attributed quote, and the article's core rule) using the blockquote styling that already existed in PROSE_CLASSES but no post had used yet. - A callout box and a stats box, both reusing the site's existing border/tint treatment (brand-500) and the shared `section-eyebrow` class, not a new component. - Closing CTA button reuses the real `btn-gradient` classes from Button.tsx's primary variant instead of a plain text link. - All external citations (CoALA, LangChain docs, Atlan, Salesforce CRMArena-Pro, CIO, ICLR 2025 benchmark) verified and linked to their real source — nothing invented. Note: this branch is based on main before fix/blog-og-meta merges, so this post's <title>/og:title will show the generic homepage one in the static HTML until that PR lands too — expected, not a regression.
Same visual treatment as the new episodic-vs-semantic-memory post — no new patterns, reusing the blockquote styling already in PROSE_CLASSES and the brand-500 callout box. This post has no FAQ-shaped content, so no accordion added here.
Same treatment as the previous two posts — the opening definition and the closing architecture-mistake line as blockquotes, and the 'what memory adds' list as a brand-500 callout box. No FAQ content to restyle here either.
Same treatment as the previous three: two blockquotes (the early hook line, and the 'points at receipts' line closing Step 4) and the 'What this doesn't solve' list as a brand-500 callout box.
Same treatment as the other four: the foreign-key blockquote and the closing 'that's the deal' line as blockquotes, and the 'You give up / You get' tradeoff list as a brand-500 callout box.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
2 participants
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.
Summary
Two things bundled in one branch since they touch the same area:
New post: "Episodic vs Semantic Memory in AI Agents" at
/blog/episodic-vs-semantic-memory— full article with a comparison table, a code-block diagram, 2 blockquotes, a callout box, a collapsible FAQ (6 questions, native<details>/<summary>— same accessible pattern as the home page's FAQ section), a stats callout, and a real CTA button. All external citations (CoALA, LangChain docs, Atlan, Salesforce CRMArena-Pro, CIO, ICLR 2025 benchmark) verified and linked to their real source.Visual polish on the 4 existing posts — one commit per post, same treatment throughout:
blockquotestyling that already existed inPROSE_CLASSESbut no post had used yetbrand-500border/tint treatment + the sharedsection-eyebrowclass) around whatever list in that post was the best fit — no new visual components, just applying what already exists in the design systemNo new components, no new CSS beyond a small
.blog-faq-chevronrule insrc/index.cssfor the FAQ's disclosure arrow (Tailwind'sgroup-open:variant needs a literalgroupclass, which is fragile to rely on in hand-authored MDX — a plain:where([open])rule is more robust there).Test plan
npm run buildgreen after every commit