How to Layer Curtains with Valances, Tiers & Shades

Vermont Country Store — Oracle Commerce Cloud
Role: Frontend Developer / OCC Implementation
Live URL: [vermontcountrystore.com/signature-products-how-to-layer-curtains-with-valances-tiers-shades](https://www.twine.net/signin

What This Was

A static promotional page supporting VCS’s curtains category expansion after becoming the exclusive seller of the Country Curtains brand. Part of the Signature Products series — VCS’s editorial format for content-first shopping guidance — built outside the standard catalog templates, directly in OCC Admin using custom HTML and CSS.

What I Built

Structured the page to walk shoppers through the layering decision in the order they’d actually think about it: why to layer → treatment types defined → how they work together → product CTAs. This required mapping VCS’s full curtain taxonomy (valances, swags, panels, tiers, sheers, Roman and roller shades) into a layering logic that was both educationally accurate and merchandising-aligned.

Many VCS curtain styles ship as coordinating families — valance, tier, panel, swag, and door panel designed to mix and match but sold separately. I cross-referenced OCC SKU data and category structures to map those relationships and surface them accurately in the page content.

OCC static pages don’t have a dedicated UX or content layer, so page hierarchy, copy, cross-link strategy, and CTA structure were all developer-level decisions on this project.

Code Sample

The layering-combination card pattern, reused across each pairing section:

<div class="layer-combo-card">
  <h3>Valance + Sheer + Tier</h3>
  <p>Light, airy, and ideal for kitchens or bedrooms wanting
  privacy without blocking natural light.</p>
  <a href="/curtains/category/valances" class="cta-link">Shop Valances</a>
</div>

Constraints

• Vanilla HTML/CSS only — no framework, no custom JS
• All HTML authored through OCC’s content editor (no direct filesystem access)
• Scoped to VCS’s existing global stylesheet — no shared CSS modifications
• All images managed through OCC’s media asset library
• SEO requirements: clean URL, indexable, proper heading hierarchy, internal link structure

Why It’s Interesting

Static pages in OCC are deceptively complex. The platform is built for catalog pages, so editorial content outside that structure requires understanding both the content slot architecture and how to make non-catalog pages feel native to the storefront. The result functions as editorial, performs as commerce, and is indistinguishable from the VCS design system.

Oracle Commerce Cloud OCC Admin ATG HTML CSS Enterprise Ecommerce Content Architecture UX Writing SEO

Role — Frontend Developer