import React from 'react' import { usePage } from '@inertiajs/react' import SeoHead from '../../components/seo/SeoHead' import DocsCallout from '../../components/docs/DocsCallout' import DocsComparisonTable from '../../components/docs/DocsComparisonTable' import DocsFaqAccordion from '../../components/docs/DocsFaqAccordion' import DocsSection from '../../components/docs/DocsSection' import DocsSidebarNav from '../../components/docs/DocsSidebarNav' import DocsStepList from '../../components/docs/DocsStepList' import { BENEFITS, BEST_PRACTICES, COMMON_MISTAKES, CREATE_STEPS, FAQ_ITEMS, FEATURE_CARDS, GOOD_FIT, NOT_YET, ROLE_TABLE, SECTION_ITEMS, STUDIO_AREAS, TROUBLESHOOTING_ITEMS, WORKFLOWS, } from './groupHelpContent' function HeroMetric({ label, value, note }) { return (
{label}
{value}

{note}

) } function TwoColumnChecklist({ title, eyebrow, items, tone = 'sky' }) { const toneClass = tone === 'emerald' ? 'border-emerald-300/15 bg-emerald-400/10 text-emerald-100' : 'border-sky-300/15 bg-sky-400/10 text-sky-100' return (

{eyebrow}

{title}

{items.map((item) => (

{item}

))}
) } function InfoCard({ title, body, icon }) { return (

{title}

{body}

) } function BulletGrid({ items }) { return (
{items.map((item) => (
{item}
))}
) } function WorkflowCard({ workflow }) { return (

{workflow.title}

{workflow.summary}

    {workflow.bullets.map((bullet) => (
  • {bullet}
    • ))}
) } function TroubleCard({ item }) { return (

{item.title}

{item.body}

) } export default function GroupHelpPage() { const { props } = usePage() const links = props.links || {} const heroJsonLd = [ { '@context': 'https://schema.org', '@type': 'Article', headline: 'Groups Help & Guide', description: props.description, url: props.seo?.canonical, author: { '@type': 'Organization', name: 'Skinbase', }, about: ['Groups', 'Collaborative publishing', 'Contributor credit', 'Group Studio', 'Releases'], }, { '@context': 'https://schema.org', '@type': 'FAQPage', mainEntity: FAQ_ITEMS.map((item) => ({ '@type': 'Question', name: item.question, acceptedAnswer: { '@type': 'Answer', text: item.answer, }, })), }, ] return (

Groups documentation

Build, manage, and publish through Groups without losing personal credit.

Groups on Skinbase Nova are shared creative identities for studios, collectives, release teams, and long-term collaborations. This guide explains when to use them, how to structure roles, how publishing works, and how to keep the public page clear, trustworthy, and easy to maintain.

{links.quickstart ? ( ) : null} {links.faq ? ( ) : null}
A Group is a shared publishing identity, not a way to erase authorship. If real people made the work, their authorship and contribution history should still be represented clearly.

Groups are a good fit for

{['Design studios', 'Pixel art crews', 'Wallpaper teams', 'Photography collectives', 'Event-based collaborations', 'Release teams'].map((label) => ( {label} ))}
If the team needs shared publishing, shared coordination, or a shared public identity more than it needs absolute simplicity, a Group is probably worth it.
Most new Groups should begin with one Owner, a very small Admin circle, Editors for day-to-day managers, and Contributors for creative participation. Complexity is easier to add later than remove.
Choose a name that will still make sense when the Group grows. Add a short description that says what the Group makes, not just what it likes. Decide early who should be Owner and who truly needs Admin. Teams create a lot of avoidable friction when this stays vague.
{['Cover and avatar', 'Description and About', 'Members and leadership', 'Artworks and collections', 'Posts and announcements', 'Projects, challenges, events, releases'].map((item) => (
{item}
))}
Use a consistent visual identity, keep the About copy current, feature the best work, and pin only the update that gives new visitors the best context.
The easiest way to create confusing attribution is to publish from the wrong context. If the work belongs to the Group, confirm that Group Studio is active before you submit or publish.

How to read the publishing record

Published by
Warlock

The shared identity the work appears under publicly.

Uploaded by
Gregor

The person who performed the upload or publishing action.

Primary author
Gregor

The person who should be understood as the main author of the work.

Contributors
Denis, Paula

Additional people who made meaningful creative contributions.

Group publishing creates a shared public identity for the work, but personal authorship, accountability, and contribution history should still be easy to understand. If the work is mainly one person\'s piece, make sure the primary author and contributors reflect that reality clearly.
Attribution problems are rarely just metadata problems. They affect trust, morale, and how future collaborators feel about the Group.
Keep Owner count very limited, give Admin only to trusted operators, use Editor for content managers, and keep Contributor focused on creation. If your Group supports join requests or recruiting, use them with a real onboarding process. Recruiting without follow-through makes the Group feel abandoned.
Small, trusted teams often move faster with direct publishing. Use review only when it protects quality or reduces confusion. Larger teams, new contributors, and release-heavy groups usually benefit from a review queue because it catches context, permission, and attribution mistakes before they go public.
{FEATURE_CARDS.map((card, index) => ( ))}
Many teams start with artworks and posts, then add projects when collaboration gets busier, and use releases when the Group is ready for stronger public storytelling around major drops.
Mix unclear roles with vague attribution and inconsistent publishing context. Users will stop trusting what they are looking at.
{COMMON_MISTAKES.map((item) => (
{item}
))}
{WORKFLOWS.map((workflow) => )}
{TROUBLESHOOTING_ITEMS.map((item) => )}
) }