docs(okf): add blog/site knowledge sections to the OKF bundle#366
Conversation
Fold a separately-produced Hugo blog/site OKF bundle into the existing course bundle as two new sibling sections plus five workflow concepts. Docs-only; no course-side concepts changed. - architecture/: hugo-site, css-pipeline, blog-list-page, cover-image-pipeline, seo-meta-tags - content-strategy/: icp-primary-website-target, voice-guide - workflows/: blog-pipeline, linkedin-post-pipeline, css-maintainability-plan, visual-scroll-gate, testing Root index + workflows index list the new entries; dated log entry appended. Validated conformant via okf:validate --strict (25 concepts). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 49 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe change adds architecture documentation for Hugo, CSS, blog rendering, images, and SEO; content strategy guidance; blog and LinkedIn workflows; testing and visual validation playbooks; and updated navigation and merge records. ChangesDocumentation bundle
Estimated code review effort: 2 (Simple) | ~15 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.okf/architecture/cover-image-pipeline.md:
- Around line 11-17: Update the cover-image pipeline documentation to describe
the implemented derivation contract: CDN outputs retain the resource’s own
dimensions, local fallback uses Hugo’s `.Fit "512x512 jpeg"`, and thumbnail
widths are supplied by callers. Remove the unsupported fixed 1200×630 and
640/960/1920 dimension claims, unless the implementation and tests are changed
to enforce them.
In @.okf/architecture/seo-meta-tags.md:
- Around line 12-16: Update the SEO contract documentation for
partials/seo/enhanced-meta-tags.html to describe maximum limits of 60 characters
for titles and 160 for descriptions, rather than guaranteed ranges. Document the
branch-specific suffixes (| JT, | JetThoughts Blog, or none) and clarify that
power-word injection is not consistent for individual blog titles.
In @.okf/log.md:
- Around line 19-30: Reorder the new 2026-07-18 entry in the log so it appears
after all existing 2026-07-17 entries, including the “later” entry, while
preserving the entry’s content unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 5e3ce6c9-3218-4985-9050-88e65b33c293
📒 Files selected for processing (17)
.okf/architecture/blog-list-page.md.okf/architecture/cover-image-pipeline.md.okf/architecture/css-pipeline.md.okf/architecture/hugo-site.md.okf/architecture/index.md.okf/architecture/seo-meta-tags.md.okf/content-strategy/icp-primary-website-target.md.okf/content-strategy/index.md.okf/content-strategy/voice-guide.md.okf/index.md.okf/log.md.okf/workflows/blog-pipeline.md.okf/workflows/css-maintainability-plan.md.okf/workflows/index.md.okf/workflows/linkedin-post-pipeline.md.okf/workflows/testing.md.okf/workflows/visual-scroll-gate.md
Address CodeRabbit review on #366: - seo-meta-tags: describe actual behavior — per-branch hardcoded titles, max-length caps (60/160, not guaranteed ranges), varying suffixes (| JetThoughts / | JT / | JetThoughts Blog / none), and note the $powerWords dict + $titleSuffix var are defined but unused. Add the partial's own 1200x630 og:image path. - cover-image-pipeline: attribute the 1200x630 / 640·960·1920 / 360x189 sizes to the .stitch/design.md spec as target output, not template derivation; point the fixed 1200x630 og:image at seo-meta-tags. - log: move the 2026-07-18 entry below both 2026-07-17 entries to keep the chronological order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 participant
Summary
Folds a separately-produced Hugo blog/site OKF bundle into the existing course
.okf/bundle (added on master in #361) as two new sibling sections plus five workflow concepts. Docs-only — no course-side concepts, templates, CSS, or content pages changed.New sections
architecture/—hugo-site,css-pipeline,blog-list-page,cover-image-pipeline,seo-meta-tagscontent-strategy/—icp-primary-website-target,voice-guideNew workflow concepts (alongside master's
render-verification+review-swarm)blog-pipeline,linkedin-post-pipeline,css-maintainability-plan,visual-scroll-gate,testingBookkeeping
index.mdandworkflows/index.mdlist the new entries2026-07-18log.mdentry appended (existing headings untouched)Content distilled from
CLAUDE.md,bin/hugo-build,Rakefile,config/_default/hugo.toml, theme layouts/partials, anddocs/workflows/+docs/90-99-content-strategy/.Verification
okf:validate --strict→ conformant, 25 concepts. Remaining warnings are soft §7 date-format notes; the new log heading matches the pre-existing## YYYY-MM-DD - descriptionconvention already on master.themes//layouts//*.css/content-body changes, so the visual-regression gate (bin/test/bin/dtest) does not apply.🤖 Generated with Claude Code
Summary by CodeRabbit