Context. Make the org page look finished: description + profile README + pinned repos.
1 · Org description & website (run from anywhere, org-admin)
gh api -X PATCH orgs/JorisJonkers-dev \
-f description="Self-hosted platform & agent stack powering jorisjonkers.dev — typed deploys, shared libraries, and apps." \
-f blog="https://jorisjonkers.dev"
2 · Profile README (in your .github clone)
main is protected, so this goes via a quick PR:
mkdir -p profile
cat > profile/README.md <<'MD'
# JorisJonkers-dev
Self-hosted platform and agent stack powering **[jorisjonkers.dev](https://jorisjonkers.dev)**.
Source-available — © Joris Jonkers Both. All rights reserved.
### Platform & deploy
- **deploy-config-schema** — typed deployment schema + compiler (Kubernetes / Traefik / VSO / Gatus / Flux)
- **platform-blueprints** — reusable platform packs (edge, observability, NVIDIA, Flux core)
- **nix-platform** — parameterized Nix modules & host profiles
- **github-workflows** · **gradle-conventions** · **openapi-client-gradle** · **repo-template** — shared CI & scaffolding
### Libraries
- **kotlin-spring-commons** · **vue-web-commons** · **authz-model** · **api-contract-checks**
### Apps
- **agents-api** · **agents-ui** — agent platform
- **auth-api** · **auth-ui** — authentication
- **knowledge** — knowledge base & MCP endpoint
- **home-portal** — landing portal
MD
git checkout -b chore/profile-readme
git add profile/README.md
git commit -m "docs: add org profile README"
git push -u origin chore/profile-readme
gh pr create --base main --head chore/profile-readme \
--title "docs: add org profile README" --body "Org profile landing page."
# once Pipeline Complete is green (auto-merge isn't enabled on .github, so merge directly):
gh pr merge chore/profile-readme --squash
3 · Pin showcase repos (UI — no API for org pins)
Org home → Customize pins → select ~6: deploy-config-schema, platform-blueprints, kotlin-spring-commons, vue-web-commons, nix-platform, agents-api.
Acceptance
Where to run: gh commands run from anywhere (they name repos explicitly) and need gh auth status as an org-admin. Steps marked (in your .github clone) must run inside the cloned repo.
Progress: ✅ Profile README done — merged via PR #29. Remaining: run the gh api PATCH /orgs description command (step 1) and pin repos (step 3).
Context. Make the org page look finished: description + profile README + pinned repos.
1 · Org description & website (run from anywhere, org-admin)
2 · Profile README (in your
.githubclone)mainis protected, so this goes via a quick PR:3 · Pin showcase repos (UI — no API for org pins)
Org home → Customize pins → select ~6:
deploy-config-schema,platform-blueprints,kotlin-spring-commons,vue-web-commons,nix-platform,agents-api.Acceptance
profile/README.mdmerged and rendering on the org pageWhere to run:
ghcommands run from anywhere (they name repos explicitly) and needgh auth statusas an org-admin. Steps marked (in your.githubclone) must run inside the cloned repo.