Bohdan Triapitsyn
ca33c6ae57
Add a Voice & Style section to the docs authoring guide, then bring every docs page in line with it: lead with the task, add success signals to procedures, explain jargon on first use, keep bullet casing consistent, and link out to Troubleshooting where steps can fail. Applied across English source and all localized versions (uk, zh-cn, es, pt-br, ko, pl).
31 lines
738 B
Plaintext
31 lines
738 B
Plaintext
---
|
|
title: Themes
|
|
description: Customize OpenChamber with built-in and user-defined themes.
|
|
---
|
|
|
|
# Themes
|
|
|
|
OpenChamber supports built-in themes and custom theme JSON files.
|
|
|
|
## Add a custom theme
|
|
|
|
1. Create the themes directory:
|
|
|
|
```bash
|
|
mkdir -p ~/.config/openchamber/themes
|
|
```
|
|
|
|
2. Add your JSON file to that directory (for example `my-theme.json`).
|
|
3. Open OpenChamber, then go to **Settings -> Theme -> Reload themes**.
|
|
4. Pick your theme from the dropdown. It applies right away.
|
|
|
|
## Theme location
|
|
|
|
- macOS/Linux: `~/.config/openchamber/themes/`
|
|
|
|
## Full JSON format reference
|
|
|
|
Use the full format guide in the main repo docs:
|
|
|
|
- [`docs/CUSTOM_THEMES.md`](https://github.com/openchamber/openchamber/blob/main/docs/CUSTOM_THEMES.md)
|