| 1 | # Steid |
| 2 | |
| 3 | The source of truth for everything in a developer's or organization's portfolio. |
| 4 | |
| 5 | ## Vision |
| 6 | |
| 7 | Steid is a developer/org identity and portfolio platform. It's where you host your |
| 8 | code, your writing, your projects — everything you do, in one place, under your |
| 9 | control. |
| 10 | |
| 11 | Git repos are a core feature, not the whole product. Blogs, documentation, project |
| 12 | showcases, and anything else a dev or org wants to present lives here too. |
| 13 | |
| 14 | Personal-first, but organizations can collaborate on it. |
| 15 | |
| 16 | **What makes it different from Gitea/Forgejo:** those are GitHub clones scaled down. |
| 17 | Steid is portfolio-first — the profile page is the product, and repos are one kind of |
| 18 | thing that appears on it. That framing should win any tie-break. |
| 19 | |
| 20 | ## Core Principles |
| 21 | |
| 22 | - **Fast** — Rust, minimal overhead |
| 23 | - **Reliable** — correct first, then optimize |
| 24 | - **Personal-first** — great for a single dev, scales to orgs |
| 25 | - **Identity-centric** — everything is built around who you are (user/org); auth is |
| 26 | designed in from day one, not bolted on |
| 27 | |
| 28 | ## Stack |
| 29 | |
| 30 | Starting intent, not settled decisions. Each one gets a record in |
| 31 | [decisions/](decisions/) when it's actually made and confirmed in this build. |
| 32 | |
| 33 | |
| 34 | |
| 35 | | Web framework | Topcoat (tokio-rs) | — | |
| 36 | | Git transport | smart HTTP via `git http-backend` | [0001](decisions/0001-git-over-http-not-ssh.md) | |
| 37 | | Git auth | personal access tokens over HTTP Basic | [0001](decisions/0001-git-over-http-not-ssh.md) | |
| 38 | | Crate layout | single crate | — | |
| 39 | | Ownership | personal org owns repos | — | |
| 40 | | Database | SQLite via sqlx | — | |
| 41 | |
| 42 | Architecture and conventions: [architecture.md](architecture.md). |
| 43 | |
| 44 | ## Milestone Ladder |
| 45 | |
| 46 | A from-scratch rebuild on Topcoat. Much of this was built and verified end-to-end in a |
| 47 | previous attempt — see [progress.md](progress.md). Treat that code as reference, not as |
| 48 | a baseline. |
| 49 | |
| 50 | |
| 51 | |
| 52 | | 0 | **Skeleton** — Topcoat app boots, config, one page, SQLite wired | done | |
| 53 | | 1 | **Identity, thin** — claim on first run, login, session | active (all but `/api/me`) | |
| 54 | | 2 | **Profile page** — `/{owner}` as the real home page | not started | |
| 55 | | 3 | **Writing** — posts, markdown | not started | |
| 56 | | 4 | **Repo model** — records + bare repos on disk | not started | |
| 57 | | 5 | **Git over HTTP** — `git http-backend`, PATs for auth | not started | |
| 58 | | 6 | **Repo browsing** — tree, blob, commit log | not started | |
| 59 | | 7 | **Identity, full** — multi-user, orgs, invites, registration policy | not started | |
| 60 | | 8+ | Projects/showcases · issues & PRs · SSH transport · federation | not started | |
| 61 | |
| 62 | `/api` is not a milestone. It's a standing practice: every milestone that adds a use |
| 63 | case exposes it under `/api` where that makes sense. An API isn't a feature, it's a |
| 64 | second surface on work already being done — and having a third consumer keeps the use |
| 65 | case layer honest. |
| 66 | |
| 67 | ### Why this order |
| 68 | |
| 69 | The vision calls Steid portfolio-first, but every previous ladder put portfolio behind |
| 70 | four milestones of git plumbing. Across two attempts and ~6,000 lines, Steid has |
| 71 | shipped identity, repo records, clone, push, and key auth — and not one portfolio |
| 72 | feature. Attempt #2 ended with all the git infrastructure working and nothing that |
| 73 | distinguishes it from Gitea. |
| 74 | |
| 75 | So the differentiator ships early (2–3), and git — which is well-understood and has a |
| 76 | working reference implementation — comes after. Full multi-user identity is deferred |
| 77 | to 7, because personal-first means one user, and there's nothing to collaborate on |
| 78 | until there's something worth collaborating on. |
| 79 | |
| 80 | **Open:** milestone 3 is written as *writing/posts*, but *projects & showcases* is the |
| 81 | other candidate for the first portfolio feature. Unresolved. |
| 82 | |
| 83 | **One numbering scheme.** The previous attempt kept two (a roadmap ladder and a |
| 84 | separate build log with conflicting numbers) and they drifted apart within three |
| 85 | milestones. If the plan changes, edit this table — don't start a second list. |
| 86 | |
| 87 | The active milestone is broken into steps in [current.md](current.md). |