Loading something special...

Bancroft

Webflow Development, CMS Architecture, Dynamic Content, Information Architecture, UX

The Problem:

Website architecture and dynamic content implementation for Bancroft — restructuring the site around a CMS-driven, component-first system that enables non-technical users to manage content efficiently while maintaining design consistency, scalability, and performance.

2025
Webflow Development, CMS Architecture, Dynamic Content, Information Architecture, UX

Phase 1: Prototyping

A scalable CMS-driven website structure, improved consistency across dynamically generated pages, reduced manual maintenance for content updates, a more efficient workflow for managing and publishing content, and a foundation that supports future expansion without major rework. Key takeaway: CMS architecture should always be defined before visual implementation — proper field structuring is critical for dynamic tag functionality, and planning for scalability early prevents technical debt later.

The Problem

The existing setup lacked a scalable CMS structure for dynamic content, consistent design patterns across pages, flexible content relationships between collections, and efficient workflows for updating and managing content. Proper use of dynamic tags and templating was absent throughout the site — resulting in limited control over content presentation and constrained ability to expand without manual workarounds.

No items found.

CMS Architecture

Defined collection types and relationships to support dynamic content rendering. Structured fields to align with reusable templates and established a hierarchy that supports future content expansion without requiring restructuring. Built reusable page templates tied to CMS collections and implemented dynamic bindings for consistent content injection across pages. Configured dynamic data sources for fields including titles, metadata, and content blocks — ensuring correct binding between CMS fields and page elements.

No items found.

Component System & Dynamic Templates

Created modular components to maintain design consistency while allowing flexibility across page types. Addressed limitations in dynamic tag availability by aligning collections and fields properly. Ensured consistent behavior across multiple templates and components while avoiding overly rigid structures that would constrain future updates.

No items found.

UX & Content Workflow Optimization

Simplified the editing experience for content managers by reducing dependency on manual page edits and centralizing content in CMS collections. Improved scalability of content publishing workflows so the team could update and expand content without developer involvement. Balanced system integrity with flexibility to prevent technical debt as the site grows.

No items found.
A storyboard depicting the user journey with a dental health app. It starts with a person waking up, followed by motivation to brush teeth, using an app that tracks and encourages good dental hygiene. The storyboard illustrates various app features such as progress tracking, rewards, and a smart mirror that analyzes brushing technique.

What I Learned

1

CMS architecture must be defined before visual design begins

On Bancroft, the temptation to start with visual components was real — but the CMS structure had to come first. Collection types, field relationships, and template logic determine what's possible visually. Building the architecture before the design meant every component had a reliable data source from the start.
2

Dynamic tag limitations are a Webflow-specific constraint worth planning around

Webflow's dynamic tag availability has real boundaries — not every field can be bound to every element in every context. Understanding those constraints before designing dynamic templates prevents the frustrating late-stage discovery that a critical binding isn't supported where you need it.
3

Reusable components reduce long-term maintenance exponentially

Every time a component was updated globally rather than page-by-page on Bancroft, the time savings compounded. A site with 20 instances of a well-built reusable component is dramatically easier to maintain than a site with 20 individually styled elements that happen to look similar.
4

Scalability planning early prevents technical debt later

The decisions that create technical debt aren't usually the dramatic ones — they're the small structural shortcuts taken under time pressure. On Bancroft, treating scalability as a constraint from the first collection structure decision rather than a goal for later is what produced a system the team could actually grow without hitting walls.

Get in Touch

If you're impressed with my work, then let's make something special together

“The Website looks official and it’s Always evolving. I love it.”

-Vince Wimberly Jr.
Owner of Life Advance Fitness

Send me an email