task: apply the Build with X / Build for X naming convention to Build tab titles
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Read AGENTS.md sections 2, 4, and 6, then inspect the listed Build pages and their titles and sidebarTitle values. Decide which entries count as tools versus platforms and whether the two filenames should change; if renamed, update redirects, navigation, and inbound links. Run mint broken-links --check-redirects; done means the rule is recorded, labels follow it, and the check passes.
Written by the indexing model from the issue text.
Description
Follow-up from #2259 / #2368. The Build tab move did not touch page titles; the convention the issue asked for is still open.
What needs to be done?
The issue's convention: "Build with X" for tools and SDKs, "Build for X" for platforms. Titles and nav labels on the Build tab do not follow it consistently:
| Page | Current title | Kind |
|---|---|---|
build/mini-apps/overview |
Build for MiniPay | platform: matches |
build/build-with-farcaster |
Build with Farcaster | platform: should be "Build for Farcaster" |
build/build-with-self |
Build with Self | tool or protocol: matches |
build/build-with-defi |
Build with DeFi | topic: decide |
build/build-with-local-stablecoin |
Build with Local Stablecoins | topic: decide |
build/build-with-usat |
Build with USA₮ | asset: decide |
build/build-on-socialconnect |
Introduction to SocialConnect | no pattern; file name says "on" |
build/agents/overview |
Build with AI on Celo | tool: matches, but the group is called "Agents" |
Also decide whether the file names (build-with-farcaster, build-on-socialconnect) should change; if they do, each needs a redirect (AGENTS.md section 2) and inbound links updated.
Definition of done
- A one-line rule recorded in AGENTS.md (section 4 or 6) naming which products count as tools and which as platforms
- Every title and
sidebarTitlein the Build tab follows it - Any renamed file has a redirect, an updated nav entry and updated inbound links
-
mint broken-links --check-redirectsgreen
Priority
low
Size
S — hours
Refs #2259.
- Dominant language
- MDX
- Stars
- 89
- Forks
- 396
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 17
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 celo-org/docs
-
Add BlockVectra to the Celo mainnet RPC providers listPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
chore priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
celo-org/docs#2362 · 1 comment ·
Maintainers usually reply within 1 day
-
chore priority:medium
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Maintainers usually reply within 1 day
Similar issues
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
storytold/photocraft#15350 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
docker documentation
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
VincenzoImp/openings-job-search#463 ·
Maintainers usually reply within 1 day
-
source:reader type:content-error
Difficulty 1/5 Under an hour Newbie friendliness 82/100
stephrobert/blog-roadmap#193 ·
-
Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
pandas-dev/pandas#72163 ·
Maintainers usually reply within 2 days