tarun.codes

A Planter's Daughter

2024

A data-dense botanical store on Horizon, with apothecary pages driven by metafields so new ingredients and stories are content edits, not code.

Client

A Planter's Daughter

Role

Theme developer

Service

Custom theme · Liquid · Horizon · OS 2.0

A Planter's Daughter cover

Work Details

The brief

A Planter's Daughter is the third build with the Pallavi Nopany team, and by now the pattern was set: a beautiful, exacting design file, and a build that has to match it completely. What changed was the foundation. This time I built on Horizon, Shopify's new theme generation, chosen because it is flexible all the way down: every block and snippet is reusable, so layouts get assembled from parts instead of rebuilt per page.

The build

The hard part of this store is data density. Pages like the apothecary carry serious content: each entry has its own ingredient list, properties and story, all of which has to render consistently and stay editable by the team. I modeled that content properly in Shopify (metafields feeding shared section patterns) rather than hardcoding it, so adding a new ingredient or product story is a content task, not a development task.

A Planter's Daughter detail 1
A Planter's Daughter detail 2

The result

Technically it follows the same discipline as my other OS 2.0 builds: one shared section schema pattern so the editor experience is consistent, reusable blocks that slot into any template, and responsive srcset imagery so uploads never ship oversized. Same designer, same fidelity bar, new architecture, and a store the team extends by composing blocks.

A Planter's Daughter solution