Docs: add CONTRIBUTING-docs.md and flesh out README#319
Conversation
Publishes the docs contributing bar so community PRs come in pre-shaped. Covers Diataxis mode selection, the quality bar (verified commands, dated freshness lines, real diagrams, no abandoned drafts), the PR submission flow and review expectations, and the project voice. The defect-pattern section cites real findings from the 2026-05-10 docs audit. The README went from one line to a real landing — local-dev commands, where pages live, and a pointer to CONTRIBUTING-docs.md. Co-Authored-By: Paperclip <noreply@paperclip.ing>
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThis PR establishes a comprehensive contribution framework for the ESPresense documentation site. The README is expanded to provide project setup and development instructions, while a new CONTRIBUTING-docs.md file specifies the Diataxis-based organizational framework, multi-part quality standards, known defects to avoid, step-by-step PR submission workflow, site writing voice, common contribution patterns, and coordination requirements. ChangesDocumentation and Contribution Guide
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@CONTRIBUTING-docs.md`:
- Line 108: Replace the inline code span `` `## ` `` with `` `##` `` and move
any note about the required trailing space outside the backticks so the
backticked code contains no internal trailing space (this resolves MD038);
update the sentence around the heading example in CONTRIBUTING-docs.md where the
code span is used to say e.g. use `##` and then describe that two consecutive
headings with no content between them indicate an empty H2.
🪄 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: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 5c537d86-6bd3-4472-b39d-f87ab773e60d
📒 Files selected for processing (2)
CONTRIBUTING-docs.mdREADME.md
CodeRabbit flagged the inline code span `## ` as MD038 (no-space-in-code). Drop the trailing space and reword the surrounding clause so the meaning is unchanged. Co-Authored-By: Paperclip <noreply@paperclip.ing>
|
Addressed CodeRabbit's MD038 finding in commit 25b4fd5: removed the internal trailing space from the Re-requesting CodeRabbit re-scan; @DTTerastar still owns final maintainer review/merge per the auto-assignment. |
Summary
CONTRIBUTING-docs.mdat the repo root — the docs contributing bar so community PRs come in pre-shaped. Covers the Diataxis frame, the docs quality bar (verified commands, dated freshness lines, real diagrams, no abandoned drafts), the PR submission flow and review expectations, and the project voice.README.mdto a real landing — local-dev commands, where pages live, and a pointer toCONTRIBUTING-docs.md.Why
Until now there was no public bar for what a "good" docs PR looks like and no contributor instructions in the README. The result has been mixed-mode pages, undated freshness, and stale UI screenshots accumulating over time. Once the bar is public, drive-by contributions can hit it.
Test plan
./src/content/docs/...,./astro.config.mjs,./.nvmrc,./src/content/docs/credits.md).src/content/docs/is touched, so no Starlight pages or sidebar entries change.Diataxis mode of new content: explanation (CONTRIBUTING-docs.md), reference (README.md).
🤖 Generated with Claude Code
Summary by CodeRabbit