administrator/Worldshaper
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Expand request review tooling and KB

Browse source
This commit is contained in:
Andraxion 2026-06-27 01:12:35 -04:00
parent ab1dfbf029
commit cae21b61b7
16 changed files with 1258 additions and 241 deletions
Download patch file Download diff file Expand all files Collapse all files

50
docs/kb/systems/launcher-home.md
View file

@ -1,42 +1,36 @@
# Launcher Home
## What It Does
## What It Owns
The launcher is the public-facing entry point for Worldshaper. It presents the hero card, opens the editor in its own floating window, links to the repo, and hosts the News and Requests tabs.
The launcher is the public-facing web shell for Worldshaper. It handles editor launch, launch presentation, release notes, repo navigation, and the visible request board entry point.
## Key Files
## Core Behaviors
- Open the editor in a separate floating window.
- Show the release/news presentation.
- Show the Requests board.
- Swap between public request browsing and protected admin review mode.
- Present launcher artwork and page-level theming.
## Important Files
- `src/WorldshaperLauncher.tsx`
- `src/index.css`
- `src/worldshaperStudio/windowing.ts`
## Endpoints It Uses
## Important UI Surfaces
- `GET /api/world-default`
- `GET /api/launcher-requests`
- Hero launch card
- News tab
- Requests tab
- Protected admin unlock flow
## Important State
## Relationships
- launch state: ready, opening, opened, blocked, error
- active board tab: news or requests
- request list, filters, and expanded request rows
- resolved default world id
- Depends on `Floating Window Shell` for popup launch behavior.
- Depends on `Request Board` for request intake and moderation UI.
- Intersects with `Website` and `Polish` requests more than the editor-runtime systems do.
## Invariants And Constraints
## Triage Hints
- The editor is intended to open in a separate popup-style window.
- The launcher should still work if the default world lookup fails by falling back to `overworld`.
- Browser popup blocking is a real failure mode and must be surfaced to the user.
## Common Request Themes
- page styling and presentation
- launch flow and popup behavior
- repo button or external links
- tab layout and launcher information architecture
## Triage Questions
- Is this about the launcher page itself, or the studio window after launch?
- Does it affect only presentation, or also request API behavior?
- Does it depend on popup/window behavior?
Requests about the landing page, launch flow, background presentation, release content, public request visibility, and repo-linking should start here.