README and launch messaging (template #209)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
Wait for components-web-app/components-web-app#96 to land on main, then compare its template code against the requested documentation claims. Read the docs' CLAUDE.md and confirm home copy and placeholder changes with Daniel before editing. Review content/index.yml, about.yml, built-for-business.yml, 6.deployment/0.index.md, getting-started/4.releases.md, and the listed image placeholder pages; done means the requested copy, deployment fork, policy page, and images match the landed template and agreed principles.
Written by the indexing model from the issue text.
Description
Source: components-web-app/components-web-app#209. Blocked: don't edit pages until the template change is on main (part of components-web-app/components-web-app#96, "A gentler first hour", for 2.0.0-beta). Check every claim against the template's code when it lands.
- content/index.yml hero and lines 78-85, about.yml, built-for-business.yml:79: drop 'low-code' and 'website builder', lead with purge-driven caching. The docs' CLAUDE.md says not to rewrite the home copy without asking Daniel: confirm the wording with him first.
- Make 6.deployment/0.index.md a fork: one server (preview) or Kubernetes.
- Make getting-started/4.releases.md the versioning and support policy page.
- Fill the image placeholders on the newcomer path (installation 2, deployment index 2, key-ideas 1, admin-panel 14) and hide the other 57. Hiding placeholders changes the docs principle that keeps them visible; confirm with Daniel.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 20m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 components-web-app/docs
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
components-web-app/docs#294 · 1 comment ·
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 45/100
components-web-app/docs#290 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
components-web-app/docs#289 · 2 comments ·
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 43/100
components-web-app/docs#285 ·
-
documentation
Difficulty 4/5 1-2 days Newbie friendliness 35/100
components-web-app/docs#284 ·
All issues in components-web-app/docs
Similar issues
-
bug P3 UI/UX
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
StellarState/SS-backend#712 ·
Maintainers usually reply within 1 day
-
area: backend bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
snapotter-hq/SnapOtter#3473 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
gitroomhq/postiz-app#2304 ·
Maintainers usually reply within 1 day
-
harlan-agent-ready-to-implement routine:ci-review
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
harlan-zw/unlighthouse#454 · 2 comments ·
Maintainers usually reply within 1 day