Lucy & Yak: Component-Based Content for a Shopify Rebuild

May 29, 20265 min read

Outcome

A component-based Lucy & Yak store rebuilt on Shopify 2.0, with a content model that gave the brand's own editors day-to-day control of the experience without developer intervention. The structured approach replaced a fragmented, plugin-heavy legacy site with a fast, modular system designed to flex as the brand evolved.

Client

Lucy & Yak, a values-led, gender-neutral fashion brand known for its dungarees and its strong sustainability and community ethos. The work was delivered through Absurd, a digital agency, as a full design and build of the brand's customer-facing Shopify commerce store. Leading on the delivery of the engagement from the agency side, I managed the team remotely and worked directly with the tech team on the app audit and integration recommendations across the stack.


The brief

The existing lucyandyak.com needed rebuilding to improve customer experience, site speed, and ultimately conversion. The brand had grown quickly, and the site carried the legacy of that growth: a fragmented set of plugins and apps, inconsistent content structures, and a front end that wasn't serving the brand's distinctive voice or its customers' shopping behaviour.

The rebuild moved the store onto Shopify's Online Store 2.0 architecture using the Dawn theme framework, with its JSON templates, modular sections, and native metafields. This was a shift from a page-bound site to a component-based, structured-content approach.


Strategic considerations

Three tensions shaped every decision:

Headless ambition vs Shopify 2.0 pragmatism. The discovery phase evaluated a fully headless rebuild against Shopify 2.0's evolving native capabilities. The cost-benefit analysis pointed to Shopify 2.0 with the Dawn theme framework: a deliberate architectural choice that traded some long-term flexibility for delivery speed, native commerce features, and a much stronger editor experience. The deeper work then was making sure the component-based content model still delivered the structural rigour a headless build would have given.

Structure with editor freedom. The content model had to be structured enough to stay coherent across a growing store, and flexible enough for a non-technical team to run day to day. Too rigid and the editors can't move; too loose and the system loses integrity.

Brand voice at scale. Component-based content systems can drift toward generic. Lucy & Yak's gender-neutral point of view had to survive every reusable module, not just the headline pages. Structured content at scale still has to sound like the brand at every touchpoint.


Approach

Leading on the delivery of the engagement and managing the team, my focus was on the content layer alongside the integration recommendations: how content would be structured, modelled, and made manageable by the brand's own editors after launch.

The work began with discovery. We reviewed the existing technical stack and the full set of Shopify apps powering the store, from search and product recommendations to reviews, wishlists, stock notifications, and loyalty. Each was assessed against a clear question: does this serve customer experience and conversion, or is it adding weight without value? The app audit produced specific recommendations: replace some (search moving to a more customisable, customer-tracking solution; product recommendations rebuilt for editorial control), retain and re-implement others through their APIs for performance, and remove those that Shopify 2.0's native functionality now made redundant.

The content modelling sat at the heart of the build. Working component by component rather than page by page, we defined the structured content for each part of the store: the home page modules, collection pages, product pages, content sections, and blog. Each component was specified with its content fields, image aspect ratios, and acceptance criteria, then documented as user stories for the development team. Where components were reused across templates, we modelled them once and composed them flexibly, which is the core efficiency of a component-based approach.

A guiding principle throughout was editor empowerment. Shopify 2.0's metafields and section architecture meant the brand's content editors could reorganise, add, hide, and customise content blocks without developer intervention. Hero messaging, collection grids, navigation, and product information could all be managed in the back office. The content model had to be structured enough to stay coherent and flexible enough to let a non-technical team run the store day to day.

Content also had to carry the brand's voice. The size guidance and fit recommendation content, for example, was flagged for revision to align with Lucy & Yak's gender-neutral point of view, because structured content at scale still has to sound like the brand at every touchpoint.


Impact

  • A component-based store delivered on Shopify 2.0's Online Store 2.0 architecture using the Dawn theme framework, with native metafields and modular sections.

  • Content model that empowered brand editors to manage hero messaging, collection grids, navigation, and product information without developer intervention.

  • App audit recommendations implemented: redundant apps removed, retained apps reimplemented via API for performance, and selected apps replaced with more customisable, customer-trackable solutions.

  • Documented set of component-level content models and acceptance criteria, providing a reusable foundation for future phases of work.

  • Reduced reliance on developer time for routine content management.

The shift from page-bound to component-based content modelling is what made the platform sustainable. Reusable structures, brand voice preserved at every touchpoint, and editor control built in from day one.


What it taught me

This project is a clear example of why composable and component-based thinking matters for commerce. The hard part wasn't designing beautiful pages. It was structuring content as reusable, channel-independent components that a non-technical team could manage confidently, while keeping the brand's distinctive voice intact across every module. Get the content model right and the store becomes flexible, fast, and sustainable. Get it wrong and you've simply rebuilt the old problem with newer tools.

Louise Leone

Louise Leone

Founder of Lion's Roar Studio. Senior content strategist with two decades across editorial, structured content, and digital experience. She writes in her own voice, on her own terms.

LinkedIn logo icon
Instagram logo icon
Back to Blog