Clean up setup page

AJenbo · AJenbo · commit 2499e84c0606 · 2026-03-19T04:51:13.000+01:00
diff --git a/docs/SETUP.md b/docs/SETUP.md
@@ -57,43 +57,12 @@ This creates a `.phpantom.toml` in the current directory. Currently supported se
 
 The file is optional. When absent, all settings use their defaults. New settings will be added as features land. Unknown keys are silently ignored, so the file is forward-compatible.
 
-### Indexing Strategy
-
-By default, PHPantom trusts Composer's autoloader to determine which classes exist in your project. This is intentional: it means completions, diagnostics, and go-to-definition reflect what your code will actually see at runtime. Classes that aren't autoloadable don't appear, because using them would be an error.
-
-The `strategy` setting controls this behaviour:
-
-| Strategy | Behaviour |
-| --- | --- |
-| `"composer"` (default) | Use Composer's classmap when available, self-scan to fill gaps. Results match what `composer dump-autoload` knows about. |
-| `"self"` | Ignore Composer's classmap entirely and scan every PHP file in the workspace. Discovers all classes regardless of autoloading. |
-| `"none"` | Use only Composer's classmap with no fallback scanning. The most conservative option. |
-
-Most projects should leave this at the default. Change it to `"self"` if your project loads classes outside of Composer (custom autoloaders, `require_once`, legacy inclusion patterns). Be aware that `"self"` will also surface vendor-internal classes and potential duplicates that Composer's autoloader would never load.
-
-## Troubleshooting
-
-### Classes from other files are not found
-
-PHPantom resolves cross-file classes through Composer's autoloading rules (PSR-4 mappings and the generated classmap). If a class exists in your project but PHPantom reports it as unknown, the most common causes are:
-
-1. **The class isn't Composer-autoloadable.** If your project loads classes via `require_once`, `include`, or a custom autoloader alongside Composer, those classes won't be discovered by default. Set `strategy = "self"` in `.phpantom.toml` to scan all files.
-
-2. **Composer's classmap is stale.** Run `composer dump-autoload` to regenerate it. PHPantom reads the classmap at startup.
-
-3. **The class is in a directory not covered by `autoload` or `autoload-dev`.** Check that your `composer.json` PSR-4 mappings cover the directory where the class lives.
-
-### Too many classes in completion lists
-
-If you're seeing vendor-internal classes, duplicate framework classes (common in monorepos), or other noise, your indexing strategy may be too broad. The default `"composer"` strategy only surfaces classes that Composer's autoloader can load, which filters out this noise. If you previously set `strategy = "self"`, consider switching back to `"composer"`.
-
 ## Editor Setup
 
 PHPantom communicates over stdin/stdout using the standard [Language Server Protocol](https://microsoft.github.io/language-server-protocol/). Any editor with LSP support can use it. Point the client at the `phpantom_lsp` binary with `php` as the file type. No special initialization options are required.
 
----
-
-### Zed
+<details>
+<summary><b>Zed</b></summary>
 
 A Zed extension is included in the `zed-extension/` directory:
 
@@ -116,9 +85,10 @@ To make PHPantom the default PHP language server, add to your Zed `settings.json
 }
 ```
 
----
+</details>
 
-### Neovim
+<details>
+<summary><b>Neovim</b></summary>
 
 ```lua
 vim.lsp.config['phpantom'] = {
@@ -129,9 +99,10 @@ vim.lsp.config['phpantom'] = {
 vim.lsp.enable('phpantom')
 ```
 
----
+</details>
 
-### VS Code
+<details>
+<summary><b>VS Code</b></summary>
 
 1. **Install a generic LSP client extension**
 
@@ -154,9 +125,10 @@ vim.lsp.enable('phpantom')
    * Add the Language ID: `php`
    * Restart VS Code
 
----
+</details>
 
-### PHPStorm
+<details>
+<summary><b>PHPStorm</b></summary>
 
 1. **Download PHPantom LSP binary**
 
@@ -172,15 +144,16 @@ vim.lsp.enable('phpantom')
 
      * Name: `PHPantom`
      * Command: path to your PHPantom binary
-     * Mapping: add a new Language and set it to `PHP`
+     * Mapping: set `PHP` on both the **Language** tab and the **File Type** tab (the dialogs are identical). Setting both ensures PHPStorm activates the server reliably.
 
-<img width="779" height="645" alt="Screenshot From 2026-02-21 00-28-37" src="https://github.com/user-attachments/assets/2da88e68-d012-476e-82e7-977dbfcd9653" />
+<img width="779" height="645" alt="PHPStorm new language server dialog" src="https://github.com/user-attachments/assets/2da88e68-d012-476e-82e7-977dbfcd9653" />
 
-<img width="779" height="645" alt="Screenshot From 2026-02-21 00-32-24" src="https://github.com/user-attachments/assets/62358f9e-973c-487d-ac17-098d7dab007e" />
+<img width="779" height="645" alt="PHPStorm language server mapping dialog" src="https://github.com/user-attachments/assets/62358f9e-973c-487d-ac17-098d7dab007e" />
 
----
+</details>
 
-### Sublime Text
+<details>
+<summary><b>Sublime Text</b></summary>
 
 > [!NOTE]
 > This configuration is untested. If you get it working (or run into issues), please [open an issue](../../issues).
@@ -198,3 +171,35 @@ With [LSP for Sublime Text](https://github.com/sublimelsp/LSP):
   }
 }
 ```
+
+</details>
+
+## Indexing Strategy
+
+By default, PHPantom trusts Composer's autoloader to determine which classes exist in your project. This is intentional: it means completions, diagnostics, and go-to-definition reflect what your code will actually see at runtime. Classes that aren't autoloadable don't appear, because using them would be an error.
+
+The `strategy` setting controls this behaviour:
+
+| Strategy | Behaviour |
+| --- | --- |
+| `"composer"` (default) | Use Composer's classmap when available, self-scan to fill gaps. Results match what `composer dump-autoload` knows about. |
+| `"self"` | Ignore Composer's classmap entirely and scan every PHP file in the workspace. Discovers all classes regardless of autoloading. |
+| `"none"` | Use only Composer's classmap with no fallback scanning. The most conservative option. |
+
+Most projects should leave this at the default. Change it to `"self"` if your project loads classes outside of Composer (custom autoloaders, `require_once`, legacy inclusion patterns). Be aware that `"self"` will also surface vendor-internal classes and potential duplicates that Composer's autoloader would never load.
+
+## Troubleshooting
+
+### Classes from other files are not found
+
+PHPantom resolves cross-file classes through Composer's autoloading rules (PSR-4 mappings and the generated classmap). If a class exists in your project but PHPantom reports it as unknown, the most common causes are:
+
+1. **The class isn't Composer-autoloadable.** If your project loads classes via `require_once`, `include`, or a custom autoloader alongside Composer, those classes won't be discovered by default. Set `strategy = "self"` in `.phpantom.toml` to scan all files.
+
+2. **Composer's classmap is stale.** Run `composer dump-autoload` to regenerate it. PHPantom reads the classmap at startup.
+
+3. **The class is in a directory not covered by `autoload` or `autoload-dev`.** Check that your `composer.json` PSR-4 mappings cover the directory where the class lives.
+
+### Too many classes in completion lists
+
+If you're seeing vendor-internal classes, duplicate framework classes (common in monorepos), or other noise, your indexing strategy may be too broad. The default `"composer"` strategy only surfaces classes that Composer's autoloader can load, which filters out this noise. If you previously set `strategy = "self"`, consider switching back to `"composer"`.
