Skinbase.org

Upload help

Uploading on Skinbase is a guided workflow, not just a raw file submission.

This page explains how uploads move from file submission to draft, review, and final publish. It is designed to help you upload confidently, prepare the right details in advance, avoid common context mistakes, and understand what to do when something feels stuck.

Core idea
Guided workflow, not raw submission

Uploading is more than sending a file. It includes draft setup, metadata, previews, context, and publishing checks.

Most common mistake
Wrong context at publish time

Personal and Group uploads can look similar, but the published identity and review behavior can be very different.

Safest habit
Review before final publish

Drafts exist to help you finish details before the public version goes live.

Workflow

How uploading works

Uploading is designed to feel understandable and safe. The workflow gives you space to review and finish the public version before it goes live.

  1. 1

    Start the upload

    Begin with the file you want to publish and confirm whether the upload belongs to your personal identity or to a Group context.

  2. 2

    The file is received

    Skinbase accepts the file and starts turning the upload into a manageable workspace item instead of sending it public immediately.

  3. 3

    A draft is created

    Uploads usually start as drafts so you can review details, context, credits, and presentation before publishing.

  4. 4

    Processing and previews happen

    Previews or processing steps may run so the upload is easier to review and present clearly.

  5. 5

    Metadata is completed

    Titles, descriptions, tags, categories, and other public-facing details are finalized while the upload is still safe to edit.

  6. 6

    Context and contributors are checked

    Before publishing, verify whether the work belongs to you or a Group and make sure contributor credit reflects the real people behind the upload.

  7. 7

    Publish or submit for review

    Once the upload is ready, it is either published or routed into review depending on the workflow and permissions involved.

Preparation

What to prepare before upload

The better prepared you are before upload starts, the less likely you are to end up with an unfinished draft, weak presentation, or incorrect publishing context.

Final file you actually want people to see, not a rough placeholder.
Clear title and description so the upload is understandable without extra cleanup later.
Tags and categories if they apply to the content type you are publishing.
Contributor information for collaborative work, especially if a Group is involved.
The correct publish context: personal or Group.
A good preview mindset so the public version feels intentional and discoverable.

Context

Personal upload vs Group upload

The most important upload decision is not just the file. It is whether the work should publish under your personal identity or under a Group.

Comparison between Personal upload and Group upload
TopicPersonal uploadGroup upload
Published identityThe work publishes under your personal creator identity.The work publishes under the Group identity.
Human creditYour own authorship and upload role are usually straightforward.Contributor credit still matters. Group identity does not replace human authorship.
Why behavior can differYou usually control the full flow yourself.Roles, review queues, and approvals may affect whether you can publish directly.
Draft handlingDrafts stay in your personal workspace until you finish them.Drafts may be part of a team review flow before they are publicly published.

Drafts

Draft flow

Uploads usually begin as drafts so you can finish the details deliberately instead of publishing a half-finished item by accident.

Uploads usually begin as drafts so you can finish details without rushing a public release.
Drafts are where metadata, context, previews, and contributor setup are reviewed.
Drafts may still be processing while you are working on the rest of the upload.
Incomplete drafts can be left temporarily, but they are best finished quickly so the workspace stays clean.
In Group workflows, drafts may be submitted for review instead of publishing directly.

Publish

Publish flow

Publish is the final decision point. By the time you reach it, the file, context, metadata, and contributor details should already feel solid.

Publishing should happen after file review, metadata review, and context confirmation.
You should verify titles, descriptions, previews, and contributor information before the final step.
Some Groups may route the upload into review instead of publishing immediately.
Publishing under the wrong context is one of the most common avoidable mistakes.

Presentation

File, preview, and metadata basics

Strong uploads are not only about file quality. They also depend on how clearly the work is presented and how understandable it feels to other people.

Previews matter because people often decide whether to open or trust a piece based on its first impression.
Metadata matters because clear titles and descriptions help the work feel intentional and improve discoverability.
Final review matters because small mistakes feel much bigger after the upload is public.
Taking a minute to review the presentation is usually faster than correcting avoidable problems later.

Credit

Contributor credit during upload

Upload identity, published identity, and authorship are related, but they are not always the same thing. That matters most in collaborative and Group uploads.

Group uploads still preserve human credit.
Primary author should reflect the main author of the work, not just the person who clicked upload.
Uploaded by and published identity are not always the same thing.
Contributor lists should be intentional, accurate, and checked before publish.

Simple example

Published by
Nightshift Collective
Uploaded by
Gregor
Primary author
Gregor
Contributors
Paula, Denis

Best practices

Best practices

The best upload habits are simple: prepare before you start, review before you publish, and keep the workspace clean enough that you can trust what you are looking at.

Prepare metadata before you start uploading whenever possible.
Use strong files and previews so the public result feels finished.
Check the publishing context before the final publish step.
Do not rush final publish just because the file is already in the system.
Give proper contributor credit for collaborative work.
Keep drafts organized and return to incomplete uploads quickly.

Avoid this

Common mistakes

Most upload problems are not technical failures. They come from skipping review steps, using the wrong context, or leaving too many things unfinished at once.

Uploading under the wrong context and only noticing after publish.
Forgetting contributor credit during a collaborative upload.
Leaving metadata empty because the file itself looked finished.
Abandoning drafts until the workspace becomes cluttered.
Trying to publish before everything has been reviewed clearly.
Misunderstanding review queue behavior in Group workflows.

FAQ

Upload FAQ

These answers cover the most common questions people ask when an upload becomes a draft, stalls before publish, or behaves differently inside a Group.

Uploads move through a guided workflow. The file is received, a draft is created, previews or processing may happen, metadata is completed, context and contributor credit are reviewed, and then the work is published or submitted for review.

Troubleshooting

Troubleshooting

Use these shortcuts when the upload workflow feels stalled, confusing, or inconsistent.