docs

Author: ericdallo

docs/configuration.md

@@ -68,6 +68,39 @@ For MCP servers configuration, use the `mcpServers` config, example:
 }
 ```
 
+## Custom command prompts
+
+You can configure custom command prompts for project, global or via `commands` config pointing to the path of the commands.
+Prompts can use variables like `$ARGS`, `$ARG1`, `ARG2`, to replace in the prompt during command call.
+
+=== "Local custom commands"
+
+    A `.eca/commands` folder from the workspace root containing `.md` files with the custom prompt.
+
+    `.eca/commands/check-performance.md`
+    ```markdown
+    Check for performance issues in $ARG1 and optimize if needed.
+    ```
+
+=== "Global custom commands"
+
+    A `$XDG_CONFIG_HOME/eca/commands` or `~/.config/eca/commands` folder containing `.md` files with the custom command prompt.
+
+    `~/.config/eca/commands/check-performance.mdc`
+    ```markdown
+    Check for performance issues in $ARG1 and optimize if needed.
+    ```
+
+=== "Config"
+
+    Just add to your config the `commands` pointing to `.md` files that will be searched from the workspace root if not an absolute path:
+
+    ```javascript
+    {
+      "commands": [{"path": "my-custom-prompt.md"}]
+    }
+    ```
+
 ## Rules
 
 Rules are contexts that are passed to the LLM during a prompt and are useful to tune prompts or LLM behavior.
@@ -114,39 +147,6 @@ There are 3 possible ways to configure rules following this order of priority:
     }
     ```
 
-## Custom command prompts
-
-You can configure custom command prompts for project, global or via `commands` config pointing to the path of the commands.
-Prompts can use variables like `$ARGS`, `$ARG1`, `ARG2`, to replace in the prompt during command call.
-
-=== "Local custom commands"
-
-    A `.eca/commands` folder from the workspace root containing `.md` files with the custom prompt.
-
-    `.eca/commands/check-performance.md`
-    ```markdown
-    Check for performance issues in $ARG1 and optimize if needed.
-    ```
-
-=== "Global custom commands"
-
-    A `$XDG_CONFIG_HOME/eca/commands` or `~/.config/eca/commands` folder containing `.md` files with the custom command prompt.
-
-    `~/.config/eca/commands/check-performance.mdc`
-    ```markdown
-    Check for performance issues in $ARG1 and optimize if needed.
-    ```
-
-=== "Config"
-
-    Just add to your config the `commands` pointing to `.md` files that will be searched from the workspace root if not an absolute path:
-
-    ```javascript
-    {
-      "commands": [{"path": "my-custom-prompt.md"}]
-    }
-    ```
-
 ## All configs
 
 === "Schema"

docs/installation.md

@@ -1,42 +1,47 @@
 # Installation
 
-:warning: ECA is already automatically downloaded in all editor plugins, so you don't need to download it manually, even so, if you want that, follow below:
-
-Eca is written in Clojure and compiled into a native binary via graalvm. You can download the [native binaries from Github Releases](https://github.com/editor-code-assistant/eca/releases) or use one of the methods below:
-
-## Editor (recommended)
-
-ECA is already downloaded automatically by your ECA editor plugin, so you just need to install the plugin for your editor:
-
-- [Emacs](https://github.com/editor-code-assistant/eca-emacs)
-- [VsCode](https://github.com/editor-code-assistant/eca-vscode)
-- [Vim](https://github.com/editor-code-assistant/eca-nvim)
-- Intellij: Planned, help welcome
-
-## Script (recommended if manual installing)
-
-Stable release:
-
-```bash
-bash <(curl -s https://raw.githubusercontent.com/editor-code-assistant/eca/master/install)
-```
-
-Or if facing issues with command above:
-```bash
-curl -s https://raw.githubusercontent.com/editor-code-assistant/eca/master/install | sudo bash
-```
-
-nightly build:
-
-```bash
-bash <(curl -s https://raw.githubusercontent.com/editor-code-assistant/eca/master/install) --version nightly --dir ~/
-```
-
-## Homebrew (MacOS and Linux)
-
-We have a custom tap using the native compiled binaries for users that use homebrew:
-
-```bash
-brew install editor-code-assistant/brew/eca
-```
-
+Eca is written in Clojure and compiled into a native binary via graalvm.
+
+!!! info "Warning"
+
+    ECA is already automatically downloaded and updated in all editor plugins, so you don't need to handle it manually, even so, if you want that, check the other methods.
+
+=== "Editor (recommended)"
+
+    ECA is already downloaded automatically by your ECA editor plugin, so you just need to install the plugin for your editor:
+    
+    - [Emacs](https://github.com/editor-code-assistant/eca-emacs)
+    - [VsCode](https://github.com/editor-code-assistant/eca-vscode)
+    - [Vim](https://github.com/editor-code-assistant/eca-nvim)
+    - Intellij: Planned, help welcome
+  
+=== "Script (recommended if manual installing)"
+
+    Stable release:
+    
+    ```bash
+    bash <(curl -s https://raw.githubusercontent.com/editor-code-assistant/eca/master/install)
+    ```
+    
+    Or if facing issues with command above:
+    ```bash
+    curl -s https://raw.githubusercontent.com/editor-code-assistant/eca/master/install | sudo bash
+    ```
+    
+    nightly build:
+    
+    ```bash
+    bash <(curl -s https://raw.githubusercontent.com/editor-code-assistant/eca/master/install) --version nightly --dir ~/
+    ```
+
+=== "Homebrew"
+
+    We have a custom tap using the native compiled binaries for users that use homebrew:
+    
+    ```bash
+    brew install editor-code-assistant/brew/eca
+    ```
+
+=== "Gtihub releases"
+
+    You can download the [native binaries from Github Releases](https://github.com/editor-code-assistant/eca/releases), although it's easy to have outdated ECA using this way.

mkdocs.yml

@@ -41,6 +41,8 @@ markdown_extensions:
   - meta
   - toc:
       permalink: '#'
+  - admonition
+  - pymdownx.details
   - pymdownx.emoji:
       emoji_index: !!python/name:materialx.emoji.twemoji
       emoji_generator: !!python/name:materialx.emoji.to_svg