Case study · Tech education
One template, a landing page for every role.
Scaler wanted a landing page for each role they teach. We built one landing page template driven by the CMS: their team fills in the role data, and a new landing page is created from it.

The problem
Many roles,
one page each.
Each role Scaler teaches needs its own landing page to rank and convert. Designing and building every page by hand would not scale.
What we did
What we built
for Scaler.
One landing page template
A single template holds the layout, sections and calls to action for every role page.
Pages created from the CMS
Role data goes into the CMS, and each item becomes its own landing page.
SEO on every page
Titles, descriptions and headings come from the role data, so every page is ready for search.
Inside the build
Data in,
pages out.
The template reads every field from the CMS, so a new role page needs data, not design or development time.
Results
What it means for the team.
Scaler can launch a landing page for a new role by filling in the CMS, with the same layout and SEO setup as every other role page.

Next


