Theme Generator overhaul

[endigo9740]

Describe the feature in detail (code, mocks, or screenshots encouraged)

This will be a broad initiative for updating and replacing the current/static Theme Generator app, with a fully realized cloud-based solution. Enabling users to login, manage and sharing themes, and more. This ticket should serve as the anchor for a number of sub-tasks detailing the specifics for implementing.

NOTE: the theme generator will likely be the last phase of the v5 updates, given it requires all theme and design system updates to be implemented beforehand.

How to Contribute Ideas

This ticket has been created ahead of time to help gather ideas and plan for the theme generator updates. This will be purely focused on what is actually going to be implemented after thorough vetting with the team.

Important

This ticket is not intended for posting personal opinions on the changes (ex: "I don't like having to login"). Please refer to the RFC post or #contributors channel on Discord for those topics instead.

Provide relevant links, wireframes, prototypes, or additional information.

Refer to the Skeleton v5 proposal for more information:

• https://www.notion.so/Skeleton-v5-RFC-33466a04713c809abb60dad12826a140

[endigo9740]

One issue raised on Discord: providing an auth-gate for existing generator features (import, edit, export) might add unnecessary friction for both new and existing users. We should only require auth for users features that absolutely require this if at all possible. Examples of these use cases might include: publishing to the community portal, saving and managing themes in the cloud, etc.

[TazorDE]

Tooling for Authentication: https://better-auth.com/