Skip to content

Looks & executions

Looks are the styling layer of Shona — the space where garments are assembled into outfits and brought to life through real-world wear. Only stylist profiles can create looks. Every look has two sides: the look itself (the recipe) and its executions (the instances).

looks vs executions

Every look on Shona has two layers. Understanding the distinction is the key to how the system works.

Look

The look as a concept — the stylist's creative recipe. It holds the styling notes, display image, gallery, and the garment manifest. A look is the root record.

execution

A real-world instance of the look — a specific occasion when the look was worn or shot. An execution belongs to one look, can feature a model, and carries its own images, context type, and engagement.

A single look can have many executions. The same outfit recipe might be worn as an OOTD on a Tuesday, then appear in an editorial shoot, and later walk a runway — each of those is a separate execution record attached to the same look.

In the feed, look cards and execution cards are distinct content types. look cards link to the look's concept page. Execution cards link to the specific instance, with the model (or stylist, if no model is credited) as the primary profile shown.

creating a look

Look creation is restricted to stylist profiles. If your active profile is not a stylist, you will be prompted to switch to a stylist profile or create one before you can access the look editor.

Only the stylist role can create looks. Designers, models, and fashion houses can be linked to executions but cannot initiate a look. Make sure your active profile is set to your stylist identity before navigating to the look editor.
Once published, a look can be edited at any time from its detail page — an "Edit" button appears in the top bar, visible only to the stylist who owns it. This opens the same editor used for creation, with the garment manifest and executions sections already unlocked.

The core fields

styling_notes

The creative brief for the look — your intent, the mood, the occasion it's built for. At least 10 characters. This text is the primary descriptor shown on look cards.

display_image

The hero image for the look — required before publishing. This is the image shown on look cards in the feed.

gallery_images

Optional additional images for the look. These appear in the media carousel on the look detail page alongside the display image.

  1. 1

    navigate to looks → create look

    The look editor is accessible from your stylist profile or via the main navigation. The profile switcher at the top of the editor confirms which profile the look will be attributed to.

  2. 2

    write your styling notes

    Describe the look — the aesthetic, the occasion, the creative direction. This is the public-facing text on the look card.

  3. 3

    upload a display image

    Upload the hero image that represents this look. This is required before you can publish. Additional gallery images are optional.

  4. 4

    publish the look

    Clicking publish creates the look record and makes it visible on your profile. The garment manifest and executions sections unlock immediately after.

screenshot — look editor core section with styling notes and image upload

the garment manifest

The garment manifest is the itemised list of every piece in the look. Each item is assigned to a layer — the garment's position in the outfit — and can be sourced in four different ways depending on whether the piece exists on Shona as a design or comes from the outside world.

garment layers

headwear

Hats, caps, headbands, and other head pieces.

top

Shirts, blouses, t-shirts, and upper body garments.

outerwear

Jackets, coats, blazers, and outer layers.

bottom

Trousers, skirts, shorts, and lower body garments.

footwear

Shoes, boots, sandals, and other footwear.

accessory

Bags, jewellery, belts, scarves, and all other accessories.

item source types

platform design

A design published on Shona. Linking to a platform design creates a clickable connection — audiences can navigate from the look directly to the design's full record.

external retail

A piece purchased from a retail brand or store not on Shona. Add the brand name and a brief description.

vintage / thrift

A found, vintage, or secondhand piece. No brand link required — just a description.

custom

A bespoke or commissioned piece. Add the maker's name and a description.

screenshot — garment manifest showing platform design links and external items by layer

How platform designs appear on looks cards

When a Look card has platform designs in its manifest, a 'pieces' button appears on the card showing the piece count. Tapping it opens a bottom sheet listing each linked platform design with its image, title, and layer — all clickable through to the full design record. External and vintage items count toward the total but are noted as not shown in the sheet.

Linking platform designs to a look creates a two-way discovery path: audiences browsing the design feed can see which looks it has appeared in, and audiences browsing looks can navigate to the source designs.

adding executions

Executions are added from the look editor's executions section, which unlocks after the look is published. Each execution is a specific real-world instance of the look — a moment it was worn, shot, or performed. This section covers the stylist's workflow, where a model can optionally be credited by search. Models can also submit executions of their own independently — see the next section.

Execution fields

images

Photos from this specific instance of the look. These are the images shown in the execution card carousel and on the execution detail page.

context_type

The category of occasion — OOTD, editorial, runway, or street style. Controls how the execution is labelled and filtered in the feed.

occasion_name

An optional name for the specific occasion — the event name, shoot title, or location. Appears as the execution card's heading.

model_profile_id

An optional link to a model profile who wore the look. When set, the model becomes the primary profile shown on the execution card. If absent, the stylist is shown.

event_id

An optional link to an event on Shona. When set, the event appears in the execution's context — connecting the look to the event's provenance trail.

  1. 1

    open the executions section in the look editor

    Scroll past the garment manifest to the executions enrichment section. It unlocks once the look is published.

  2. 2

    upload images for this instance

    Add photos specific to this execution — not the look's display image. These are the shots from the actual occasion.

  3. 3

    set the context type and occasion name

    Choose the type of occasion and optionally name it. The context type determines how the execution is categorised in the feed.

  4. 4

    optionally link a model and event

    Search for a model profile to credit as the wearer. Search for an event to link this execution to a specific occasion on the platform.

  5. 5

    save the execution

    Each execution saves independently. You can add as many executions as the look has real-world instances — there is no limit.

screenshot — execution form inside the look editor

A look's execution count is visible on look cards in the feed. Multiple executions signal that a look has had real-world traction — they function as social proof for the look.

independent model executions

Executions aren't only added by the stylist. A model has physical proof of wearing a look — a photo, a shoot, an appearance — regardless of whether the stylist was present to document it. Shona lets any model profile submit their own execution of a published look, independent of the stylist.

Only model profiles can submit an independent execution. Stylists — even the stylist who created the look — cannot use this flow. A stylist adds executions from their own look editor, described above.

Starting an independent execution

From any look card in the feed, opening the action menu shows an "execute this look" option (in place of the delete option shown to the look's owner). This opens a dedicated execution page at /looks/[id]/new-execution, separate from the stylist's look editor. Editing an execution afterward happens on a different route, covered below.

  1. 1

    switch to a model profile

    Your active profile must be a model profile. If it isn't, you'll be shown a gate prompting you to switch profiles before continuing.

  2. 2

    review the look you're executing

    The execution page shows a reference card for the look you're about to execute, crediting the original stylist.

  3. 3

    choose the context type

    Select OOTD, editorial, runway, or street style — the same context types used everywhere else in the executions system.

  4. 4

    add an occasion name or link a runway event

    Optional for most context types, required when the context type is runway.

  5. 5

    upload your photos and submit

    Add the images proving you wore the look, then submit. You are automatically credited as the model — there is no separate step to tag yourself.

screenshot — model-initiated execution page with look reference card

Ownership and editing

An execution you submit independently belongs to you. Only you can edit or delete it — not the stylist whose look it executes. The reverse is also true: executions the stylist adds from their own look editor can only be edited or deleted by that stylist.

From the execution's detail page, an edit option is shown only to the model who submitted it, opening /executions/[id]/edit. This reuses the same form you used to submit the execution, pre-filled with your existing context type, occasion, event link, and photos — you can swap photos in or out and save changes without resubmitting the whole thing. If someone other than the submitting model — including the look's stylist — reaches this URL, they're shown the same profile-switch gate used on the submission page rather than the editor.

The stylist is notified when a model independently executes their look, the same way a model is notified when a stylist tags them in an execution. Beyond that initial notification, ongoing likes and comments on an independently-submitted execution are only sent to the model who submitted it — the stylist isn't notified of every like or comment on an execution they didn't create.

execution context types

Every execution has a context type that describes the setting in which the look appeared. This controls the label shown on execution cards and how executions are filtered and categorised in the feed.

🌅

OOTD

Outfit of the day — a casual or daily wear instance. The most common context type for personal style documentation.

📸

editorial

A styled shoot for publication — magazine features, lookbooks, campaign imagery. Typically involves a creative team and a photographer.

✨

runway

A catwalk or fashion show appearance. When combined with an event link, places the execution in the event's provenance trail.

🏙️

street style

A candid or unplanned documentation of the look in public space — street photography, city shots.

Linking a runway execution to an event is especially powerful — it connects the look to the event's featured content, making it discoverable to anyone exploring that event's page.

feeds & discovery

Looks surface across the platform through two separate feed types — one for looks and one for executions. They are distinct content streams that can be browsed independently.

The look feed

look cards show the stylist's display image, styling notes, piece count, execution count, and a follow button for the stylist. Tapping the piece count opens the garment manifest sheet. Tapping anywhere else navigates to the full look detail page at /looks/[id], which shows the full manifest, all executions as thumbnails, and any recent events the look has appeared in.

The execution feed

Execution cards show the execution images in a swipeable carousel. The primary profile shown is the credited model — or the stylist if no model is linked. The card shows the context type, occasion name, and attribution line. Tapping navigates to the execution detail page at /executions/[id].

screenshot — look card and execution card side by side in feed

Where looks appear

stylist profile — looks tab

All looks created by a stylist profile appear here. This is the primary home for a stylist's look portfolio.

model profile — executions tab

All executions where a model is credited appear on their profile. This lets models build a portfolio of credited wear instances.

event pages

When a runway execution is linked to an event, the look surfaces in that event's content alongside featured designs.

design detail pages

When a platform design is in a look's manifest, the look can surface on the design's detail page — connecting the piece to how it has been styled.

Engagement

Engagement

The look itself carries its own engagement — likes, saves, and comments — visible on the look detail page via the engagement bar beneath the stylist's identity row. Executions carry a second, fully independent layer of engagement on top of this. A look's engagement reflects interest in the concept; an execution's engagement reflects the reception of that specific real-world instance. Neither rolls up into the other — liking a look and liking one of its executions are two separate actions.

the look provenance page

The look detail page only shows a preview — a handful of recent executions and recent events. For the full history, every look has a dedicated provenance page at /looks/[id]/provenance with two tabs, reached via the "see all" links on the look page.

The two tabs

executions

Every execution of this look, fully paginated — not just the recent strip shown on the look page itself.

events

Every event this look has appeared at, derived from runway executions that were linked to an event.

screenshot — look provenance page with executions and events tabs

Like the design provenance page, this is a read-only view — editing executions or event links happens back in the look editor.

deletion

Looks and executions can each be deleted independently, but deleting a look removes everything under it.

Deleting a look

Deleting a look look is a permanent action. It removes the look record, all its images, the garment manifest, and every execution attached to it — including all execution images and engagement data. The look is removed from all feeds and from the stylist's profile portfolio.

look deletion is accessible from the danger zone at the bottom of the look editor, or from the action menu on the look card (visible only to the owner).

Deleting a single execution

Individual executions can be deleted without affecting the parent look or other executions. Deleting an execution removes its images, any event or model links, and all engagement records for that instance. The look and its other executions remain intact.

Deleting a look is irreversible and cascades to all its executions. If you only want to remove a specific instance of the look, delete the individual execution instead.