dev-tool: LinkedIn review kanban (Now/Next/Future), dev-only - #453
Conversation
- config/development/hugo.toml: mount linkedin-posts/ -> content/linkedin and each lane's assets/ -> static/linkedin-assets/<lane>, re-declaring Hugo's default mounts (content/static/layouts/data/assets/archetypes) since declaring any [[module.mounts]] replaces the implicit set. config/_default and config/production untouched -> zero linkedin output in production builds. - layouts/linkedin/list.html: standalone Now/Next/Future kanban, grouped by the new `stage` frontmatter field. - layouts/linkedin/single.html: standalone preview page - rendered body, visual image (resolved via the lane's mounted assets/), first comment, and a "Copy body" button (clipboard write of .RawContent). - linkedin-posts/**/*.md: add `stage: now|next|future` frontmatter, derived from existing `status` (scheduled/posted -> now, approved -> next, draft -> future). Additive only, no other fields touched. - bin/check-no-li-in-prod: standalone report-only checker (+ --self-test) that builds/inspects a production output and fails if any /linkedin/ review-board output exists. Verified: ENVIRONMENT=production bin/hugo-build produces zero /linkedin/ output (bin/check-no-li-in-prod passes); `hugo --environment development` renders /linkedin/index.html with working Now(2)/Next(0)/Future(12) columns and preview pages with resolved images. bin/qtest --changed: no visual-affecting changes (correct - review board never touches the production site). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 43 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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 Plus Run ID: 📒 Files selected for processing (18)
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 |
1 participant
What
A dev-only Hugo review board for LinkedIn post drafts at
localhost:1415/linkedin/— a Now/Next/Future kanban + per-post preview (body + visual + first-comment + copy button). Solves the scattered-files review UX.Dev-only guarantee (the critical property)
linkedin-posts/->content/linkedinlives inconfig/development/hugo.tomlonly.config/_defaultandconfig/productionuntouched.--environment production(.github/workflows/_hugo.yml), so the board is never built or deployed./linkedin/board absent,/linkedin/{icp-validation,course-promo}absent. (The only/linkedin/in prod is the pre-existing unrelated/social/linkedin/README.)bin/check-no-li-in-prod(report-only, --self-test) guards it going forward.Also
stage: now|next|futurefrontmatter added to the 14 drafts (derived from status; additive).layouts/linkedin/{list,single}.html— standalone, no site design-system dependency.bin/qtest --changed: no visual-affecting changes (dev-only; zero production pages touched).🤖 Generated with Claude Code