Your Disabled Friend — Artist Storefront

Problem

The creator needed a simple way to sell his photographs without having to understand SKUs, variant IDs, product templates, upload URLs, webhooks, or the internal language of a print-on-demand platform.

Description

What I built or investigated

I built a branded public shop and a deliberately simple private studio so the artist could upload a photograph, choose the products or print formats he wanted to offer, set pricing, add a title or description, and publish without touching Fourthwall’s internal product data.

Iterations

The work did not happen in one jump.

1. 01

   Reduced the creator workflow to upload photo, choose formats, set prices, add basic listing information, and publish.

2. 02

   Separated the artist-facing controls from platform internals such as SKUs, region IDs, media IDs, variant IDs, API tokens, upload URLs, and webhook payloads.

3. 03

   Added storefront cart behavior, Fourthwall integration hooks, normalized order handling, and webhook deduplication.

4. 04

   Added session hardening, CSRF protection, upload isolation, file locking, and safer error handling.

5. 05

   Rebuilt the visual system around the artist’s blue-green grounds, dark marks, cobalt accents, off-white surfaces, and circular logo language rather than a generic ecommerce theme.

6. 06

   Tested responsive layouts, long titles, cart behavior, invalid routes, signed events, and retry behavior; the final live-shop acceptance test still requires production credentials.

Result

Where the project landed

A complete branded storefront and creator publishing workflow for yourdisabledfriend.shop. The application was audited and repaired; the remaining launch boundary is a real end-to-end Fourthwall transaction using the artist’s production shop credentials.

Lessons

What carried forward

• The best accessibility improvement is often removing unnecessary system knowledge from the workflow.
• Good software can hide platform complexity while preserving the choices the creator actually needs to make.
• A small private studio still needs serious session, upload, webhook, and file-integrity controls.
• A project should state its external launch dependency honestly rather than treating an untested integration as complete.

Images & evidence

Work in context