Skip to content
09 — Platform · Creator Tools · Content SystemsSupporting project

Making a website builder start closer to finished

Improving Learnyst’s website-template system so creators could start from relevant, responsive structures instead of a generic library with inconsistent quality and weak discoverability.

Role
Product Designer — collaborative project
Status
Shipped project
Scope
Template design · Information architecture · Content structure · Visual design · Responsive design · Research · Prioritisation
Website templatesSynthetic education brands · reconstructed thumbnails
Organised by the business the creator runs
The generic library, then the same library organised by the business the creator runs. Synthetic education brands.

Some product visuals have been simplified or reconstructed to protect confidential platform and customer information.

A collaborative project. Website and page cleanup and template creation were shared with another designer; I owned the demand-data analysis, segment blueprint prioritisation and competitor benchmark review.

Chapter 01 — The audit

More templates were not automatically a better starting experience.

The audit found eleven website templates and a section library of 220 sections that was heavily unbalanced. The count was never the problem.

What the audit actually found
Not every segment had templatesQuality varied significantlyNo defined blueprintsNo consistent structureOutdated pages mixed inPoor naming, no tagging

Organize templates by user intent, not builder terminology.

Chapter 02 — Naming

“Squeeze page” is a builder’s word.

“Lead & enrollment” is what the creator is actually trying to make. Organising by intent rather than builder terminology is most of the improvement.

Builder language — the old tabs
Landing pages
Product pages
Squeeze pages
Custom pages
Creator language — the proposed structure
Home pages
Course & batch pages
Lead & enrollment pages
About & trust pages
Utility pages
Custom / blank
Chapter 03 — Prioritisation

Build where customer demand is highest first.

Segment priority came from response data rather than designer preference. Template creation was prioritised against this ranking — the part of the project I owned.

Ranked by responses
Upskilling2,069 responses
Coding1,050 responses
UPSC864 responses
Skill development740 responses
State level exam682 responses

Five of the ranked segments from the response data.

Chapter 04 — Quality

A template wasn’t done when it looked finished.

Four things had to be true before it could be published — and two of them are about being found, not about design.

01Segment blueprintContent and sections aligned to the segment’s actual page structure
02Visual systemMultiple design variations, held to one standard
03ResponsiveVerified behaviour across breakpoints
04DiscoverabilityCorrect naming, tagging and a professional preview thumbnail
Publishable template

Adding more templates before cleaning the library would scale the problem.

Audit, rename, tag — then fill the gaps. Expansion last, because a bigger library with the same taxonomy is just a harder library to search.

Order of work
01Audit — keep, improve, rebuild or remove
02Rename — names a creator would recognise
03Tag — segment and page family
04Fill gaps — only then, add what’s missing
Shipped project

The template system moved toward the creator’s business.

Templates organised by creator intent, prioritised against real demand and held to a quality contract. Publication-rate, CSAT and generation improvements were measurement plans in the project documents, not confirmed outcomes — so none are claimed here.

This project taught me that platform quality is not only the quality of each template — it is also naming, taxonomy, prioritisation and the ability to find the right starting point.

Have a complicated product problem?

Platform architecture, AI features, real-time systems, or a product that has grown more rules than anyone can hold in their head.

Or write it here

This opens your own email client with the message filled in. Nothing is sent or stored by this page.

Pragya Kumari — Product DesignerPlatform · Creator tools · 2026