docs: move design/roadmap docs to the wiki, trim the repo root
The repository root carried 11 large Markdown files (~330 KB); most were long-lived design records rather than things a newcomer needs on first contact, which buried the README and mixed "how to use Ludic" with "how we decided to build it." Move the design/roadmap docs to the Forgejo wiki (now enabled and populated): Events, Networking, Scenes, Lifecycle, Mobile and Syntax-redesign design records, the Bootstrap deep-dive and the Luanti roadmap, under a Home index + sidebar. Each page had its selfhost/ source links corrected for the #29 reorg and every repo-relative link rewritten to an absolute URL on main so it resolves from the wiki. All eight were current, actively-maintained records, so none were dropped. The root now holds README.md plus the two user-facing references, LANGUAGE.md and COMPILING.md; the README links to the wiki, and the remaining references in LANGUAGE.md / COMPILING.md / examples/README.md and the emit_net.ludic header comment point at the wiki pages. The emit_net.ludic change is a comment only — the seed stays byte-identical and bootstrap-cfree + the full suite (56) stay green. Closes #26 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
23726afa90
commit
c040fff8c8
13 changed files with 19 additions and 5146 deletions
10
LANGUAGE.md
10
LANGUAGE.md
|
|
@ -396,7 +396,7 @@ scopes, [`examples/lang/detach.ludic`](examples/lang/detach.ludic) for the struc
|
|||
attach/detach pair, and [`examples/lang/reason.ludic`](examples/lang/reason.ludic) for
|
||||
reason-carrying teardown. The rest of the lifecycle roadmap (value-change hooks,
|
||||
query-membership edges, keyed effects) is in
|
||||
[LIFECYCLE-DESIGN.md](LIFECYCLE-DESIGN.md).
|
||||
[the Lifecycle design](https://git.workshopsoft.io/workshopsoft/ludic/wiki/Design/Lifecycle).
|
||||
|
||||
**`@Handles` — the handlers a program drives.** Written in front of the
|
||||
`program`, `@Handles(Move)` names the handlers it uses. It parses and reads as
|
||||
|
|
@ -408,7 +408,7 @@ whole timeline), plus [`examples/lang/toggle.ludic`](examples/lang/toggle.ludic)
|
|||
(enable/disable). Scenes and their `on enter` / `on exit` lifecycle blocks are
|
||||
implemented — see "Scenes & layers" below. (An annotation spelling,
|
||||
`@OnEnter(Scene)` / `@OnExit(Scene)`, is a designed but not-yet-built convenience
|
||||
— see [SCENES-DESIGN.md](SCENES-DESIGN.md); today the hooks are written as `on
|
||||
— see [the Scenes design](https://git.workshopsoft.io/workshopsoft/ludic/wiki/Design/Scenes); today the hooks are written as `on
|
||||
enter { … }` inside the `scene`.)
|
||||
|
||||
## Events & modding (`event`, `emit`, `@On`)
|
||||
|
|
@ -469,7 +469,7 @@ if emit BeforeHurt(amount: dmg) == 0 { hp = hp - dmg } # apply only if not vet
|
|||
```
|
||||
|
||||
The full modding roadmap — the world-table reflection ABI, scoped/leak-proof
|
||||
listeners, and the sandbox — is in [EVENTS-DESIGN.md](EVENTS-DESIGN.md).
|
||||
listeners, and the sandbox — is in [the Events design](https://git.workshopsoft.io/workshopsoft/ludic/wiki/Design/Events).
|
||||
|
||||
## Records (`property`), arrays and slices
|
||||
|
||||
|
|
@ -821,7 +821,7 @@ are future work.
|
|||
Records (`property` used with `new`) and array types, `break`/`continue`, and
|
||||
argv/stderr — once listed here as near-term — are now implemented and
|
||||
self-hosting; their lowerings are in
|
||||
[BOOTSTRAP.md](BOOTSTRAP.md) §4.
|
||||
[the Bootstrap deep-dive](https://git.workshopsoft.io/workshopsoft/ludic/wiki/Bootstrap) §4.
|
||||
|
||||
## Scenes & layers
|
||||
|
||||
|
|
@ -831,7 +831,7 @@ self-hosting; their lowerings are in
|
|||
> implicit active-scene register, states numbered by declaration order, and
|
||||
> `become` as two direct calls plus a store. Richer scene features (the overlay
|
||||
> stack, scene-owned entities, scene-local state, transition parameters) are
|
||||
> designed in [SCENES-DESIGN.md](SCENES-DESIGN.md) and not built yet.
|
||||
> designed in [the Scenes design](https://git.workshopsoft.io/workshopsoft/ludic/wiki/Design/Scenes) and not built yet.
|
||||
|
||||
A program is usually several mutually-exclusive states — a title screen, the
|
||||
overworld, a battle — and the usual way to write that is a mode register
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue