HTML/CSS to Image Blog
How HCTI handles runtime performance, download size, trimming, loading experience, and browser testing for a production Blazor WASM editor.
How HCTI uses MemoryPack, read-time schema repair, and MagicOnion to store and transport a deeply typed template model.
How HCTI turns typed template models into deterministic CSS shared by a Blazor editor and a server-side HTML renderer.
How HCTI kept Handlebars for content while extending template variables to colors, sizes, images, and other strongly typed editor properties.
How we integrate TypeScript into a Blazor WebAssembly application without making the two runtimes fight over state, rendering, or browser interactions.
How the HCTI template editor uses generated paths, typed tracking facades, transactions, and separate preview state to manage complex edits.
How typed models, Roslyn-generated property descriptors, shared input components, and common rendering contracts keep a large Blazor editor consistent.
How we designed a browser-based template editor around typed models, efficient change tracking, code generation, deterministic CSS, and testability.
Learn about how our new editor offers the best of both worlds: rich interactive visual design while keeping things grounded in HTML/CSS implementation.