Public site conversion & trust surface #28

Stängd
öppnade 2026-07-17 16:33:55 +00:00 av supernaut · 1 kommentar
Ägare

The public site had to carry two things it did not: a trust surface concrete enough to be
checked rather than asserted, and a commercial surface that says what Bitborg costs and why it
is worth paying for when other hosts are free. Alongside those, a set of credibility defects —
claims the site made that were not accurate, and copy that undermined the rest by being visibly
wrong.

The conversion surface must exist at or before paid launch.

Scope

  • Credibility corrections: cookie handling described in the privacy policy rather than behind a
    dead link, a complete sub-processor list, corrected Terms wording on backup location, Swedish
    copy fixes above the fold, and the removal of a stale "coming soon" claim that was no longer
    true
  • The four principle cards rewritten so each states something verifiable — the security card
    names the weekly restore-and-verify drill, and the free-software card names the licences and
    links to Bitborg's own source
  • /security — the trust and compliance page, both locales
  • /pricing — single account plus add-ons, both locales, in the primary navigation
  • The waiting-list call to action replaced by sign-up, superseded by open registration
    (ADR 0029)
  • The documentation knowledge base and FAQ launched, with guides for Renovate, Actions and
    accounts
  • gitborg/gitborg-web#181 — a getting-started guide: connect over SSH, first repository, clone,
    commit and push. Shipped 2026-08-02
  • gitborg/gitborg-web#182 — a migration guide for repositories arriving from GitHub or GitLab

Out of scope (2026-08-02)

Two pages in the original scope are dropped, not deferred:

  • /why-bitborg — a comparison and objection-handling page
  • /teams — an organisation page

The trust and pricing pages carry the argument these were meant to make, and an organisation page
describing a product with no self-serve billing behind it would be a promise the site cannot keep.
If either is wanted later it should be argued for on its own merits, as its own epic, rather than
inherited from this one.

Done when

A visitor can find out what Bitborg costs, check the claims it makes about sovereignty, privacy,
security and licensing, and get from sign-up to a first push without leaving the site.

Status — 2026-08-02

The trust and commercial surfaces are live and the credibility defects are corrected. What remained
was never tracked: this epic was created as a tracking epic and its phase issues were never filed,
so the work proceeded without child issues and the epic pointed at nothing. That is now repaired —
the delivered scope is recorded above, the two genuinely outstanding items are filed as
gitborg/gitborg-web#181 and gitborg/gitborg-web#182, and two pages have been dropped explicitly
rather than left implicitly undone.

The getting-started guide, which was the one launch concern, shipped the same day: a visitor
finishing sign-up now has a documented path from an account to a first push. The migration guide is
the only item left, and it is a switching-cost improvement rather than a blocker — so the epic's
build scope is effectively complete and it can close once that guide lands.

The public site had to carry two things it did not: a **trust surface** concrete enough to be checked rather than asserted, and a **commercial surface** that says what Bitborg costs and why it is worth paying for when other hosts are free. Alongside those, a set of credibility defects — claims the site made that were not accurate, and copy that undermined the rest by being visibly wrong. The conversion surface must exist at or before paid launch. ## Scope - [x] Credibility corrections: cookie handling described in the privacy policy rather than behind a dead link, a complete sub-processor list, corrected Terms wording on backup location, Swedish copy fixes above the fold, and the removal of a stale "coming soon" claim that was no longer true - [x] The four principle cards rewritten so each states something verifiable — the security card names the weekly restore-and-verify drill, and the free-software card names the licences and links to Bitborg's own source - [x] `/security` — the trust and compliance page, both locales - [x] `/pricing` — single account plus add-ons, both locales, in the primary navigation - [x] The waiting-list call to action replaced by sign-up, superseded by open registration (ADR 0029) - [x] The documentation knowledge base and FAQ launched, with guides for Renovate, Actions and accounts - [x] gitborg/gitborg-web#181 — a getting-started guide: connect over SSH, first repository, clone, commit and push. Shipped 2026-08-02 - [x] gitborg/gitborg-web#182 — a migration guide for repositories arriving from GitHub or GitLab ## Out of scope (2026-08-02) Two pages in the original scope are **dropped**, not deferred: - **`/why-bitborg`** — a comparison and objection-handling page - **`/teams`** — an organisation page The trust and pricing pages carry the argument these were meant to make, and an organisation page describing a product with no self-serve billing behind it would be a promise the site cannot keep. If either is wanted later it should be argued for on its own merits, as its own epic, rather than inherited from this one. ## Done when A visitor can find out what Bitborg costs, check the claims it makes about sovereignty, privacy, security and licensing, and get from sign-up to a first push without leaving the site. ## Status — 2026-08-02 The trust and commercial surfaces are live and the credibility defects are corrected. What remained was never tracked: this epic was created as a tracking epic and its phase issues were never filed, so the work proceeded without child issues and the epic pointed at nothing. That is now repaired — the delivered scope is recorded above, the two genuinely outstanding items are filed as gitborg/gitborg-web#181 and gitborg/gitborg-web#182, and two pages have been dropped explicitly rather than left implicitly undone. The getting-started guide, which was the one launch concern, shipped the same day: a visitor finishing sign-up now has a documented path from an account to a first push. The migration guide is the only item left, and it is a switching-cost improvement rather than a blocker — so the epic's build scope is effectively complete and it can close once that guide lands.
supernaut lade till detta till projektet Bitborg Roadmap 2026-07-17 16:34:26 +00:00
Upphovsperson
Ägare

Build scope delivered — closing per the epic-closing rule in
contributing/issue-tracking.md.

The migration guide (bitborg/bitborg-web#182) was the single outstanding item and the
condition this epic set for closing ("the epic's build scope is effectively complete and it
can close once that guide lands"). It landed and closed on 2026-08-03. All eight items are
now complete.

Moving to Shipped on the Roadmap.

Build scope delivered — closing per the epic-closing rule in `contributing/issue-tracking.md`. The migration guide (bitborg/bitborg-web#182) was the single outstanding item and the condition this epic set for closing ("the epic's build scope is effectively complete and it can close once that guide lands"). It landed and closed on 2026-08-03. All eight items are now complete. Moving to **Shipped** on the Roadmap.
Logga in för att delta i denna konversation.
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Förfallodatumet är ogiltigt eller utanför gränserna. Använd formatet "åååå-mm-dd".

Inget förfallodatum satt.

Beroenden

Inga beroenden satta

Referens
bitborg/bitborg-docs#28
Ingen beskrivning angiven.