Creator Hub

Feature Owner: James Derick Billate
Module: Dashboards
Priority: Should
Date: July 9, 2026

Executive Summary

What is this feature?

The Creator Hub dashboard allows Creators to view their projects, quests, adventures, and content status in one central workspace. This feature gives Creators a quick overview of their active work, published content, drafts, and project collections, while providing direct access to continue editing or managing each item.

Why does it matter?

Creators need a clear and reliable starting point for managing their learning content. Without a dashboard, Creators may lose track of which projects are drafts, published, under review, or archived. The Creator Hub reduces confusion, improves workflow visibility, and supports faster decisions on what content needs action next.

What's the MVP scope?

• Summary cards for total quests, published quests, draft quests, and adventures.

• Project/content list with visible status.

• Tabs for quests, adventures, and trash.

• Filtering by skills for active content.

• Navigation from dashboard cards into the correct editor or content library.

1. User Pain Point & Solution

John is creating multiple learning projects in WyzQuests but has difficulty keeping track of which quests are still drafts, which ones are published, and which content needs continued work. He wants one dashboard where he can see his projects and their status without opening each project one by one.

Pain Points

• Emotional: Overwhelmed, unsure, and concerned about losing track of ongoing work.

• Functional: No single overview of project status, content type, publishing state, and quick access to editing.

• Business: Better project visibility increases content completion, improves publishing readiness, and reduces creator workflow delays.

2. 4D Framework Mapping

Diagnose: Provides a clear dashboard overview of a Creator's current projects, quests, adventures, and publishing statuses.

Design: Gives Creators a structured view of content groupings and progress so they can plan next actions.

Develop: Supports active production by allowing Creators to quickly continue editing drafts, inspect published content, and manage projects.

Deliver: Helps ensure content is ready for learners by exposing status and guiding Creators toward publish-ready output.

3. USER FLOWS

Entry Points: Creator logs in and navigates to the Creator Dashboard or is routed to /creator from role-based navigation.

Success Criteria: Creator can view their projects/content, understand status at a glance, and open the correct item for continued work.

Main Path (Happy Path)

1. Creator opens the Creator Hub dashboard.

2. System loads creator analytics summary cards.

3. Creator views total quests, published quests, drafts, and adventures.

4. Creator opens the "My Content" area.

5. Creator switches between Quests, Adventures, and Trash tabs.

6. Creator sees content cards with title, thumbnail, tags, skills, and publishing status.

7. Creator selects a quest or adventure card.

8. System routes Creator to the correct editor view.

9. Creator continues work with project context preserved.

No Data: Display empty state message such as "No current content" when there are no quests or adventures.

API Error: Display error message if analytics or content list cannot be loaded.

Permission Denied: Only authenticated Creators and authorized agency-scoped users can view content assigned to their ownership scope.

Decision Points:

1. IF Creator opens dashboard THEN load analytics and content list ELSE keep dashboard empty.

2. IF content type tab is selected THEN fetch matching content list ELSE keep current list.

3. IF content card is clicked THEN route to quest editor or adventure editor ELSE remain on dashboard.

4. IF content has archived status THEN show it in Trash view ELSE exclude from active content lists.

5. IF skills filter is applied THEN show matching content ELSE show empty filtered state.

4. Information Architecture

Primary Information

• Creator dashboard header.

• Creator analytics summary cards.

• Content/project list.

• Quest or adventure title.

• Publishing status.

• Content type: Quest or Adventure.

Secondary Information

• Thumbnail image.

• Introduction or description preview.

• Tags.

• Skills.

• Duration.

• Enrollment fee.

• Quest mode.

• Folder/project location.

Tertiary Information

• Recent activity.

• AI suggestions.

• Trash state.

• Archived item controls.

• Actions

Actions

• Primary CTA

  • "Create" or content creation action from Creator Header.

  • Open a quest or adventure from its content card.

• Secondary Actions

  • Switch between Quests, Adventures, and Trash.

  • Filter by skills.

  • Clear selected skills.

  • View Library.

  • Archive content.

  • Restore or manage archived content from Trash.

5. Data Requirements

Frontend Needs

• Creator-scoped analytics counts.

• Quest list with title, introduction, tags, skills, thumbnail, publishing status, duration, fee, quest mode, and folder metadata.

• Adventure list with title, introduction, tags, skills, thumbnail, publishing status, duration, fee, and folder metadata.

• Archived content list for Trash view.

• Authentication and agency ownership context.

API Calls Frontend Will Make

• GET /api/creator/analytics

• GET /api/creator/list-quests

• GET /api/creator/list-adventures

• GET /api/creator/(content)/list-archived

• PATCH /api/creator/archive-content

• GET /api/creator/quest-status?quest_id={questId}

6. Performance Considerations

Database Optimization

• Use Creator or agency ownership filters on dashboard queries.

• Use count-only queries for dashboard metric cards.

• Order content by updated_at so recently changed work appears first.

• Exclude archived content from active quest and adventure lists.

• Use indexes on ownership fields, publishing_status, and updated_at for dashboard list speed.

• Frontend Optimization

• Show loading skeletons for analytics and content cards.

• Avoid loading Trash content until the Trash tab is selected.

• Keep skill filtering client-side after the active content list is loaded.

• Limit card content display so long titles, tags, and descriptions do not break the dashboard layout.

7. Security & Authorization

Who Can Access This Feature?

• Administrator: No direct access to Creator Hub.

• Reviewer: No access.

• Creator: Full access to owned or agency-scoped creator content.

• Learner: No access.

• Agency Admin: Limited access only where agency-scoped ownership rules allow dashboard/content visibility.

8. Error Handling

Current Existing Error Handling

• Current Existing Error Handling

• Invalid credentials -> 401 Unauthorized.

• Expired session -> 401 Unauthorized with redirect to login.

• Non-creator attempting to access Creator Dashboard -> permission blocked by layout/auth checks.

• User attempting to view content outside their ownership scope -> filtered out or denied.

• Quest not found -> 404 Not Found or access denied.

• Invalid quest ID for status polling -> 400 Bad Request.

• Analytics fetch failure -> error state in analytics card area.

• Content list fetch failure -> error state in My Content area.

• Database connection failure -> 500 Internal Server Error.

9. Testing Checklist

Happy Path

• Creator navigates to Creator Hub dashboard.

• Analytics cards load totals for quests, published quests, drafts, and adventures.

• Creator views the Quests tab by default.

• Quest cards display title, image, tags, skills, and publishing status.

• Creator switches to Adventures tab.

• Adventure cards display correct project details and status.

• Creator clicks a quest card and is routed to /quest-editor/{id}.

• Creator clicks an adventure card and is routed to /creator/edit-adventure/{id}.

• Creator opens View Library and is routed to /creator/content-library.

• Creator filters by skills and sees matching content only.

• Creator clears skills filter and full content list returns.

Edge Cases

• Creator with no quests sees empty state.

• Creator with no adventures sees empty state.

• Creator with selected skills but no matching content sees filtered empty state.

• Archived content does not appear in active Quests or Adventures tabs.

• Trash tab loads archived content separately.

• API timeout or failed fetch displays a clear error state.

• Unauthorized user cannot access the dashboard.

• Creator cannot view another Creator's private content.

• Malformed analytics response displays an error instead of crashing.

10. OPEN QUESTIONS

• Should Creator Hub separate projects from quests/adventures more explicitly, or is "My Content" sufficient for MVP?

• Should archived items also be available as a filter chip inside the Quests tab, or remain isolated in Trash?

• Should publishing statuses include reviewer workflow labels such as submitted, in review, changes requested, and approved on the dashboard cards?

• Should the dashboard support sorting by status, last updated, or project folder?

• Should dashboard counts include agency-shared content or only content directly created by the logged-in Creator?

11. OUT OF SCOPE

• Advanced project timeline visualization.

• Bulk publishing controls.

• Reviewer queue management.

• Learner performance analytics.

• CSV export of creator dashboard data.

• Custom dashboard widgets.

• Real-time collaborative status updates.

12. SUCCESS METRICS

• Creator can view project/content status from the Creator Hub.

• Creator can identify draft and published content without opening each item.

• Creator can navigate from dashboard to the correct editor.

• Creator can filter content by skills.

• Creator can access archived content through Trash.

18. DEPENDENCIES

This feature depends on

• Clerk Authentication

• Supabase Database

• Creator role authorization

• Agency ownership and resource filtering

• Quest and Adventure content APIs

• Content card UI components

This feature depends on this

• Quest Editor

• Adventure Editor

• Creator Content Library

• Trash Content Management

• Publishing Status Workflow

19. TIMELINE & OWNERSHIP

Backend: James Derick Billate

Frontend: James Derick Billate

QA: Internal development testing

Estimated Completion: Feature completed.

Note: API Endpoints and Schema please refer to its Technical Documentation