> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qomicex.top/llms.txt
> Use this file to discover all available pages before exploring further.
# Plugin settings pages (settingsPages)
## Plugin settings pages (settingsPages)
Plugins often need their own configuration UI (toggles, API keys, default behavior). Instead of scattering **Settings** buttons across plugin pages, put the settings UI **inside the Launcher**: in **Settings → Plugins → Plugin settings (Settings → Plugins → Plugin Settings)** the left side lists one vertical tab per plugin and the right side shows the settings UI that plugin provides. Users can find it and do not get lost.
## Quick start
**Step 1**: Declare a Plugin settings page (Plugin Settings) in `contributes.settingsPages` of `manifest.json` (the relative path of an HTML file inside the `.qplugin` package):
```json theme={null}
{
"id": "top.qomicex.weather",
"name": "Weather",
"version": "1.0.0",
"layers": ["l2"],
"entry": { "frontend": "dist/index.html" },
"contributes": {
"settingsPages": ["dist/settings.html"]
}
}
```
**Step 2**: Write `dist/settings.html` inside the package. It is a plain HTML page running in **exactly the same Sandbox environment** as the plugin's main page (iframe Sandbox + full `__PLUGIN_API__` Bridge + injected theme variables); use `getSettings` / `setSettings` to read and write the plugin's own configuration:
```html theme={null}
City
The city shown by the weather widget
Auto refresh
Refresh the weather data every 10 minutes
```
**Step 3**: Pack the `.qplugin`, install it, and enable the plugin. **Settings → Plugins → Plugin settings** now shows a tab named after the plugin, and opening it shows the UI you wrote.
## Runtime environment
* **iframe Sandbox**: `