Cordy/Cairn
2
1
Fork 0
Code Issues 20 Pull requests Projects Releases Packages Wiki Activity Actions

#251: consolidated Administration settings shell + Peering pilot (v0.6.30) #256

Merged
Cordy merged 3 commits from feat/251-shell into main 2026-08-16 17:54:41 +00:00
Conversation 0 Commits 3 Files changed 2 +120 -1
Cordy commented 2026-08-16 17:53:25 +00:00
Owner
Copy link

Phase 1 of epic #250 (Option A — grouped rail + tabs).

  • New Administration view: the account menu gains an Administration entry (admin-gated) that repurposes the left sidebar as a grouped topic rail (Instance / Access / Sharing & spaces / Federation / Billing) and renders the topic in the main pane. Deep-linkable at #admin/<topic> (a leading-slash-free prefix so it can't collide with the folder-path hash). A "Files" back button exits.
  • Peering pilot: the full peering panel — relationships with inline config, add-a-peer, instance on/off — now lives in the shell as a single panel (no artificial sub-tabs, per the review that a relationship's config shouldn't be fragmented). Implemented by relocating the existing peering DOM into the shell at runtime, so peerRefresh and every handler are reused unchanged. The old Peering menu entry now redirects into the shell.
  • Remaining topics show a placeholder that opens today's Settings, so nothing is unreachable until phases 2–5 port them.

Frontend-only (no settings-API changes). Injected JS passed node --check.

Phase 1 of epic #250 (Option A — grouped rail + tabs). - New **Administration** view: the account menu gains an Administration entry (admin-gated) that repurposes the left sidebar as a grouped topic rail (Instance / Access / Sharing & spaces / Federation / Billing) and renders the topic in the main pane. Deep-linkable at `#admin/<topic>` (a leading-slash-free prefix so it can't collide with the folder-path hash). A "Files" back button exits. - **Peering pilot**: the full peering panel — relationships with inline config, add-a-peer, instance on/off — now lives in the shell as a single panel (no artificial sub-tabs, per the review that a relationship's config shouldn't be fragmented). Implemented by **relocating the existing peering DOM** into the shell at runtime, so `peerRefresh` and every handler are reused unchanged. The old Peering menu entry now redirects into the shell. - Remaining topics show a placeholder that opens today's Settings, so nothing is unreachable until phases 2–5 port them. Frontend-only (no settings-API changes). Injected JS passed `node --check`.
#251: consolidated Administration settings shell + Peering pilot (v0.6.30)
All checks were successful
ci / test-and-build (pull_request) Successful in 35s
Details
103b56a42a
Cordy merged commit 46b29c4347 into main 2026-08-16 17:54:41 +00:00
Cordy deleted branch feat/251-shell 2026-08-16 17:54:43 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#256
No description provided.
Delete branch "feat/251-shell"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?