For artists

Uploading takes one action, some metadata is filled in for you, and your work shows up on the feed as soon as the upload finishes.

The upload flow

You can start an upload three ways:

1. Drag and drop anywhere on any page. A full-window drop zone appears, the upload modal opens, and files start uploading right away. The progress bar is the upload — there’s no separate “submit” step.
2. Click the Upload button in the top-right of the nav. Same modal, just a file picker as the first step.
3. Inside a collection. The Upload button on a collection page pre-fills the collection context, so the upload lands inside that collection automatically.

The modal uploads up to 3 files at once, each with its own row showing progress, the inferred title, and an optional tag chip-strip. Closing the modal does not cancel in-flight uploads — they finish in the background. Files that hadn’t started yet are dropped.

Posts wrap your assets

Every upload session ends in one of three outcomes:

• One post containing all the assets (the default). A multi-asset post — gallery, set, or sequence — shows up as a single card on the feed with an asset-count badge.
• One post per file. Each file gets its own post; useful for a batch of unrelated pieces.
• No post — just upload as assets. The assets land in storage and in your library; you can compose a post later, or never.

The post composer at the bottom of the upload modal handles the title, description, visibility (private / followers / public), tags, and the optional cover thumbnail.

Cover thumbnails

By default the first asset is the cover. You can also:

• Pick a different member asset as the cover.
• Upload a separate image that’s only used as the cover (not a member of the post).

Tags, fields, and metadata

• Tags are free-form text chips. Type a tag, press enter. They power search and the tag filter on the browse feed.
• Per-asset metadata fields appear inside each row’s “Metadata” disclosure during upload. Fields are admin-defined (resource types, field definitions) and inherited at upload time.
• Inferred metadata — filename, file size, MIME type, and dimensions, plus EXIF, IPTC, XMP, and PDF metadata (title, author, page count, and so on) parsed on ingest. Raw-camera embedded thumbnails are on the roadmap.

Versioning

Versioning is implicit through content addressing. Every asset is keyed by its file_hash (SHA-256). Re-uploading the same bytes deduplicates instead of creating a duplicate row. To create a new version of a post, edit the post and swap a member asset for a new upload — the old asset stays in storage, and the post points at the new one.

A dedicated “version history” surface (per-asset and per-post) is on the roadmap.

Finding your work

The browse feed at / is your home. It shows posts newest-first by default. The floating footer at the bottom-left switches between:

• Grid — square cards, the default.
• Masonry — variable-height cards in flowing columns.
• Thumbnail — denser preview wall.
• List — sortable table with toggleable columns (title, author, tags, asset count, likes, comments, posted-at, etc.).

The middle of the footer scopes the feed: Team (your team’s posts), Trending, Latest (default), Following. The right of the footer toggles ascending vs descending sort.

The search bar in the navbar runs a full-text query against post title, description, tags, and member-asset metadata. Advanced search with field-level filters and facets lives at /search/advanced, including reverse-image search.

When a reviewer leaves feedback

Comments and likes on your posts surface on the post detail modal (click any post card to open it). In-app notifications (the bell, including @-mentions) and email digests ship today; webhook delivery is on the roadmap for the notifications phase.