Final project — Accessible welcome screen

PART I

Warm-up

Reconnect with a useful idea before starting explain, improve, and resubmit. In one or two sentences, describe the input, output or host boundary from the previous exercise that this lesson builds on. If you are arriving directly, skim the worked example first; there is no locked prerequisite.

A rough note is enough. You can revise it after the example.

PART II

Instruction & guided example

Deliver an accessible-welcome design with honest review limits

The final public artifact should be useful for a real later review. Package the fixed-text design, audience/purpose, exact content, source ownership path, activation contract and concrete acceptance cases. Accessibility is a product goal that requires supported native behavior and observation; this website cannot certify it by inspecting a configuration.

A complete sample packet uses Welcome to the workshop. Start with one route; records one text component in a column; names main and the host’s show invocation; includes normal-content inspection complete, narrow/long-text native review pending, assistive-technology review pending and unavailable-target behavior unresolved. It also states no account lookup, persistence or game mutation is implemented. This lets a future reviewer see both the design and the remaining work.

Personal practice completion remains available even while real-host checks are pending. That lenience helps learning and does not change evidence standards. Keep drafts exportable through the school’s browser-local progress controls; exported practice is your writing, not a private grade or native test report.

Worked reasoning and supplied artifact

import wuix.widget.button;
import wuix.layout;
domain Login {
    const screen = {
        layout: { type: "column", padding: [24,32], gap: 16 },
        components: [{ type: "text", value: "Welcome to the workshop. Start with one route." }]
    };
    fnc show() -> void {
        wuix.mount("main", screen);
    }
}

Illustrative example from the proposed WillowScript design. The language and WUIX/WMATH/WDB/WAUDIO/WTMP services are not implemented in the supplied source. This site has no interpreter, VM or native host and does not execute or certify the snippet.

Try the guided change

Build the sample packet and identify the next host review that would most reduce uncertainty about the intended user experience.

• Write the supplied inputs and initial state before following the example.
• Reconstruct each intermediate calculation or host decision, then compare with the worked artifact.
• Explain why the contrasting alternative fails before attempting the changed inputs in Part IV.

PART III

Take a breather

Step back after the guided example. Look away from the screen, stretch, or reread your prediction. This is an optional learning pause, not a timer or an assessment gate.

When you return, try to name the lesson’s key idea without copying its wording. If that feels difficult, return to Part II and trace one line rather than restarting the entire lesson.

PART IV

Independent practice

Project context: Accessible welcome screen. Build a small, understandable change around explain, improve, and resubmit.

Submit your own final welcome design for a specific mod workshop. Include required text, source draft, ownership/activation map, three distinct acceptance cases, accurate evidence statuses and a prioritized next native accessibility review.

What to produce

A complete review packet that another learner can inspect and a future host reviewer can use without reconstructing assumptions.

• State the intended behavior in a sentence before editing.
• Use only source-backed syntax and the host services whose contract you have been given.
• Record a normal case and a boundary or unavailable-resource case.
• Label hand predictions separately from anything actually measured in a supplied toolchain.

Syntax colors are a reading aid, not a compiler. The line you are editing stays uncolored until you move to a different line; capitalization is never changed. Drafts stay on this browser and code is not executed.

import wuix.widget.button;
import wuix.layout;
domain Login {
    const screen = {
        layout: { type: "column", padding: [24, 32], gap: 16 },
        components: [{ type: "text", value: "Welcome back" }]
    };
    fnc show() -> void {
        wuix.mount("main", screen);
    }
}

PART V

Self-check

Use this check to notice what to revisit. It does not award a private course grade, block another page or claim to verify compiled code. Every answer has a learning explanation.

You may keep exploring even if you are unsure. Use the hint, compare the trace, and revise your explanation.

PART VI

Recap & small task

Bring the idea back to the mod feature you are building. A useful recap connects the mechanism to a decision you can make in your own code.

• Deliver an accessible-welcome design with honest review limits
• The final public artifact should be useful for a real later review. Package the fixed-text design, audience/purpose, exact content, source ownership path, activation contract and concrete acceptance cases. Accessibility is a product goal that requires supported native behavior and observation; this website cannot certify it by inspecting a configuration.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Write the next real-host review condition and the evidence you would record if it were supplied.

This marks your personal practice record only. It is not a certification or an official workspace assessment.