Navigation
WorkAboutContactGet in touch

© 2026 Alfonso Barreiro

Men's Sole Revival · UX Case Study

A Foot Health Resource Built for Men

Content-first design that treats foot health the way men's grooming brands treat skincare: with authority, not apology. Editorial credibility meets e-commerce UX patterns to serve a reader who's evaluating, not just browsing.

Role

UX/UI Designer · Content Strategist

Type

Solo · Self-initiated

Timeline

Jan – Apr 2026

Methods

Competitive Analysis · Content UX · Design System Architecture

Stack

Next.js · Tailwind v4 · MDX · Vercel

Men's Sole Revival homepage — dark editorial design with foot health content
01

Context

I kept Googling the same thing — “cracked heels men fix” — and landing on the same three articles written for women, repackaged with a stock photo of a guy. The clinical sources were accurate but impersonal. The product sites were selling, not teaching. Nothing spoke to men who actually wanted to understand what was happening to their feet and what to do about it without a referral.

63% of Americans report foot pain, but only 12% ever see a podiatrist. Men have a 3× higher fungal infection rate. The men's foot-care segment is growing at 10% CAGR. The audience exists. The resource doesn't.

Design synthesis

Men need a foot health resource that's male-specific, clinically grounded, and product-informed — the intersection no existing site occupies.

02

The Competitive Gap

Three categories of content exist for men's foot health. Each covers part of the problem. None covers all of it.

CLINICALWebMD, Mayo ClinicCleveland ClinicPRODUCT-FIRSTSneaker blogs, GQAmazon listiclesWELLNESSHealthline, Verywell Healthno male focusno productguidanceno clinicalrigorMen's SoleRevival

Men's Sole Revival sits at the intersection: male-specific, clinically grounded, and product-informed. Not a compromise between the three categories — the resource that should exist where they overlap.

03

The Pivot

The original plan was a premium men's foot care e-commerce site. Curated product kits — antifungal treatment, toe separators, insoles, foot cream. Headless Shopify, Next.js frontend, dark editorial brand.

The numbers kept breaking. Commodity products with thin margins, fulfillment costs, customer acquisition on a cold audience. Three weeks of modeling margins that wouldn't work was the signal: the friction wasn't execution. It was the starting point.

DimensionBeforeAfter
RevenueProduct salesAffiliate links + brand partnerships
Page designProduct listingsReview pages using e-commerce UX patterns
ContentCatalog copyPillar articles + product comparison reviews
GrowthPaid acquisitionSEO, social, direct brand outreach

Key insight

The pivot wasn't away from e-commerce — it was toward content as the product, using e-commerce UX patterns to frame editorial decisions.

04

Design Decisions

Two decisions defined the direction: the visual language and the review page layout. Each came from reasoning about the audience's emotional state and task intent, not aesthetic preference.

Brand Direction: Dark Editorial

Three visual directions were prototyped and evaluated against one question: does this aesthetic lower the stigma barrier before the first word is read?

ClinicalRejected

Medical authority is precisely the barrier these men are already dealing with. Clinical design confirms the user’s fear: ‘this requires professional help.’ That’s what drives them away.

SalesyRejected

Hesitation in this audience comes from shame, not indecision. Pressure amplifies shame. Fear-based design destroys trust before it starts.

Dark EditorialChosen

The visual language of premium grooming brands and men’s performance gear. Brands men already trust for personal care. The aesthetic says this topic is handled here with confidence, not apology.

Visual Directions Explored

Clinical — Rejected

Clinical — Rejected

Salesy — Rejected

Salesy — Rejected

Dark Editorial — Chosen

Dark Editorial — Chosen

Review Pages: E-Commerce UX, Not Blog Format

The user's task on a review page is evaluation, not reading. A blog format buries signal in narrative — the user has to read to evaluate. An e-commerce layout does the orienting work: hero image, specs grid, rating, pros/cons, buy links. Users already know how to scan this pattern from every product page they've used.

This isn't a store. There's no checkout, no inventory. The UX pattern is borrowed from e-commerce because it matches the user's task, not because it serves a transaction.

Key Design Decisions

Brand

Dark editorial as stigma reduction

Visual familiarity with premium grooming brands lowers the barrier before the first word is read

Layout

E-commerce UX for review pages

Match the layout to the task. Evaluation requires scanning, not reading prose

Content

Pillar articles build SEO authority

Long-form editorial is right when the user is learning. Depth earns organic traffic over time

Architecture

Every page maps to a user task

Orient, Learn, Evaluate, Browse, Explore, Trust, Act. The IA is the product strategy made navigable

05

Design System

Three typefaces, each with a job. Barlow Condensed for display headlines — authority and presence. Lora for editorial subheads and quotes — readable, approachable. DM Sans for body copy and UI — legibility at scale. The roles are explicit, not decorative.

The token architecture runs three tiers: CSS custom properties as the source of truth, TypeScript semantic aliases for brand-aware naming, and Tailwind utilities consumed in components. One file change propagates everywhere. The same naming convention holds across Brand, Wayfarer, and Men's Sole Revival — this wasn't retrofitted. It was a decision made before the first component was built.

TokenBrandWayfarerMSR
brand-500#1C3F5E#2D5A3D#1C3F5E
brand-900#091016#0A1A10#091016
accent-500#C4703A#B8860B#C4703A
neutral-50#F8F7F7#F7F8F5#F8F7F7
neutral-500#6B6560#5E6B5A#6B6560

Same naming convention, different values per project. The AB Core Library holds primitives for all three properties.

06

Site Architecture

Seven page types, each designed for a different user task. The information architecture is the product strategy made navigable — every route maps to a specific intent.

RouteTypeUser TaskPurpose
/HomepageOrientUnderstand what this site is and whether it’s for me.
/blog/[slug]ArticleLearnGo deeper on a foot health topic.
/reviews/[slug]Product ReviewEvaluateCompare and decide on a product.
/kitsCurated KitsBrowseSee grouped product recommendations.
/learnEducational HubExploreFind the right starting point.
/aboutBrand StoryTrustUnderstand who built this and why.
/assessmentSelf-Check ToolActGet a personalized starting point.

Page Types in Context

Orient + Browse

Orient + Browse

The homepage answers one question: is this site for me?

Learn

Learn

Long-form articles build authority. The layout is for reading, not scanning.

Evaluate + Decide

Evaluate + Decide

Product reviews use e-commerce UX patterns. The layout matches the task.

07

Evaluation Plan

This is a self-initiated project. There were no live metrics at launch. What I defined instead was a validation plan: specific measures tied to the strategic hypotheses, structured around the first 3, 6, and 12 months of content publishing.

What to MeasureMetricWhy It Matters
Organic search trafficMonthly visits at 3, 6, 12 monthsDo men find this content when searching?
Email list growthSignup rate from article pagesA reader who signs up plans to come back.
Time on product reviewsAverage time on pageIf they’re spending time, the e-commerce layout works.
Brand partnership inquiriesOutreach to Vivobarefoot, Altra, Correct ToesDoes the site read as a credible media property?
Reddit engagementShares in r/BarefootRunning, r/PlantarFasciitisOrganic community uptake is the early trust signal.

No live data yet. These thresholds were defined to test the core hypotheses: that the content reaches the audience, that the UX patterns match their tasks, and that the site earns credibility with brands.

08

Reflection

The first build spent three weeks fighting a stack that wasn't right for the problem. The friction was the signal and I waited too long to act on it. The pivot from e-commerce to content wasn't a retreat — it was the moment the project found its actual shape.

The absence of user validation is the biggest open question. The e-commerce layout for reviews is the call I'd make again, but it hasn't been tested with the actual audience. The competitive analysis and UX reasoning are sound, but reasoning isn't evidence. The evaluation plan is how I'll find out if the reasoning holds.

Content authority takes time. The honest uncertainty: whether the SEO ramp will produce the audience before the motivation to sustain the project runs out. That's not a design problem. It's the real risk of building something this slowly, alone.

What wasn't done

I didn't conduct user interviews before building. I didn't run usability tests on the review page layout. The e-commerce UX pattern is based on competitive analysis and reasoning about mental models, not observed behavior with real users. Self-initiated, no research budget. The decisions are reasoned, not tested. The evaluation plan is how I'll find out if the reasoning holds.

If I had more time

Run moderated usability tests with 5–6 participants matching the target persona — men 25–55 who have Googled a foot health question in the last 6 months. Test the review page layout against a blog-format control. Measure task completion time, information findability, and whether the e-commerce pattern reduces cognitive load for evaluation tasks.

From there: A/B test the homepage topic categories to see which entry points drive the deepest engagement. Validate the email signup placement. And pressure-test the brand direction with the audience directly — does the dark editorial tone actually lower the stigma barrier, or is that an assumption that deserves its own research cycle?

Next Case Study

Spotify — Recently Played Controls

View Case Study