Team growth: /contribute/ page, landing join-us, CONTRIBUTING.md #35

Merged

ops merged 1 commit from oss-oo/team-growth into main

2026-09-23 01:09:54 +00:00

ops commented

2026-09-23 00:51:15 +00:00

Contributor

What

Product surfaces for the team-growth action (two brothers looking for 2–4 companions):

New /contribute/ page (site/contribute/): who we are, the three open roles (Maintainer, Ops-Buddy, Community-Heart) with honest "you get" lines, an explicit what you don't get: money section (volunteer reality + euro-for-euro donation honesty), the 200-word "Join the laboratory" manifesto, and a three-step start (open signup → introduce-yourself thread → first task).
Caddy route /contribute/* + prod compose mount ./site/contribute:/srv/contribute:ro — same pattern as /donate/*.
Landing: gentle "Join us — Build the fire with us." section directly under Support (not aggressive), a Contribute footer link, and a "Can I help build this?" FAQ entry.
CONTRIBUTING.md in the laboratory repo: ways to contribute, ground rules (crypto + LLM code welcome, English, security off-channel), getting started, local dev + the non-negotiable e2e gate, PR conventions, agents-as-contributors (AGENTS.md + /agents/ + MCP gateway), recognition. README gets a Contributing section linking it and AGENTS.md.
RUNBOOK: contribute-page row in the branding/site inventory (notes the issue-#34 link dependency).

The pinned introduce-yourself issue #34 was created on the live forge before this PR so the page's entry flow is real from day one.

Verification

scripts/e2e-local.sh: PASS (org → repo → branch → PR → merge, MCP gateway, registrar, mailer relay) — executed via a byte-identical copy with two isolation overrides (compose project oss-oo-tg, port 3001 + !override ports overlay) because the default local stack on 127.0.0.1:3000 was in active use by a parallel session; overlay file lives outside the committed tree.
Caddy route smoke test on a throwaway caddy container with the exact shipped directives: /contribute/ → 200, /contribute → 301 → /contribute/, landing join section served.
Compose config validation for local/prod/ci overlays + bash -n — green.
Browser screenshots of every new section (hero/roles/manifesto/join-us) captured.

Boundaries

Site boundary respected: only oss-singularity.io is named externally; signup/explore/issue links are internal.
No payment promises — volunteer terms and the modest donation jar are stated up front.

## What Product surfaces for the team-growth action (two brothers looking for 2–4 companions): - **New `/contribute/` page** (`site/contribute/`): who we are, the three open roles (**Maintainer**, **Ops-Buddy**, **Community-Heart**) with honest "you get" lines, an explicit *what you don't get: money* section (volunteer reality + euro-for-euro donation honesty), the 200-word "Join the laboratory" manifesto, and a three-step start (open signup → introduce-yourself thread → first task). - **Caddy route** `/contribute/*` + **prod compose mount** `./site/contribute:/srv/contribute:ro` — same pattern as `/donate/*`. - **Landing**: gentle "Join us — Build the fire with us." section directly under Support (not aggressive), a Contribute footer link, and a "Can I help build this?" FAQ entry. - **`CONTRIBUTING.md`** in the laboratory repo: ways to contribute, ground rules (crypto + LLM code welcome, English, security off-channel), getting started, local dev + the non-negotiable e2e gate, PR conventions, agents-as-contributors (AGENTS.md + /agents/ + MCP gateway), recognition. README gets a Contributing section linking it and AGENTS.md. - **RUNBOOK**: contribute-page row in the branding/site inventory (notes the issue-#34 link dependency). The pinned introduce-yourself issue [#34](https://oss-oo.io/OSS-OO/laboratory/issues/34) was created on the live forge before this PR so the page's entry flow is real from day one. ## Verification - `scripts/e2e-local.sh`: **PASS** (org → repo → branch → PR → merge, MCP gateway, registrar, mailer relay) — executed via a byte-identical copy with two isolation overrides (compose project `oss-oo-tg`, port 3001 + `!override` ports overlay) because the default local stack on 127.0.0.1:3000 was in active use by a parallel session; overlay file lives outside the committed tree. - Caddy route smoke test on a throwaway caddy container with the exact shipped directives: `/contribute/` → 200, `/contribute` → 301 → `/contribute/`, landing join section served. - Compose config validation for local/prod/ci overlays + `bash -n` — green. - Browser screenshots of every new section (hero/roles/manifesto/join-us) captured. ## Boundaries - Site boundary respected: only oss-singularity.io is named externally; signup/explore/issue links are internal. - No payment promises — volunteer terms and the modest donation jar are stated up front.

ops added 1 commit

2026-09-23 00:51:15 +00:00

Team growth: /contribute/ page, landing join-us, CONTRIBUTING.md

ci / ci (pull_request) Successful in 3s

Details

451ef64e75

- site/contribute: roles (Maintainer, Ops-Buddy, Community-Heart), honest
  volunteer terms, 200-word manifesto, three-step start (open signup +
  pinned introduce-yourself issue in this repo)
- caddy: /contribute/ route + prod compose mount (site/contribute)
- landing: gentle join-us section under Support, footer link, FAQ entry
- CONTRIBUTING.md + README contributing section (AGENTS.md pointer)
- RUNBOOK: contribute page row in the branding/site inventory

ops force-pushed oss-oo/team-growth from 451ef64e75

ci / ci (pull_request) Successful in 3s

Details

to b8453834eb

ci / ci (pull_request) Successful in 4s

Details

2026-09-23 01:03:26 +00:00

Compare

ops force-pushed oss-oo/team-growth from b8453834eb

ci / ci (pull_request) Successful in 4s

Details

to 01a335468a