How Rise Canvas was created

Testing the output

Testing the builders followed a consistent pattern for each new component:

1. Build the component in the builder UI with a range of content

2. Copy the HTML output

3. Paste into a real Rise course as a code block

4. Preview in Rise on both desktop and mobile viewpoints

5. Check keyboard navigation works

6. Check the output still looks right if Rise changes its surrounding styles

This cycle repeated for every component and for every significant change. Bugs found at this stage were commonly, template literal escaping issues, CSS specificity conflicts with Rise’s own styles, or interaction timing problems with Rise’s (sometimes) lazy-loading behaviour (sorry articulate!)