rythm-path-five.webflow.io
Rythm is the marketing site of a creative branding studio that packages design, strategy, writing and marketing into brand experiences, and it speaks to founders and marketing leads shopping for an agency partner by walking them through the team, the case studies, the journal and a contact path that ends in a scheduled call. The published site runs on Webflow, with its projects, journal posts and team profiles driven by CMS collections behind a single shared page shell.
The palette is close to monochrome: warm off-white and pale grey grounds, near-black ink for type and buttons, occasional deep charcoal bands for contrast, and no accent hue beyond that restraint. Typography pairs a large, tightly-set sans headline voice in sentence case with small uppercase eyebrows and meta labels carrying wide letter-spacing, over quiet grey body copy at a modest size. Composition works in full-width horizontal bands stacked down a long scroll, several of them white cards that overlap the band above, with generous whitespace, two-column splits that pin an intro beside a scrolling list, and even three-up card grids. Element shapes stay simple and geometric: square-cornered cards and tiles, hairline rules and thin bordered boxes, fully rounded pill buttons and outline links with underline rules, plus small circular avatars and icon wells.
Scope at a glance
How the 28 pages break down
9 unique layout pages to build
Complexity assessment
Nothing here is a judgement call — every rating comes from thresholds over the numbers above.
Content model
3 collections, each with a single dynamic segment in its route. Collections like these map almost one-to-one onto document types in Sanity or collections in Payload, and the route patterns themselves tell us what the slug fields and templates need to be.
Page composition
28 distinct section types across 60 instances is a wide surface, and it is wide rather than deep — 19 of those types appear exactly once. A section used once still needs a schema, a component and a round of visual QA, so a long tail costs nearly as much as a reused set of the same size while giving back none of the leverage. 8 types appear both as free-standing page-builder blocks and inside collection template pages, so those components have to accept content from two different sources — worth deciding deliberately at the start rather than retrofitting later.
Design system & assets
One typeface, Montserrat, pulled from Google Fonts in 9 weights and 2 styles — nothing licensed, nothing self-hosted, nothing to re-purchase, and next/font handles it with no layout shift. The media library is 84 unique images, with no video anywhere on the site. The only real task here is re-hosting: the assets are served from cdn.prod.website-files.com and d3e54v103j8qbb.cloudfront.net, and those URLs stop working when the site is unpublished.
Forms & integrations
One form collects input, and it does not post to an endpoint of its own — Webflow's built-in submission handler takes it. That means there is nothing to point the new site at, and the new site has to bring its own handler, spam protection and notification routing, plus an export of the submissions already collected.
Content volume
22 published documents across 3 collections. That fits into a single automated migration pass with room to review every record by hand afterwards, and it keeps the content freeze short.
Content model
3 collections make up the CMS side of this site. Each is rendered through a single collection template page that every document in it reuses, so the documents below differ in content, not in layout.
Section library
The 9 unique layout pages are built from 28 distinct section types used 60 times in total: 9 types appear more than once, 19 appear exactly once, 8 are used both as page-builder blocks and inside collection template pages, and 10 exist only inside a collection template page.
Instances per type, most-used first
Green bars are reused types. Grey bars are the long tail.
Page composition
All 9 unique layout pages, top to bottom, as the sections each is built from. Globals are marked G — they are authored once and reused everywhere.
Global sections
2 sections are shared rather than placed per page. They wrap every page-builder page and all three collection template pages, so each is authored once and reused everywhere.
Site Header
9Fixed top navigation bar with the RYTHM wordmark, Projects/Services/Company menu, a social dropdown circle and a Let's Talk pill button.
Site Footer
9Footer with the RYTHM brand block and blurb plus Learn More link, Email and Phone columns, and a bottom credits row with legal links.
Forms
One distinct form collects input on this site, listed below with the fields it submits.
Contact enquiry
Media & typography
Everything the pages load: the images and video behind the layouts, and the font families the type is set in.
Alt text coverage
That accessibility and SEO debt is copied into the new site verbatim unless it is addressed. The migration is the cheapest moment to fix it — but writing alt text is manual content work.
Typefaces
1 familyNothing licensed, nothing self-hosted, nothing to re-purchase — next/font handles it with no layout shift.
Risks & watch-outs
Each one fired from a rule over the counts above — none of them is a hunch.
Form submissions have nowhere to go after cutover.
The one form on this site posts to Webflow's built-in handler — there is no external endpoint to point the new site at. Plan for: a form handler, spam protection, notification routing, and an export of existing submissions before the Webflow subscription lapses.
Every image lives on the platform's CDN.
All 84 images are served from cdn.prod.website-files.com, d3e54v103j8qbb.cloudfront.net. Those URLs stop working when the site is unpublished. Plan for: re-hosting assets into the new CMS as part of the content migration, not after it — this is automated by our migration tooling, but it has to happen before the old site is switched off.
84 of 84 images have no alt text.
That accessibility and SEO debt will be copied into the new site verbatim unless it is addressed. Plan for: the migration is the cheapest moment to fix it, but writing alt text is manual content work and should be scheduled as such.
8 sections are used in two different ways.
They appear both as page-builder blocks and inside collection template pages. Plan for: components designed to take either author-picked content or CMS-referenced content, decided before they are built rather than retrofitted.
Interactive behaviour is not visible to static analysis.
Accordions, marquees and carousels are Webflow interactions; this report sees their markup, not their motion. Plan for: a short pass to spec and rebuild animations, sized after a walkthrough of the live site.
The CMS field model is inferred from rendered pages.
With 22 published documents, fields that exist in Webflow but are not rendered by any template are invisible to this analysis. Plan for: a short review of the source field list against the proposed schema before content migration starts.
28 URLs need a redirect map.
Route patterns are stable and map one-to-one, so this is bookkeeping rather than a problem — but it is a launch blocker if it is skipped.
How the migration runs
Page discovery
All 28 published pages are split into 6 page-builder pages and 3 collection template pages — 9 unique layout pages in all.
Asset extraction
The 84 unique images are pulled off the source CDN with their metadata, along with the one font family the site is set in.
Schema & content
The content model is derived from the 3 collection template pages and the page structures first, then the 22 collection documents and the content of all 28 pages are extracted against it.
Section generation
A component is generated for each of the 28 section types, the 2 shared globals and the one form.
Project & seeding
The target project is generated from those schemas and components, and seeded with the extracted content and assets.
Migrate this site yourself
The analysis above was produced by our open pipeline, and the migration itself has open tooling too. If you want to see the shape of the output before talking to anyone:
Go through the risks
line by line with us
FocusReactive is a Next.js and headless-CMS migration agency. We move enterprise sites off legacy monoliths and visual builders — Webflow, Framer, WordPress, AEM — onto Sanity, Payload CMS, Storyblok and MedusaJS, and we do it without losing traffic, rankings or a publishing day.