Six words, and then we can be precise
You do not need to write code to build blocks, but you do need to name things accurately. These six words are the entire technical vocabulary this course assumes, and every one of them comes back.
Building Interactive Rise Blocks with Claude Code
You do not need to write code to build blocks, but you do need to name things accurately. These six words are the entire technical vocabulary this course assumes, and every one of them comes back.
The embed tool Rise uses to drop custom HTML blocks into a course as a web object, no plugin required.
Everything you build in this course ends its life as a zip handed to Mighty.
The sandboxed window your block runs inside. It cannot see or touch the rest of the Rise page directly.
This isolation is a gift and a constraint. It is why your block cannot break the course around it, and why it cannot resize itself without asking.
The browser API a block uses to safely talk to its parent page, for example to report its own height.
The one line of plumbing every block in this course carries.
Accessible Rich Internet Applications: attributes like role and aria-live that tell assistive technology what your widget is doing.
The defect in the last lesson was a missing ARIA attribute. It will not be the last time.
Named CSS variables such as --ink or --accent that keep colour and spacing consistent across every block.
Define them once at the top of the file and the whole block inherits a house style.
Building and testing a block on its own, with sample data standing in for anything a real course would provide.
You will build every block this way, which is why none of them need Rise to be running to work on.
Two of these, the iframe and postMessage, explain almost every strange thing a block does. Keep them in mind through the next check.