Freelance › Projects › Web development › Web programming › Fast Jamstack Site Rebuild — Astro or Next Static Export
Fast Jamstack Site Rebuild — Astro or Next Static Export
Employer
Dmytro
Project parameters
Type of cooperationOne-time project
SectionWeb development, Web programming
Prepaymentwithout prepayment
Payment methodsCash, Bank transfer
Acceptance of requestsfrom today, 04:01 until Sep 7, 2026
Project description
We run a marketing and blog site that has grown slow and heavy over the years, and we want to rebuild it from the ground up as a fast Jamstack application. Your job is to take the existing pages, structure, and content and reimplement them using static site generation, either with Astro or with a Next static export, whichever you can justify for our case. The goal is a site that renders instantly, ships almost no unnecessary JavaScript, and scores in the green across every Core Web Vitals metric on both mobile and desktop. Design, copy, and information architecture already exist, so this is primarily an engineering and performance task rather than a redesign, although we welcome sensible improvements to markup and semantics along the way.
Content must come from a headless data source rather than being hard-coded, so editors can keep publishing blog posts and landing pages without touching code. You will model the content types, wire the build to pull from that source at generation time, and produce fully static HTML for every route. We expect clean, accessible, semantic markup, responsive images with modern formats and correct sizing, careful control over fonts and third-party scripts, and a sensible caching strategy at the CDN edge. Deployment should be automated so that a content change or a code push triggers a rebuild and publishes to the CDN without manual steps. Please document how the pipeline works so our team can maintain it.
We care about measurable results, not just a framework swap. Before and after, we want real numbers: largest contentful paint, cumulative layout shift, interaction latency, total blocking time, and payload size, measured on representative pages and throttled connections.
— Static generation of all marketing and blog routes with Astro or Next static export
— Headless data source for posts and pages, modeled and wired into the build
— Responsive images, optimized fonts, and minimal client-side JavaScript
— Automated CDN deploy triggered by content or code changes
— Documented pipeline plus before and after Core Web Vitals reports
Content must come from a headless data source rather than being hard-coded, so editors can keep publishing blog posts and landing pages without touching code. You will model the content types, wire the build to pull from that source at generation time, and produce fully static HTML for every route. We expect clean, accessible, semantic markup, responsive images with modern formats and correct sizing, careful control over fonts and third-party scripts, and a sensible caching strategy at the CDN edge. Deployment should be automated so that a content change or a code push triggers a rebuild and publishes to the CDN without manual steps. Please document how the pipeline works so our team can maintain it.
We care about measurable results, not just a framework swap. Before and after, we want real numbers: largest contentful paint, cumulative layout shift, interaction latency, total blocking time, and payload size, measured on representative pages and throttled connections.
— Static generation of all marketing and blog routes with Astro or Next static export
— Headless data source for posts and pages, modeled and wired into the build
— Responsive images, optimized fonts, and minimal client-side JavaScript
— Automated CDN deploy triggered by content or code changes
— Documented pipeline plus before and after Core Web Vitals reports
