Sixteen weeks of real Corporate IT work. Practice stays on your machine and stays yours. The competition is scored on the server, and that is the part that counts.
Week 4 has eight activities. These four are the ones that carry the week, and the last of them is the hand-in. Work them in the order they are numbered.
Six pages, a real selector, and a site that gets redesigned under you. 480 XP.
OpenThe hand-in gate. Checks whether the team's evidence is complete, traceable and safe enough for facilitator review.
OpenAcross the sixteen week plan.
What the lab reports without asking you.
Lab work and the arcade land on the same board, because they are the same skill measured twice. It reads from the record, so it cannot drift from it.
Seat names and scores are placeholders on this preview page.
Week 4 is data gathering and the register, so week 4's game is collecting data under a clock. It is not a break from the week. It is the same week, faster.
fx.js and fx.css give a learning page the
same feel language the weekly games already have: synthesized sound and small transform-and-opacity
animations, nothing else. Nothing below is wired into a real page yet. This is where each effect is
heard and seen on its own, before the next pass puts any of it to work.
Toggling this writes to the exact same key
jz_play_muted_v1 that every game's own sound button reads and writes. Mute it here,
open a game page, and the game opens muted too, and the other way round.
Synthesized with WebAudio, no audio file. Each one starts only after you press its button, which is the same rule the browser itself enforces: no sound before a real click.
A soft tick for a step or a selection.
A rising two note for a correct answer.
A flat low tone for a wrong answer.
A short chord for finishing a section.
A light tone for revealing or opening something.
Transform and opacity only. Every one of these turns off under your system's reduced motion setting, and the element it touches ends up in the same correct place either way.
A small ring at the point of contact, for a press.
A brief scale up and back, for a state change.
A short side to side move, for a wrong answer.
A number climbing to its final value.
A bar filling to a fraction, on a transform, not a width.
A page that paints part of its own body from JavaScript, which
is most of this lab, adds elements after fx.js has already run its first pass.
Fx.scan() re-checks the page for anything new, the same job Motion.scan()
already does for scroll reveal. The button below actually appends a new counter to the page and calls
Fx.scan() on it.
Every control on this page calls the real Fx module
shipped in fx.js. Nothing here is a mockup of an effect the module does not have.