A server-rendered site and headless CMS for a light-gauge steel frame manufacturer, built page by page for paid search and organic ranking rather than as a brochure.
ResultAn ad-ready site the client edits without a developer
The impact:
6
SEO landing pages
SSR
Rendering
2
Deploy targets
0
Manual deploy steps
What this product is.
A2 LSTK-Stroy manufactures, delivers and installs light-gauge steel frames. The site is the company's primary sales channel: six purpose-built landing pages covering production, contractors, portfolio, project detail and pricing, each written to convert paid traffic and to rank on its own terms.
PROJECT FACTS
IndustryConstruction & Manufacturing
Product TypeMarketing Platform
PlatformWeb
RenderingNuxt 4 SSR
ResultAn ad-ready site the client edits without a developer
What needed solving.
A construction manufacturer buys expensive regional ad traffic, and every click that lands on a slow or thin page is money burned. A client-rendered single-page app would have handed search engines an empty shell. The client also needed to publish new portfolio projects and prices themselves, without waiting on a developer or risking the ad campaigns.
How we approached it.
We built the frontend as a Nuxt 4 server-rendered application on Firebase App Hosting, so every page arrives as complete HTML for both crawlers and first-paint speed. Content lives in Firestore behind a FireCMS admin the client's own team operates, and the two apps deploy independently from a single push to master. Firestore and Storage rules are the security source of truth and are verified against the emulator in CI before they can be deployed.
A2 LSTK Steel Framing on a device
What's inside?
Six pages, each with a job
Home, production, contractors, portfolio, project detail and pricing — separate entry points so ad groups land on matching content.
Server-side rendering throughout
Nuxt 4 SSR on Firebase App Hosting delivers complete HTML to crawlers and users alike, not a JavaScript shell.
Client-operated CMS
A FireCMS admin deployed to its own hosting site lets the company publish portfolio projects and update prices with no developer involved.
Portfolio with per-project pages
Every completed frame gets its own indexable URL, turning delivered work into long-tail search traffic.
Rules tested before they ship
Firestore and Storage security rules run against the emulator in CI and deploy without force flags, so a bad rule fails the build instead of the site.
Push-to-deploy on one branch
Master is the only long-lived branch; a merge rebuilds the SSR backend and redeploys the CMS through shared reusable workflows.
Tools change. Standards don’t.
We choose the stack around the product — not the other way around.
We worked on the product development and implementation, focusing on building a polished, functional and user-friendly experience aligned with the goals of the product.
