Add "Building an Oracle" post and restyle post index lists#12
Merged
Conversation
# Problem The blog had no post for the Oracle project, and the post index lists across the homepage and theme landing pages used inline `—` separators and `<small>` tags for metadata, making dates, descriptions, and tags visually muddled and hard to style consistently. # Solution Adds the "building an oracle" engineering post, which covers the Table22 Oracle: a knowledge base of ~50 principles mined from nearly a thousand PR discussions, grounded in verbatim review quotes, and used as an agentic code reviewer that learns from whether the team accepts or ignores its feedback. Alongside the new post, the build pipeline and all rendered HTML are updated to emit semantic BEM-style classes on list markup: `post-list`, `post-item`, `post-title`, `post-date`, and `post-desc`. Section headers on the homepage are promoted from a bold `<p>` to an `<h2 class="post-section-title">` for correct document outline. The `—` inline separator and `<br><small>` description pattern are removed entirely in favor of block-level elements. CSS adds the new classes with explicit block display, a subtle divider between items, and a lighter tag palette so tags read as metadata rather than badges. # Notes The rendered HTML files (index.html, engineering/index.html, side-projects/index.html, and the new post file) are committed alongside the source changes, consistent with how this project handles the build output.
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
1 participant
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.
Problem
The blog had no post for the Oracle project, and the post index lists across the homepage and theme landing pages used inline
—separators and<small>tags for metadata, making dates, descriptions, and tags visually muddled and hard to style consistently.Solution
Adds the "building an oracle" engineering post, which covers the Table22 Oracle: a knowledge base of ~50 principles mined from nearly a thousand PR discussions, grounded in verbatim review quotes, and used as an agentic code reviewer that learns from whether the team accepts or ignores its feedback.
Alongside the new post, the build pipeline and all rendered HTML are updated to emit semantic BEM-style classes on list markup:
post-list,post-item,post-title,post-date, andpost-desc. Section headers on the homepage are promoted from a bold<p>to an<h2 class="post-section-title">for correct document outline. The—inline separator and<br><small>description pattern are removed entirely in favor of block-level elements.CSS adds the new classes with explicit block display, a subtle divider between items, and a lighter tag palette so tags read as metadata rather than badges.
Notes
The rendered HTML files (index.html, engineering/index.html, side-projects/index.html, and the new post file) are committed alongside the source changes, consistent with how this project handles the build output.