Skip to content

How it works

One homepage design, from first share to approval

This is the sample project in the demo: Veld & Vaan's storefront launch. You can run the same cycle yourself.

  1. 1. The studio shares version 1

    Alex uploads the first homepage design for Veld & Vaan, adds a note and submits it. Until then, Nina can't see the draft.

    1. V1
    veldvaan.store
    Version 1: delivery details only in the footer, call to action as a quiet text link.
  2. 2. The client requests a specific change

    Nina reviews version 1 and requests changes: “Please make the delivery information easier to find and give the main button more emphasis.” The request is saved on version 1, which is now marked Changes requested.

    1. V1
    2. Changes requested
    “Please make the delivery information easier to find and give the main button more emphasis.”
    Nina · Veld & Vaan
  3. 3. The studio adds a visibly revised version 2

    Version 2 adds a delivery bar at the top and a delivery block under the hero. The understated text link becomes a solid dark button. Alex writes what changed, then submits.

    1. V1
    2. Changes requested
    3. V2
    veldvaan.store
    Version 2: delivery bar and block, solid call-to-action button.
  4. 4. The client approves version 2

    Nina confirms the approval in a dialog that names the deliverable and version. Both views now show: Approved by Nina · Version 2. Version 1 keeps its feedback and can no longer be approved.

    1. V1
    2. Changes requested
    3. V2
    4. Approved
    Approved by Nina · Version 2
    Nina · Veld & Vaan

Open this deliverable in the workspace

It opens in its current saved state. Nothing is reset.