A Tailwind UI for comparing broken and passing transactional email checks

[awslew]

I built InlinerAPI's web UI with Tailwind CSS and Next.js. It lets developers compare rendered email HTML with explicit expectations for amounts, links and conditional content. I'm the solo maker; this introduction is AI-assisted.

The interface puts the HTML draft, selector-based requirements and per-rule results in one workflow. My usability goal is that a first-time visitor can identify a failed requirement and understand the corrected result without setting up an account.

Try the existing free demo: choose Order receipt, then Load broken example and Preview requirements. The synthetic EUR case reports Blocked · 4/5 passed for a wrong total. Load passing example followed by preview reports Passed · 5/5 passed for that case.

If you run this comparison, which control, label or result is hardest to understand? Please describe the step you actually reached, including an unfinished attempt. Written replies here are enough.

Tailwind styles the application interface. The checks inspect HTML source and supplied expectations; they don't establish Gmail/Outlook appearance, delivery, real billing correctness or coverage of every email variant.