Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Produce two DevRel artifacts. (1) A conference TALK package: a CFP (Call for Papers) abstract, a talk OUTLINE with one clear core message and a structured arc, a planned DEMO with an explicit safety net (since live demos fail), and how you'd handle Q&A — framed to TEACH, not pitch. (2) A 90-day COMMUNITY engagement plan for a developer community (Discord/forum/GitHub Discussions): how you'd seed and grow it, foster peer-to-peer help (so it's not all you), a code of conduct/moderation approach, a champions/ambassador idea, and the HEALTH signals you'd watch — distinguishing meaningful engagement from vanity headcount.
Strong CFP + outline with one core message and a clear arc; a demo with a safety net; teaches rather than pitches.
Realistic seed->grow plan fostering peer-to-peer help; CoC/moderation; champions; health signals over vanity headcount.
Both artifacts build credibility/trust; no shilling or over-promotion.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A talk + community engagement plan ## Goal Produce two DevRel artifacts. (1) A conference TALK package: a CFP (Call for Papers) abstract, a talk OUTLINE with one clear core message and a structured arc, a planned DEMO with an explicit safety net (since live demos fail), and how you'd handle Q&A — framed to TEACH, not pitch. (2) A 90-day COMMUNITY engagement plan for a developer community (Discord/forum/GitHub Discussions): how you'd seed and grow it, foster peer-to-peer help (so it's not all you), a code of conduct/moderation approach, a champions/ambassador idea, and the HEALTH signals you'd watch — distinguishing meaningful engagement from vanity headcount. ## Acceptance criteria - [ ] Talk craft: Strong CFP + outline with one core message and a clear arc; a demo with a safety net; teaches rather than pitches. - [ ] Community plan: Realistic seed->grow plan fostering peer-to-peer help; CoC/moderation; champions; health signals over vanity headcount. - [ ] Authenticity: Both artifacts build credibility/trust; no shilling or over-promotion. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.