[5.3] Creator Hub

Author: James Derick Billate
Reviewer:
Creation Date: March 27, 2026
Status: Draft
References: https://github.com/wyzlab/WyzQuests/issues/77

INTRODUCTION & GOALS

Problem Summary: This feature displays all the active or created projects (quests and adventures) in a dashboard. Specifically for creators to view the list or cards of their projects.

Goals & Non-Goals: That the creator will have an easy and efficient navigation to view and access their projects (quests and adventures) without the need of manually checking via a database. However it is limited first with viewing, no organization of projects is done in the feature.

HIGH-LEVEL ARCHITECTURE

System Diagram:

Technologies Used: Clerk Authentication, Typescript, Next.js, Postgres (Supabase) and Tailwind CSS

DETAILED DESIGN & IMPLEMENTATION

API Specification:

GET /api/creator/(content)/list-adventures
Retrieving all adventures

GET /api/creator/(content)/list-quests
Retrieving all quests

GET /api/creator/(content)/list-archived
Retrieving all archived quests and adventures

Logic & Workflows: To be updated, no prior documentation regarding this matter, necessary additions will be indicated during the testing process.

INFRASTRUCTURE & OPERATIONS

Dependencies:

The creator hub will only have its main functions be presented and tested efficiently if the features for generating and managing quests are stable and functional. Thus this feature is dependent from these:

• [1.1] Project Creation

• [2.1] Form Editor

Monitoring & Alerting: To be indicated after further testing. No prior documentation regarding this matter

Deployment Plan:

1. There should be an existing ‘quest’ table for retrieval of quest information.

2. Every card displayed should be redirected to a particular quest indicated.

3. Ensure that the UI/UX of the card must dynamic to mobile or desktop views.

4. After which, deployment will be safely transmitted to production.

TESTING & QUALITY ASSURANCE

Testing Strategy:

1. Ensure that there is a quest table available on the WyzQuest’s database.

2. Ensure that there are available quests stores from this table for accurate and functionable testing.

3. Card must redirect to specific quests indicated.

Known Limitations: There are no known edge cases whatsoever have be documented throughout the testing process. Nonetheless, if such case will be determined, changes to this document will be applied.

MAINTENANCE & SUPPORT

Troubleshooting:

1. For in case, in fetching quests. Check first there are ZOD validation, regex expression errors. Nonetheless, check the quest if its existing on the database.

Changelog: No prior historical record were documented, neither in Github or via workspace. If such evidence arise during the testing process, necessary additions to this document must be indicated.

Document version: 1.0 - Draft, Feature already exists on dev server before and after initial dev review, 04/06/2026