Muumuu Dresses

Vermont Country Store — Oracle Commerce Cloud
Role: Frontend Developer / OCC Implementation
Live URL: [vermontcountrystore.com/signature-products-muumuu-dresses](https://www.twine.net/signin
Update Type: Refreshed copy and imagery on an existing Signature Products page

What This Was

An existing Signature Products page educating shoppers on muumuu styles — silhouette, length, and fabric — refreshed with updated copy and current catalog imagery. Muumuus are a category-defining product for VCS’s women’s apparel, inspired by traditional Hawaiian garments and offered in roomy, breathable cotton silhouettes from spring through fall.

What I Refreshed

Reworked the length-and-fit guidance section to be more decisive and scannable: short styles for daily wear and smaller frames, mid-calf as the versatile all-around choice, ankle-length for maximum coverage and a relaxed silhouette. The original copy described the options but didn’t clearly guide a shopper toward a decision — the refresh added that decision logic explicitly.

Updated lifestyle and product imagery to reflect current print patterns and color options, since muumuu designs rotate seasonally and the original images no longer matched live inventory. Verified all cross-links into the muumuu category page after a prior taxonomy update had changed several category URLs.

Code Sample

The length-comparison block used to guide shoppers to the right silhouette:

<div class="length-guide-row">
  <h4>Mid-Calf</h4>
  <p>The dependable all-around choice — balances coverage
  with ease of movement for everyday wear.</p>
  <a href="/womens-clothing/category/womens-muumuus" class="cta-link">
    Shop Muumuus</a>
</div>

Constraints

• Vanilla HTML/CSS only — no framework, no custom JS
• Authored entirely through OCC Admin content editor
• Bound to VCS’s global stylesheet — no shared CSS modifications
• Images sourced from OCC media asset library
• SEO-optimized: refresh preserved existing ranking while sharpening decision-stage content

Why It’s Interesting

This refresh focused on closing a gap between informational and decisional content — the original page explained options well but didn’t help shoppers choose. Tightening that guidance, verifying links after a taxonomy change, and updating seasonal imagery are the kind of ongoing maintenance tasks that keep static pages performing years after initial publish.

Oracle Commerce Cloud OCC Admin ATG HTML CSS Content Refresh SEO Maintenance Women's Apparel

Role — Frontend Developer

Best Summer Bedding

Vermont Country Store — Oracle Commerce Cloud
Role: Frontend Developer / OCC Implementation
Live URL: [vermontcountrystore.com/signature-products-best-summer-bedding](https://www.twine.net/signin

What This Was

A newly published static page in VCS’s Signature Products series, built to guide shoppers toward breathable, cooling bedding as warm-weather demand peaks. The page covers cotton percale, linen, and seersucker against the seasonal problem of overheating at night, and routes shoppers to VCS’s bedding catalog — including the exclusive Clothesline Crisp percale line and lightweight quilts and coverlets.

What I Built

Structured the page around a single, relatable problem — waking up overheated — then resolved it by fabric and product type: crisp percale sheets for breathability, linen for maximum airflow, lightweight coverlets over heavy quilts for warm-weather coverage. Cross-links targeted the percale sheet collection, the Clothesline Crisp open-stock line, and coverlets/quilts category pages.

As with VCS’s other Signature Products pages, content hierarchy and copy direction were developer-level decisions, made directly in the OCC Admin without a dedicated content or UX handoff. The Clothesline Crisp line was given particular emphasis as a private-label differentiator — a product exclusive to VCS that doesn’t compete on price but on a specific sensory promise (the “line-dried” crisp feel), which required copy that could communicate that nuance concisely.

Code Sample

The fabric-comparison block used to map sheet types to their cooling properties:

<div class="fabric-cool-block">
  <h4>Cotton Percale</h4>
  <p>Crisp, tightly woven, naturally breathable — the
  Clothesline Crisp line is exclusive to VCS.</p>
  <a href="/bedding/category/percale-bedding" class="cta-link">
    Shop Percale Sheets</a>
</div>

Constraints

• Vanilla HTML/CSS only — no framework, no custom JS
• Authored entirely through OCC Admin content editor
• Bound to VCS’s global stylesheet — no shared CSS modifications
• Images sourced from OCC media asset library
• SEO-optimized: seasonal superlative format targeting time-sensitive intent

Why It’s Interesting

Seasonal superlative pages have a narrow window to perform — they need to be live and ranking before peak search demand hits, then continue earning traffic through the season. Publishing this kind of page requires coordinating content timing with merchandising readiness (making sure linked products are in stock and priced for the season) entirely within a static page workflow with no scheduling or content automation tools.

Oracle Commerce Cloud OCC Admin ATG HTML CSS Enterprise Ecommerce Content Architecture UX Writing SEO Seasonal Content Private Label Merchandising

Role — Frontend Developer

Pajamas Buying Guide

Vermont Country Store — Oracle Commerce Cloud
Role: Frontend Developer / OCC Implementation
Live URL: [vermontcountrystore.com/tips-advice-pajamas-buying-guide](https://www.twine.net/signin

What This Was

A static buying guide in VCS’s Tips & Advice series covering both men’s and women’s sleepwear — walking shoppers through material selection by season (flannel for winter, seersucker and cotton for summer, shortie sets for warm nights) and connecting those choices to VCS’s sleepwear catalog. The page also made a case for pajamas as a genuine sleep quality investment, anchoring the purchase in wellness rather than just comfort.

What I Built

Organized the guide around the shopper’s primary decision axis: season and temperature. Content moved from cold-weather materials (Portuguese triple-brushed flannel) to warm-weather options (seersucker, cotton, shortie sets) to all-season picks, with men’s and women’s collections both represented throughout. Cross-links targeted category pages for flannel pajamas, seersucker sets, and VCS’s exclusive sleepwear brands — Eileen West and Lanz of Salzburg.

The wellness framing — sleep quality, breathability, temperature regulation — required copy that felt informative rather than promotional, while still driving to product. Content structure and voice were developer-level decisions, standard for OCC static pages with no dedicated content layer.

Code Sample

The seasonal-fabric callout pattern used to organize each material recommendation:

<div class="seasonal-fabric-block">
  <h4>Winter: Triple-Brushed Flannel</h4>
  <p>Portuguese cotton, brushed for extra softness that
  improves with every wash.</p>
  <a href="/mens-sleepwear/category/mens-pajamas" class="cta-link">
    Shop Flannel PJs</a>
</div>

Constraints

• Vanilla HTML/CSS only — no framework, no custom JS
• Authored entirely through OCC Admin content editor
• Bound to VCS’s global stylesheet — no shared CSS modifications
• Images sourced from OCC media asset library
• SEO-optimized: buying guide format targeting seasonal, material-based queries

Why It’s Interesting

Buying guides in the Tips & Advice series serve the longest consideration cycle in the VCS content strategy — shoppers researching rather than browsing. This page had to earn trust before it could convert, which meant leading with genuinely useful information (sleep science, material properties, seasonal guidance) before surfacing product. Structuring that credibility-first flow within a static OCC page — no dynamic content, no personalization, no CMS tooling — is a content architecture problem as much as a development one.

Oracle Commerce Cloud OCC Admin ATG HTML CSS Enterprise Ecommerce Content Architecture UX Writing SEO Buying Guide Format Sleepwear

Role— Frontend Developer

Best Curtains for Kitchen Windows

Vermont Country Store — Oracle Commerce Cloud
Role: Frontend Developer / OCC Implementation
Live URL: [vermontcountrystore.com/tips-advice-best-curtains-for-kitchen-windows](https://www.twine.net/signin

What This Was

A static educational page in VCS’s Tips & Advice content series — a sister format to Signature Products, purpose-built for practical guidance over editorial storytelling. This page tackles the specific considerations of kitchen windows: light control, washability, privacy trade-offs, and style cohesion in a high-traffic, high-humidity room. It funnels to VCS’s kitchen curtains category, including café tiers, valances, swags, and coordinating Country Curtains collections.

What I Built

Structured the page around the kitchen’s unique constraints as a window treatment environment — smaller windows, more light needed, fabric durability a priority, and partial coverage (tiers and valances) the dominant style choice. Organized content to move the shopper from “what works in a kitchen” through treatment type options (café tiers, valances, swags, sheers) to coordinating collections with cross-links.

The Tips & Advice format required a more instructional tone than Signature Products — closer to a buying guide than editorial commerce — while still driving conversion. Copy and structure decisions were made at the developer level, as is standard in the OCC static page workflow. Particular attention was given to café tier and valance categories, the most relevant treatments for typical kitchen window dimensions.

Code Sample

The room-constraint callout block used to frame each treatment recommendation:

<div class="room-tip-block">
  <h4>Why Tiers Work in Kitchens</h4>
  <p>Partial coverage keeps the sink and counter area bright
  while still softening the window.</p>
  <a href="/curtains-drapes/category/cafe-tier-curtains" class="cta-link">
    Shop Café Tiers</a>
</div>

Constraints

• Vanilla HTML/CSS only — no framework, no custom JS
• Authored entirely through OCC Admin content editor
• Bound to VCS’s global stylesheet — no shared CSS modifications
• Images sourced from OCC media asset library
• SEO-optimized: room-specific query targeting within curtains category authority

Why It’s Interesting

Tips & Advice targets shoppers earlier in research, before they’ve settled on a treatment type — a different funnel position than Signature Products. Structuring for that required a content strategy call made entirely at the developer level.

Oracle Commerce Cloud OCC Admin ATG HTML CSS Enterprise Ecommerce Content Architecture UX Writing SEO Buying Guide Format Kitchen Curtains

Role — Frontend Developer

Tunics vs. Shirts vs. Blouses: What’s the Difference?

Vermont Country Store — Oracle Commerce Cloud
Role: Frontend Developer / OCC Implementation
Live URL: [vermontcountrystore.com/signature-products-tunics-vs-shirts-vs-blouses-whats-the-difference](https://www.twine.net/signin

What This Was

A static editorial page in VCS’s Signature Products series built around a genuine customer confusion point — the vocabulary difference between tunics, shirts, and blouses, and what each means in practice when shopping. The page educates before it sells, resolving terminology friction that can stall a purchase decision, then funnels shoppers into VCS’s women’s tops catalog, including the exclusive Ella Simone and M. Mac collections.

What I Built

Organized the page as a plain-language comparison: what defines each garment type (fit, length, fabric weight, occasion), how they differ at a glance, and which VCS styles fall into each category. The structure moves from definition to differentiation to product — the natural path for a shopper who arrives not knowing what to search for.

Content decisions were made at the developer level. Copy was written to match VCS’s voice: clear, practical, and respectful of the customer’s intelligence — not fashion-editorial, not condescending. Special attention was given to tunics, a VCS strength relevant to plus-size shoppers, where relaxed silhouettes serve comfort and coverage needs.

Code Sample

The comparison-table pattern used to lay out the three garment types side by side:

<table class="comparison-table">
  <tr><th>Type</th><th>Length</th><th>Best For</th></tr>
  <tr><td>Tunic</td><td>Hip to mid-thigh</td><td>Layering, coverage</td></tr>
  <tr><td>Blouse</td><td>Waist length</td><td>Dressier occasions</td></tr>
</table>

Constraints

• Vanilla HTML/CSS only — no framework, no custom JS
• Authored entirely through OCC Admin content editor
• Bound to VCS’s global stylesheet — no shared CSS modifications
• Images sourced from OCC media asset library
• SEO-optimized: comparison-format H1 targeting definitional search queries

Why It’s Interesting

Comparison and definition pages are among the highest-converting editorial formats in ecommerce — they intercept shoppers at the moment of confusion, before they’ve committed to a category. Building this in OCC required translating that content strategy insight into a static page structure with no CMS tooling, no templates designed for comparison content, and no UX support — just clean HTML, good content judgment, and an understanding of where the shopper is in their decision.

Oracle Commerce Cloud OCC Admin ATG HTML CSS Enterprise Ecommerce Content Architecture UX Writing SEO Women's Apparel Comparison Content

Role — Frontend Developer

Best Dresses for Everyday Wear

Vermont Country Store — Oracle Commerce Cloud
Role: Frontend Developer / OCC Implementation
Live URL: [vermontcountrystore.com/signature-products-best-dresses-for-everyday-wear](https://www.twine.net/signin

What This Was

A static page in VCS’s Signature Products series highlighting the brand’s two exclusive private-label dress collections — M.MAC (cotton jersey knit, Rock Fish print) and Ella Simone (florals, pintuck details, tiered midi styles) — alongside muumuus and the core dresses & jumpers catalog. The goal: position everyday dresses as comfortable, durable wardrobe staples rather than fast-fashion purchases.

What I Built

Organized the page around fabric and lifestyle fit rather than style name — cotton jersey for everyday wear, seersucker for warm days, flowing muumuu silhouettes for at-home comfort — each paired with the relevant exclusive collection. M.MAC and Ella Simone got dedicated emphasis as VCS-exclusive lines with the strongest brand differentiation and margin.

Content hierarchy and copy were developer-level decisions, written to match VCS’s voice: quality over trend. A customer testimonial referencing decades of M.MAC loyalty reinforced credibility for an exclusive line shoppers can’t compare-price elsewhere.

Code Sample

A representative section block from the page — a product highlight card pattern reused across the layout, built with VCS’s existing grid classes and scoped inline overrides where Signature Products styling diverged from standard catalog pages:

<div class="signature-section">
  <h2 class="signature-heading">M.MAC: The Original Rock Fish Dress</h2>
  <div class="product-highlight-grid">
    <div class="product-highlight-card">
      <img src="/media/mmac-rockfish-dress.jpg" alt="M.MAC Rock Fish print dress" />
      <p class="highlight-copy">100% cotton jersey knit, hand-printed with
      water-based inks — exclusive to The Vermont Country Store.</p>
      <a href="/women/category/m-mac" class="cta-link">Shop M.MAC Dresses</a>
    </div>
  </div>
</div>

Constraints

• Vanilla HTML/CSS only — no framework, no custom JS
• Authored entirely through OCC Admin content editor
• Bound to VCS’s global stylesheet — scoped inline overrides only
• Images sourced from OCC media asset library
• SEO-optimized: everyday-wear search intent targeting casual dress shoppers

Why It’s Interesting

This page served a generic “everyday dresses” query while steering traffic to two proprietary brands with no real price comparison available elsewhere — a merchandising-led strategy executed entirely in HTML/CSS, no personalization engine or A/B tooling required.

Oracle Commerce Cloud OCC Admin ATG HTML CSS Enterprise Ecommerce Content Architecture Private Label Merchandising SEO

Role — Frontend Developer

Best Cardigans and Dresses to Pair: Spring & Fall

Vermont Country Store — Oracle Commerce Cloud
Role: Frontend Developer / OCC Implementation
Live URL: [vermontcountrystore.com/signature-products-best-cardigans-and-dresses-to-pair-spring-fall](https://www.twine.net/signin

What This Was

A newly published Signature Products page targeting the shoulder-season layering problem — dresses that work alone in summer need a partner once temperatures dip. The page pairs VCS’s dress collections (M.MAC, Ella Simone, classic cotton dresses) with its sweater catalog (button-front cardigans, cable-knit, cowl neck) to drive cross-category discovery between two departments that don’t naturally link in standard navigation.

What I Built

Structured the page around outfit-building rather than single-product browsing — leading with the pairing logic (lightweight dress + structured cardigan = transitional outfit) before breaking it into specific combinations by dress style and cardigan weight. This required cross-linking two separate OCC category trees (women’s dresses, women’s sweaters) in a single content flow, something the standard catalog navigation doesn’t support.

Content hierarchy and copy were developer-level decisions, written in VCS’s voice: practical, seasonal, focused on versatility and re-wearability rather than trend-chasing.

Code Sample

The pairing-card pattern used to present each dress + cardigan combination, built with VCS’s grid classes and scoped overrides for the two-column comparison layout:

<div class="pairing-card">
  <div class="pairing-item">
    <img src="/media/mmac-rockfish-dress.jpg" alt="M.MAC dress" />
    <p>M.MAC Cotton Knit Dress</p>
  </div>
  <span class="pairing-plus">+</span>
  <div class="pairing-item">
    <img src="/media/merino-cardigan.jpg" alt="Merino wool cardigan" />
    <p>Button-Front Merino Cardigan</p>
  </div>
  <a href="/women/category/womens-sweaters" class="cta-link">Shop Cardigans</a>
</div>

Constraints

• Vanilla HTML/CSS only — no framework, no custom JS
• Authored entirely through OCC Admin content editor
• Bound to VCS’s global stylesheet — scoped inline overrides only
• Images sourced from OCC media asset library
• SEO-optimized: shoulder-season styling query targeting transitional wardrobe search intent

Why It’s Interesting

Cross-category content like this is genuinely useful for site architecture, not just SEO — it creates a navigable path between departments that the primary nav structure keeps separate. Building that bridge as a static page meant solving a discoverability gap with content and linking strategy alone, no nav or taxonomy changes required.

Oracle Commerce Cloud OCC Admin ATG HTML CSS Enterprise Ecommerce Cross-Category Content SEO Seasonal Content

Role — Frontend Developer

Spring Cleaning Essentials

Vermont Country Store — Oracle Commerce Cloud
Role: Frontend Developer / OCC Implementation
Live URL: [vermontcountrystore.com/signature-products-spring-cleaning](https://www.twine.net/signin
Update Type: Refreshed copy and imagery on an existing Signature Products page

What This Was

An older Signature Products page covering VCS’s housekeeping and laundry essentials catalog, refreshed with updated copy and imagery to keep it performing for the spring search season. The page organizes cleaning supplies into tiered kits — from bare-essentials to whole-house deep clean — pointing to VCS’s housekeeping and laundry categories.

What I Refreshed

Restructured the content around a three-tier kit system: “Just the Essentials” (duster, microfiber cloths, all-purpose cleaner), “Whole-House Reset” (adding specialty brushes, floor care, fabric tools), and an upgrade tier for longer-lasting equipment. This kit framing replaced more generic room-by-room copy from the original version, giving shoppers a clearer entry point based on how much cleaning they’re actually planning to do.

Updated product imagery to reflect current catalog inventory, since several housekeeping SKUs had changed since the page’s original publish. Cross-links were re-verified against the housekeeping and laundry essentials categories to ensure no dead links from discontinued items.

Code Sample

The tiered-kit card pattern used to organize each cleaning level:

<div class="kit-tier-card">
  <h3>Whole-House Reset</h3>
  <ul>
    <li>Window screen brush</li>
    <li>Floor care kit</li>
    <li>Fabric-cleaning tools</li>
  </ul>
  <a href="/home/category/housekeeping" class="cta-link">Shop Housekeeping</a>
</div>

Constraints

• Vanilla HTML/CSS only — no framework, no custom JS
• Authored entirely through OCC Admin content editor
• Bound to VCS’s global stylesheet — no shared CSS modifications
• Images sourced from OCC media asset library
• SEO-optimized: refresh preserved existing ranking equity while updating content depth

Why It’s Interesting

Refreshing an existing page is a different discipline than building new — it requires auditing what’s stale (copy, images, dead links) without disrupting the page’s existing search ranking. The kit-tier restructure was a content strategy improvement made without touching the URL or core SEO signals that had already been earning traffic.

Oracle Commerce Cloud OCC Admin ATG HTML CSS Content Refresh SEO Maintenance Housekeeping

Role — Frontend Developer

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

Why Is Crinkle Cotton So Popular?

Vermont Country Store — Oracle Commerce Cloud
Role: Frontend Developer / OCC Implementation
Live URL: [vermontcountrystore.com/signature-products-why-is-crinkle-cotton-so-popular](https://www.twine.net/signin

What This Was

A static editorial page in VCS’s Signature Products series answering a high-intent product question — why crinkle cotton is a perennial warm-weather bestseller. The page bridges content marketing and commerce: it educates shoppers on the fabric’s properties (lightweight, breathable, wrinkle-disguising, machine washable) while funneling them to crinkle cotton dresses, shirts, and pants across the apparel catalog.

What I Built

Structured the page around the customer’s actual decision path — moving from “what is it” to “why does it work” to “what do I buy.” Key sections covered fabric properties, warm-weather and travel use cases, garment-type breakdowns (dresses, shirts, pants), and care instructions — each tied to product cross-links.

Content and hierarchy decisions were made at the developer level, as is standard for OCC static pages without a dedicated UX or content layer in the workflow. Copy was written to match VCS’s voice: practical, warm, direct — the kind of guidance a trusted friend would give, not a product description.

Customer reviews were pulled from the live catalog and woven into the editorial flow to reinforce credibility at the point of purchase.

Code Sample

The review-callout block used to surface social proof inline with editorial content:

<div class="review-callout">
  <p>"I live in this dress all summer — it never wrinkles
  in the suitcase." — Verified Buyer</p>
  <a href="/womens-clothing/category/crinkle-cotton" class="cta-link">
    Shop Crinkle Cotton</a>
</div>

Constraints

• Vanilla HTML/CSS only — no framework, no custom JS
• Authored entirely through OCC Admin content editor
• Bound to VCS’s global stylesheet — no shared CSS modifications
• Images sourced from OCC media asset library
• SEO-optimized: clean URL, indexable, question-format H1 targeting search intent

Why It’s Interesting

Question-format Signature Products pages like this one sit at the intersection of SEO content strategy and storefront development. The URL and H1 directly target a search query, the editorial structure satisfies informational intent, and the product links convert that intent to purchase — all built by one developer working within a tightly constrained enterprise platform.

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

Role — Frontend Developer

Best Men’s Shirts to Wear with Khakis

Vermont Country Store — Oracle Commerce Cloud
Role: Frontend Developer / OCC Implementation
Live URL: [vermontcountrystore.com/signature-products-best-mens-shirts-to-wear-with-khakis](https://www.twine.net/signin

What This Was

A static editorial page in VCS’s Signature Products series built to drive discovery across the men’s shirts catalog by anchoring to a high-intent styling query. The page pairs wardrobe guidance — what shirt types work with khakis and why — with curated links to VCS’s men’s shirts collection, including the exclusive Orton Brothers line, flannels, polos, and button-downs.

What I Built

Structured the page around shirt type as the organizing logic — moving the shopper from casual to dressed-up across VCS’s catalog range: pocket tees, polos, short-sleeve button-downs, flannels, and Henley styles. Each shirt type was matched to a khaki use case (weekend, work-casual, outdoor) with direct product cross-links.

As with all OCC static pages in the Signature Products series, content architecture, copy direction, and cross-link strategy were developer-level decisions. Copy was written to match VCS’s voice — practical, unpretentious, built for a customer who values quality and longevity over trend. The Orton Brothers exclusive line was highlighted as a key differentiator, reinforcing private label value within the editorial flow.

Code Sample

The shirt-type-to-occasion mapping block, repeated for each style category:

<div class="style-match-row">
  <span class="shirt-type">Short-Sleeve Button-Down</span>
  <span class="match-arrow">→</span>
  <span class="occasion">Weekend Errands</span>
  <a href="/men/category/orton-brothers" class="cta-link">Shop Orton Brothers</a>
</div>

Constraints

• Vanilla HTML/CSS only — no framework, no custom JS
• Authored entirely through OCC Admin content editor
• Bound to VCS’s global stylesheet — no shared CSS modifications
• Images sourced from OCC media asset library
• SEO-optimized: question-adjacent H1 targeting men’s styling search intent

Why It’s Interesting

This page is a good example of using editorial format to serve both SEO and private label merchandising goals simultaneously. The styling guide format captures mid-funnel search traffic (“what to wear with khakis”), while the content is structured to foreground VCS’s exclusive Orton Brothers line — turning an organic content page into a direct driver for proprietary product discovery, all within the constraints of a static OCC template.

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

Role — Frontend Developer