klevze/SkinbaseNova
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

Commit workspace changes

Browse Source
This commit is contained in:
Gregor Klevže
2026-04-05 19:42:33 +02:00
parent 148a3bbe43
commit 08ad757bcb
312 changed files with 35149 additions and 399 deletions
Download Patch File Download Diff File Expand all files Collapse all files

300
resources/js/Pages/Group/groupHelpContent.js Normal file
View File

@@ -0,0 +1,300 @@
export const SECTION_ITEMS = [
{ id: 'introduction', label: 'Introduction' },
{ id: 'what-are-groups', label: 'What are Groups?' },
{ id: 'why-use-a-group', label: 'Why use a Group?' },
{ id: 'when-to-create-a-group', label: 'When should you create one?' },
{ id: 'how-groups-work', label: 'How Groups work' },
{ id: 'roles-and-permissions', label: 'Roles and permissions' },
{ id: 'creating-a-group', label: 'Creating a Group' },
{ id: 'public-group-page', label: 'Public Group page' },
{ id: 'group-studio', label: 'Group Studio' },
{ id: 'publishing-as-a-group', label: 'Publishing as a Group' },
{ id: 'contributor-credit', label: 'Contributor credit' },
{ id: 'member-management', label: 'Invites and team management' },
{ id: 'review-workflow', label: 'Review workflow' },
{ id: 'group-features', label: 'Projects, posts, events, releases' },
{ id: 'tips-and-best-practices', label: 'Tips and best practices' },
{ id: 'common-mistakes', label: 'Common mistakes' },
{ id: 'suggested-workflows', label: 'Suggested workflows' },
{ id: 'faq', label: 'FAQ' },
{ id: 'troubleshooting', label: 'Troubleshooting' },
{ id: 'need-help', label: 'Need help?' },
]
export const BENEFITS = [
'Publish under a shared name without hiding the people behind the work.',
'Separate team identity from personal portfolios when a project needs its own public home.',
'Manage roles, approvals, and release workflows in one place.',
'Run projects, posts, challenges, events, assets, and releases under the same umbrella.',
'Recruit collaborators through a Group page instead of repeating the same pitch in DMs.',
'Keep contributor credit visible even when the final publish surface is the Group.',
]
export const GOOD_FIT = [
'You collaborate with two or more people regularly.',
'You want a shared public brand for a studio, crew, or collective.',
'You publish themed drops, packs, showcases, or release-driven work.',
'You need shared collections, posts, assets, or release notes.',
'You want role-based access instead of everyone sharing one account.',
]
export const NOT_YET = [
'You only publish solo work and do not need a separate identity.',
'You are still testing ideas and not ready to manage members.',
'You want a Group only to rename personal work without collaboration value.',
'You do not want shared workflow, shared publishing context, or shared moderation responsibility.',
]
export const ROLE_TABLE = {
columns: [
{ key: 'role', label: 'Role' },
{ key: 'settings', label: 'Manage settings' },
{ key: 'members', label: 'Invite and change roles' },
{ key: 'publishing', label: 'Publish content' },
{ key: 'review', label: 'Review submissions' },
{ key: 'workflow', label: 'Manage posts, projects, events, releases' },
{ key: 'assets', label: 'Manage assets and shared resources' },
],
rows: [
{
id: 'owner',
role: 'Owner',
settings: 'Full control over branding, settings, membership policy, and archive actions.',
members: 'Can invite, remove, promote, transfer ownership, and approve the overall structure.',
publishing: 'Can publish directly and define the team workflow.',
review: 'Can always review, approve, request changes, or reject.',
workflow: 'Full access to posts, projects, challenges, events, releases, and reputation.',
assets: 'Full access.',
},
{
id: 'admin',
role: 'Admin',
settings: 'Can usually manage day-to-day settings and operations.',
members: 'Can invite and manage most members, but should not be handed out casually.',
publishing: 'Usually yes.',
review: 'Usually yes.',
workflow: 'Usually full operational access across content areas.',
assets: 'Usually full access.',
},
{
id: 'editor',
role: 'Editor',
settings: 'Usually limited or no access to sensitive settings.',
members: 'Usually cannot change member roles unless explicitly allowed.',
publishing: 'Often yes, depending on your workflow.',
review: 'Often yes when the team uses review queues.',
workflow: 'Good fit for content managers, release coordinators, and project leads.',
assets: 'Often yes.',
},
{
id: 'contributor',
role: 'Contributor',
settings: 'No sensitive settings access.',
members: 'Cannot manage team structure.',
publishing: 'Usually submits drafts instead of publishing directly.',
review: 'Usually no.',
workflow: 'Best for creative collaborators who need to contribute without running the Group.',
assets: 'Limited to what the Group makes available.',
},
],
}
export const CREATE_STEPS = [
{ title: 'Open Groups in Studio', description: 'Go to Group Studio from your main Studio area, then choose Create Group.' },
{ title: 'Choose a clear name and slug', description: 'Pick a name people can remember and a slug that still makes sense a year from now.' },
{ title: 'Add branding', description: 'Upload a recognizable avatar or logo and a cover image that gives the Group a clear visual identity.' },
{ title: 'Write a short headline and description', description: 'Tell visitors what the Group makes, who it is for, and what kind of collaboration to expect.' },
{ title: 'Set visibility', description: 'Choose whether the Group should be public, unlisted, or private based on how ready you are.' },
{ title: 'Create the Group', description: 'Finish setup, then review the public page so the branding and copy feel intentional.' },
{ title: 'Invite your first members', description: 'Bring in owners, admins, editors, or contributors based on the work each person will actually do.' },
{ title: 'Decide on your workflow', description: 'Choose whether the team should use direct publishing, review-first publishing, projects, releases, or lightweight milestones.' },
{ title: 'Publish with care', description: 'Before the first public post or artwork, confirm that contributor credit and publishing context are correct.' },
]
export const STUDIO_AREAS = [
'Dashboard for a quick read on releases, review items, events, and activity.',
'Artworks for group-owned publishing and shared presentation.',
'Review Queue for approval workflows, changes requested, and moderation hygiene.',
'Posts for announcements, release notes, recruitment, and milestones.',
'Projects for structured collaboration and shared progress.',
'Challenges and Events for community activity and time-based launches.',
'Assets for internal shared files and reusable resources.',
'Collections and Releases for public packaging, curation, and major launch moments.',
'Members, Recruitment, Invitations, and Reputation for team health and trust signals.',
]
export const FEATURE_CARDS = [
{
title: 'Projects',
body: 'Use projects when a collaboration needs a shared home, milestones, attachments, and team ownership before it becomes a public release.',
},
{
title: 'Challenges',
body: 'Challenges work well for themed prompts, community events, and structured contribution windows that keep the Group active.',
},
{
title: 'Events',
body: 'Events are for launches, showcases, meetups, timed drops, or public moments that need a calendar-style anchor.',
},
{
title: 'Assets',
body: 'The asset library keeps shared files, references, and working materials organized instead of buried in chat history.',
},
{
title: 'Releases',
body: 'Releases package a major publication moment with summary, contributors, milestones, notes, and linked work in one polished surface.',
},
{
title: 'Posts',
body: 'Posts keep the Group human. Use them for updates, recruitment, changelogs, launch notes, and curated public communication.',
},
]
export const BEST_PRACTICES = [
'Keep the Group identity focused. Visitors should understand who you are in seconds.',
'Define Owner, Admin, Editor, and Contributor responsibilities early.',
'Use the simplest permissions setup that supports the team today.',
'Check publishing context before every public action.',
'Credit real people accurately, even when the Group is the publish surface.',
'Use projects and releases for bigger work instead of burying everything in posts.',
'Keep assets tidy so new members are not onboarding into chaos.',
'Pin only the most important public update, not every update.',
'Review inactive memberships and old roles periodically.',
'Use recruitment only when the Group can actually onboard people well.',
'Write release notes that explain what changed and why it matters.',
'Treat the Group page like a living portfolio, not a one-time setup screen.',
]
export const COMMON_MISTAKES = [
'Giving too many people admin power before the team knows how it wants to work.',
'Publishing under the wrong context because no one checked whether Personal Studio or Group Studio was active.',
'Forgetting contributor credit or using vague labels that do not explain the work.',
'Creating a Group with no clear purpose, rhythm, or public identity.',
'Letting the public page go stale after the initial setup.',
'Using the Group identity to hide who actually made the work.',
'Inviting members without setting expectations around ownership, publishing, and approval flow.',
'Treating posts as noise instead of meaningful updates.',
'Keeping an asset library that nobody can search or trust.',
'Adding projects, challenges, events, and releases before the team has a simple baseline workflow.',
]
export const WORKFLOWS = [
{
title: 'Workflow A: Small trusted team',
summary: 'Owner plus one editor and one or two contributors. Simple permissions, direct publishing when the team already trusts the process.',
bullets: ['Use lightweight posts for updates.', 'Keep contributor labels accurate.', 'Only add milestones when a release needs coordination.'],
},
{
title: 'Workflow B: Growing art collective',
summary: 'Owner, admins, editors, and contributors with a review queue and recruitment enabled.',
bullets: ['Use projects for medium-term work.', 'Review submissions before public publishing.', 'Keep the member list and public page curated.'],
},
{
title: 'Workflow C: Release-driven group',
summary: 'A team built around themed drops, packs, or showcase moments.',
bullets: ['Use releases as the main public storytelling surface.', 'Attach artworks, release notes, and milestones.', 'Pair launches with a post and pinned update.'],
},
{
title: 'Workflow D: Community challenge group',
summary: 'A Group centered on challenges, events, and recurring prompts.',
bullets: ['Use join requests or recruiting to control growth.', 'Publish clear challenge briefs and event dates.', 'Keep moderation and review communication constructive.'],
},
]
export const FAQ_ITEMS = [
{
question: 'What is the difference between a personal profile and a Group?',
answer: 'A personal profile is your individual identity. A Group is a shared identity for collaboration and publishing. The Group can publish the work publicly, but contributor credit should still show the people behind it.',
},
{
question: 'Can I publish both personally and as a Group?',
answer: 'Yes. Many creators keep their personal portfolio active while also publishing collaborative work under a Group. The key is to choose the right context before you publish.',
},
{
question: 'Will my name still appear if I publish under a Group?',
answer: 'Yes. Group publishing is meant to preserve authorship, not erase it. Uploaded by, primary author, and contributor credit should still reflect the humans involved.',
},
{
question: 'Who can publish as a Group?',
answer: 'That depends on role and workflow. Owners and admins usually can. Editors often can. Contributors may submit drafts without publishing directly if the Group uses review-first workflows.',
},
{
question: 'Can contributors submit drafts without publishing directly?',
answer: 'Yes. That is one of the most useful Group workflows. Contributors can hand work off for review while editors or admins handle final approval and public publishing.',
},
{
question: 'How do I invite members?',
answer: 'Open Group Studio, go to members or invitations, choose the right role, and send an invite only after you know what that person needs access to.',
},
{
question: 'Can I remove a member later?',
answer: 'Yes. Owners and people with the right member-management permissions can update roles, revoke invitations, or remove active members when needed.',
},
{
question: 'What happens to old artworks if someone leaves the Group?',
answer: 'Existing publishing history and contributor credit should remain as part of the public record unless the content itself changes or is removed through normal moderation or management flows.',
},
{
question: 'Should every team create a Group?',
answer: 'No. Create a Group when you need shared identity, shared workflows, or recurring collaboration. If you only publish solo work, a personal profile may be enough.',
},
{
question: 'How should we use roles?',
answer: 'Start simple. Keep Owner count small, reserve Admin for deeply trusted operators, use Editor for day-to-day management, and keep Contributor focused on creative participation.',
},
{
question: 'Can we recruit new members through the Group page?',
answer: 'Yes, if recruitment is enabled. Use it when the Group is actually ready to onboard people, not just to look active.',
},
{
question: 'What are releases, projects, and challenges used for?',
answer: 'Projects help teams organize work. Releases package major publication moments. Challenges create themed participation and energy. Together they make the Group feel structured and alive.',
},
{
question: 'Can a Group have posts and announcements?',
answer: 'Yes. Posts are useful for release notes, milestone updates, recruitment, public announcements, and pinned context on the Group page.',
},
{
question: 'How should we organize our assets?',
answer: 'Keep them categorized, named clearly, and cleaned up over time. Shared assets should help the team work faster, not become a second mystery archive.',
},
{
question: 'What should we do if contributor credit is wrong?',
answer: 'Fix it quickly. Attribution errors create confusion, trust issues, and sometimes conflict. Confirm who uploaded the work, who authored it, and who contributed before changing anything publicly.',
},
]
export const TROUBLESHOOTING_ITEMS = [
{
title: 'I cannot publish as the Group',
body: 'Check that you are in Group Studio, not Personal Studio. Then confirm your role allows publishing and that the Group is active and not archived or suspended.',
},
{
title: 'I do not see Group Studio',
body: 'You may not be signed in, may not belong to the Group, or may only have a pending invitation. Accept the invite first, then reload Studio.',
},
{
title: 'My role does not let me do what I expected',
body: 'Ask the Owner or Admin which permissions are meant for your role. In many teams, Editors manage content while Contributors only submit drafts.',
},
{
title: 'Contributor credit is wrong',
body: 'Review the publish record carefully: published by, uploaded by, primary author, and contributors each mean different things. Correct the one that is inaccurate rather than replacing all of them.',
},
{
title: 'I was invited but cannot access content',
body: 'Some areas may still be internal, role-limited, or pending approval. First confirm that the invitation was accepted and the membership is active.',
},
{
title: 'I published under the wrong context',
body: 'Stop and review the affected content immediately. Confirm whether it should live under the personal profile or the Group, then correct the publish context before more linked items are built around it.',
},
{
title: 'I do not understand why my draft is in review',
body: 'Your Group may use a review-first workflow so contributors can submit work without publishing directly. Check the review queue feedback or ask the assigned reviewer what needs to change.',
},
{
title: 'I do not know which role to assign someone',
body: 'Ask what they need to do this month, not what title sounds impressive. If you are unsure, start lower and promote later.',
},
]