As a user, I want to be able to customize the theme of my Homebase or Space. The default theme will be the Nounspace theme, a nounish, nostalgic theme inspired by Myspace.

1. Users can click an edit button (or ✏️) to open Customization Mode.
2. When users are in Customization Mode, they are able to see each of the customizable elements, including Fonts, Colors, and other Settings.
   1. Design idea: remember the macbook touchbar when you’re in design programs? in that spirit, fantasizing about putting all the homebase + space customization besides Fidgets (theme + settings) in a bar at the top or bottom of the screen. (maybe top on web and bottom on mobile? or bottom everywhere)
   • Clickable prototype
3. Users are able to customize the following elements that make up a Theme (examples are defaults):
   • Theme
   • Primary Font
   • Secondary Font
   • Component Color
   • Background
   • Music
   • Settings
4. If a user clicks the Save button, they can see that their Theme settings have been saved.
5. If a user clicks the Share button, they are able to share their theme using the following options:
   1. Publish (may be post MVP)
   2. Cast
   3. Download

Stretch goal or Post MVP: Add undo/redo buttons to the Theme customization menu

Stretch goal or Post MVP: Theme history

Questions

1. How should Theme styles impact Fidget styling, if at all? Yes, POST MVP.
   1. Should Fidget Developers be able to give users the option to let Theme styling override the Fidget style? (ideally yes, but uses should have the option to style Fidgets inside the fidget settings (or use Fidget defaults if no style options exist)
   2. “Meta Themes” - down the road
2. When a Theme is saved, should it be stored on IPFS or should it be Casted?
   1. IPFS
   2. Prompt users to cast whenever they save