What it does
Generate correctly sized, themed PowerPoint templates and test decks for an LED wall. Type the wall's resolution and it works out a slide the application will actually accept: PowerPoint caps a slide edge at 56 inches, which is a schema limit rather than a fussy dialog, so a 7680 × 1080 wall wants an 80-inch slide it will not make. The answer is to build at half size and export at 2× — and the build scale is always a whole number or a whole reciprocal, because "build at half and export at 200%" is an instruction a person can follow at 2 a.m. and "build at 1/2.37" is not. Keynote's limits are different and were measured by asking Keynote until it refused: 8192 pt against PowerPoint's 4032, so the same wall it simply holds at 1:1. Themes carry the event's own colours, fonts, logo and background, and the optional test deck renders its patterns at the wall's exact raster. Everything happens in the browser — there is no backend, so a client's unannounced logo has nowhere to be uploaded to.
Where it stands
In development. Four generated decks have been opened in a real Microsoft PowerPoint and a real Keynote on macOS: none raised a repair prompt, PowerPoint reported their slide widths as 40.00″, 20.00″, 11.25″ and 40.00″ — the computed values exactly — the .potx opened as a new untitled presentation, and a full-bleed picture measured 2880 × 810 pt against a 2880 × 810 pt slide. Keynote's 200–8192 pt range was measured by asking Keynote until it refused. Every XML part is parsed by xmllint in CI. No deck produced by this has been played out to a real LED processor or wall and measured — the slide is the right size, and what a playback machine does with the picture is not something this can tell you.