All work

Template QA

A checker that loads every page of a Framer site at 7 screen widths and reports what reviewers would reject.

Role

Designer and developer

Team

Solo, AI-assisted

Timeline

1 week to the hosted pilot

Platform

Node, headless Chrome, Cloudflare

Template QA home page on a wide screen

Context

Template QA intro on a phone
Template QA intro on a phone

On Oct 29, 2026, Framer took four of my templates off the Marketplace for re-review: Quinta, Bower, Nacre Lite and Quinta Lite.

Note 1

Four templates pulled in one day is how this product started. I needed to see my sites the way a reviewer does.

Problem

Why check before you submit, on a phone
Why check before you submit, on a phone

The fixes took several publish rounds. Checking by hand, I kept missing dead links, hover effects inside code components and images in the CMS.

Note 2

Every round meant another wait for review. I couldn't see 22 pages at 7 widths by eye, so I stopped trying.

Decision

How to use Template QA, on a phone
How to use Template QA, on a phone

Every problem found by hand becomes a checker rule and a test page the same day, and each rule names the real review it came from.

Note 3

If I catch something by eye once, the checker catches it from then on.

Outcome

What a report looks like, on a phone
What a report looks like, on a phone

All four templates passed the checker on Oct 30, and Framer restored Quinta Lite, Bower and Nacre Lite that evening. On Nov 2 the checker went live as a hosted pilot at qa.shashankthigale.com.

Note 4

The hosted version matches my local runs exactly: Quinta, 22 pages, about ten minutes.

What we cut

Template QA questions, on a phone
Template QA questions, on a phone

A public list of the rules. The report says what's wrong and how to fix it, but the full checklist stays private.

Note 5

Publishing the checklist would have been easy marketing. Keeping it private keeps the checker worth running.

Template QA intro on a phone
Why check before you submit, on a phone
How to use Template QA, on a phone
What a report looks like, on a phone
Template QA questions, on a phone

Before and after

A Template QA report summaryA Template QA finding with its screenshotBeforeAfter

Note 6

One finding from a report: what went wrong, where, and a screenshot of it.

Results

7

widths checked on every page

42

issues found on Aside's first scan, all fixed before listing

3

templates back on the Marketplace the same evening

Lessons

Framer wraps every page in boxes the browser reports as hidden, so my first version quietly skipped most checks on real templates. Now every new rule is tested on a real template as well as a test page.

Next project

Aside