MAKER KIT 1.0 / PREVIEW & INSPECTION

Make a little
landing.

One small example. Familiar controls.
A clear place to begin.

Little Landing is a finite, editable starter: move along seven stops and land at five destinations. No timer. Try it, read the source, and see how a tiny experience fits together.

Preparation only. Invitations, reuse terms and a removal contact remain pending. This kit does not accept submissions.

LITTLE LANDING01 / 05

A small move.
A satisfying arrival.

Illustration of the first destination: start at stop 4, head for stop 6. The playable starter is linked above.

01 / OPEN THE BOX

Change one thing.
Play it again.

Run the downloaded kit

Unzip it, open a terminal in the archive’s root folder, then run:

python3 -m http.server 8000 --bind 127.0.0.1

Visit http://127.0.0.1:8000/makers/starter/. Stop the server with Control-C. Opening the HTML through file:// is not supported; the starter uses JavaScript modules.

Start with the settings

Edit CONFIG in makers/starter/game.mjs. Defaults: seven stops, start index 3, target indices [5, 1, 6, 2, 4]. Indices start at zero; visible stop numbers start at one.

Keep the interaction small. Check every edited route reaches its ending and can restart. The README travels with the source.

02 / ACTIONS BEFORE KEYS

One action. Two ways in.

Keep the meaning stable

left / previous
Move one stop left
right / next
Move one stop right
action
Start / land / resume / play again
pause
Pause or explicitly resume

up, down and pad1–pad4 are reserved and unused here. Keyboard and on-screen buttons call the same semantic action path.

Give the page its space

createController({ onInput, isActive }) reads the shared browser mapping. onInput(actionId) receives meaning, not a device identity; getMappings() supplies current key codes for labels.

The starter owns focus, pause and visibility handling. Leave Tab, text fields and modifier shortcuts alone. It reads mappings without rebinding or resetting them; reload after changing mappings elsewhere.

03 / A FINITE REVIEW

Small enough to inspect.

Use the downloadable checklist. A checked box needs a recorded result.

  1. Finish & retry. Complete every destination, exercise wrong-stop feedback, pause, resume and restart. Recheck changed settings.
  2. Respect input. Test default/custom mappings, keyboard, touch and pointer; outside focus, hidden tabs, forms and shortcuts must stay safe.
  3. Make it readable. Check visible focus, text alternatives, contrast, large controls, reduced motion and status announcements. Never rely on color alone.
  4. Keep it private. No accounts, telemetry, network APIs or saved play history. Play with storage blocked; confirm no mapping writes.
  5. Inspect the package. Check every asset’s source, credit and permission, measured size, external requests and extracted-kit operation.
  6. Record the limits. Check desktop, 390px and 320px. Name browser, OS and input method. Emulation does not verify physical phones, Micro gameplay, sound or lights.

04 / BEFORE ANY CONTRIBUTION

Good work needs clear terms.

Credit begins with a record

This first-party example is credited to PointCast, led by Michael Hoydich. Source is available for preview and inspection; no project license or reuse terms are granted here. Clear code, asset and brand rights before public redistribution.

Before third-party hosting, agree attribution, permissions, review scope and a working removal contact. Record original and third-party assets separately. Three invited maker prototypes remain pending; none is represented by this starter.

A removal process to prepare

The operator records the request and affected version, pauses promotion, disables the affected entry when needed, preserves review evidence privately, and removes disputed assets through a verified release. Record the resolution and check public links afterward.

The receiving channel, operator and response terms remain unagreed. Set them before invitations or hosting outside work. There is no upload form or removal inbox in this kit.

Independent PointCast project. No OpenAI or Work Louder affiliation or endorsement. See the dated compatibility evidence before making hardware claims.