Marketing: brand voice guide
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- content
Research direction
Read the linked style Epic #1120 and the source guide, “Distribution 101: A Guide to Reaching Millions.” Draft a short voice file covering the project's personality, tone, and things it would never say. Done means the guide covers those points and leaves agent generated drafts for a human to rewrite in their own voice before posting.
Written by the indexing model from the issue text.
Description
Part of #1111. Source: Ryan (@ryangrowthh), Distribution 101: A Guide to Reaching Millions, shared by Andrew 2026-10-16.
A short voice file covering personality, tone, and what the project would never say. It links to the style Epic #1120. Agent drafts are only drafts: the article warns against AI-written personal content, so a human rewrites in their own voice before posting.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 4d 44m
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from akasper/plate
-
area:security Task
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
area:cli Bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
area:cli Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
need:refinement status:stub
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 2 days
-
Design: a PLATE-native way to close and manage Question issues (Closes fails on release branches)Openarea:cli area:docs Design need:decision
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
521xueweihan/HelloGitHub#4150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
aws-samples/sample-per-model-bedrock#595 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug connectors
Difficulty 1/5 Under an hour Newbie friendliness 67/100
pyinfra-dev/pyinfra#2036 ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day