docs(launch): code of conduct and Day-0 content drafts#5
Merged
Conversation
Two pieces, both pure-docs / no library impact:
1. CODE_OF_CONDUCT.md — Contributor Covenant 2.1, fetched verbatim
from the GitHub `codes_of_conduct/contributor_covenant` API endpoint
so the text is provably canonical. Updated the [INSERT CONTACT
METHOD] placeholder to point at conduct@atriumjs.dev and the private
vulnerability advisory channel (for reports that intersect a
security issue). This closes the last community-health gap from the
launch-preparation checklist.
2. docs/launch-content/ — paste-ready copy for Day 0, separated from
the launch-preparation and launch-execution timelines:
- x-thread.md 8-tweet launch thread + quote-tweet + Day+1 follow
+ a week of micro-thread topics.
- linkedin-posts.md Day -7 warmup, Day -3 warmup, Day 0 main post,
Day +1 deep-dive, Day +3 founding story.
- devto-longform.md ~2000-word engineering story (problem,
architecture, control-handoff, security
regression, Playwright vs CDP, what's not done).
- outreach-list.md Ten personalized DM/email targets with a
per-row personalization hook and a stagger plan.
- README.md Index, tone notes, personalization checklist.
The Reddit / IH / PH / Discord post bodies stay in
docs/launch-preparation.md §5 — they're short enough to paste from
there and we already point at them.
- README.md: add CODE_OF_CONDUCT.md to the contributing-info bullets. - docs/README.md: three new rows for the launch trilogy (preparation, execution, content) so anyone landing on the docs hub can find them without grepping.
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.
Two pieces, both pure-docs / no library impact.
1. `CODE_OF_CONDUCT.md`
Contributor Covenant 2.1, fetched verbatim from GitHub's `codes_of_conduct/contributor_covenant` API so the text is provably canonical. The `[INSERT CONTACT METHOD]` placeholder is replaced with conduct@atriumjs.dev and a link to the private vulnerability advisory channel.
Closes the last community-health gap from `docs/launch-preparation.md` §3.
2. `docs/launch-content/` — paste-ready Day-0 copy
Separated from the timeline docs (`launch-preparation.md` / `launch-execution.md`) so all draft content lives in one folder.
What's intentionally NOT here
Test plan