Repository navigation
Submitting
Every folder in targets/ becomes a layout on Themezer. When a pull request is merged into master, a GitHub workflow
checks every layout, adds missing UUIDs, renders the layout previews and tells Themezer to import the new commit. A
layout whose folder is removed is retired: it disappears from the layout list and can't be picked for new themes, while
themes that already use it keep working.
You only write JSON. The preview images are rendered for you.
If something in these instructions is unclear, ask on the Themezer Discord.
A layout downloaded from Themezer carries an ID that names the layout and the options chosen for it:
Themezer:<layout ID>|<option value UUID>,<option value UUID>(<entered value>)
For example:
"ID": "Themezer:1975B|0a86b4c1-3fb9-4508-a692-003412571092,4147c2f2-b47a-11ea-b3de-0242ac748591(12)"Never edit this ID by hand. The installer uses it to recognize the layout.
Layouts and option values are identified by UUIDs (00000000-0000-0000-0000-000000000000). They're stored in
details.json and in every option value JSON. Never write, copy or reuse one yourself: the repository adds them when your
submission is checked.
Everything marked with * is required. The instructions below explain each part.
targets
└── 📂 [menu *]
├── 📂 [layout name *]
| ├── 📄 details.json *
| ├── 📄 layout.json *
| ├── 📃 common.json
| ├── 🖼️ overlay-dark.png (rendered for you)
| ├── 🖼️ overlay-light.png (rendered for you)
| └── 📁 options
| ├── 📂 [PRIORITY_TYPE_Name] // TOGGLE, INTEGER, DECIMAL, STRING or COLOR
| | └── 📄 enable.json *
| └── 📂 [PRIORITY_SELECT_Name]
| ├── 📄 [Choice 1].json *
| └── 📄 [Choice 2].json *
└── 📂 _GLOBAL
└── 📁 options // options for every layout of this menu