Added user doc

Author: mnocon

.agents/skills/external/ibexa-documentation/SKILL.md

@@ -1,25 +1,34 @@
 ---
 name: ibexa-documentation
-description: Find answers in the locally installed Ibexa DXP developer documentation. Use when working on an Ibexa DXP project and you need to look up how a feature, API, configuration, or extension point works.
+description: Find answers in the locally installed Ibexa DXP documentation (developer and user docs). Use when working on an Ibexa DXP project and you need to look up how a feature, API, configuration, extension point, or back-office workflow works.
 ---
 
-# Ibexa DXP developer documentation
+# Ibexa DXP documentation
 
 <!-- Placeholder skill: shipped with ibexa/documentation-developer, content to be expanded. -->
 
-The full Ibexa DXP developer documentation is installed locally in
-`vendor/ibexa/documentation-developer/`.
+The full Ibexa DXP documentation is installed locally in
+`vendor/ibexa/documentation-developer/`:
+
+- `developer/` — developer documentation: APIs, extension points,
+  configuration, tutorials.
+- `user/` — user documentation: back office, content management, commerce
+  workflows.
 
 ## Finding a topic
 
-1. Read `vendor/ibexa/documentation-developer/llms.txt` — the table of contents
-   for the whole documentation, grouped by section, with relative links into `doc/`.
-2. Or search directly: `grep -ri "<topic>" vendor/ibexa/documentation-developer/doc/`.
-3. Follow the relative links between pages; they all work offline.
+1. Read the set's table of contents:
+   `vendor/ibexa/documentation-developer/developer/llms.txt` or
+   `vendor/ibexa/documentation-developer/user/llms.txt` — grouped by section,
+   with relative links.
+2. Or search directly:
+   `grep -ri "<topic>" vendor/ibexa/documentation-developer/developer/`.
+3. Follow the relative links between pages (including cross-links between the
+   developer and user docs); they all work offline.
 
 ## Conventions
 
-- One page per directory: `doc/<section>/.../<page>/index.md`.
+- One page per directory: `<set>/<section>/.../<page>/index.md`.
 - PHP API references are links to the class source in `vendor/`, with the fully
   qualified class name as the link text. If the target file doesn't exist, that
   package isn't installed in this project — the class name still tells you what

.gitattributes

@@ -1,7 +1,7 @@
 /* export-ignore
 /.agents export-ignore=false
-/doc export-ignore=false
-/llms.txt export-ignore=false
+/developer export-ignore=false
+/user export-ignore=false
 /composer.json export-ignore=false
 /LICENSE export-ignore=false
 /README.md export-ignore=false

.github/workflows/release_composer_package.yaml

@@ -45,6 +45,13 @@ jobs:
               with:
                   ref: ${{ matrix.branch }}
 
+            - name: Check out user documentation
+              uses: actions/checkout@v4
+              with:
+                  repository: ibexa/documentation-user
+                  ref: ${{ matrix.branch }}
+                  path: user-docs
+
             - name: Set up Python
               uses: actions/setup-python@v3
               with:
@@ -53,7 +60,7 @@ jobs:
             - name: Install dependencies
               run: |
                   python -m pip install --upgrade pip
-                  pip install -r requirements.txt
+                  pip install -r requirements.txt -r user-docs/requirements.txt
 
             - name: Setup PHP
               uses: shivammathur/setup-php@v2
@@ -84,13 +91,17 @@ jobs:
               with:
                   dependency-versions: highest
 
-            - name: Build documentation
+            - name: Build developer documentation
+              run: mkdocs build --strict
+
+            - name: Build user documentation
               run: mkdocs build --strict
+              working-directory: user-docs
 
             - name: Resolve PHP API classes to vendor paths
-              run: php tools/llm_package/dump_class_paths.php site class_paths.json
+              run: php tools/llm_package/dump_class_paths.php site user-docs/site class_paths.json
 
-            - name: Build package Markdown (doc/, llms.txt)
+            - name: Build package Markdown (developer/, user/)
               run: python build_package_docs.py --version "${{ matrix.branch }}"
 
             - name: Copy package README
@@ -118,15 +129,15 @@ jobs:
               run: |
                   # The generated Markdown is never committed/pushed to the branch itself (only
                   # tagged), so there's nothing on the branch to diff against — compare the freshly
-                  # built content to what the last tag captured instead. -f because doc/ and
-                  # llms.txt are gitignored to keep local builds out of the working tree.
-                  git add -f doc llms.txt
+                  # built content to what the last tag captured instead. -f because developer/ and
+                  # user/ are gitignored to keep local builds out of the working tree.
+                  git add -f developer user
                   git add README.md
                   if [[ -z "$LATEST_TAG" ]]; then
                       echo "changed=true" >> "$GITHUB_OUTPUT"
                   # .agents (agent skills, tracked on the branch) is part of the package too;
                   # include it so skill-only edits also produce a release.
-                  elif git diff --cached --quiet "$LATEST_TAG" -- doc llms.txt README.md .agents; then
+                  elif git diff --cached --quiet "$LATEST_TAG" -- developer user README.md .agents; then
                       echo "changed=false" >> "$GITHUB_OUTPUT"
                   else
                       echo "changed=true" >> "$GITHUB_OUTPUT"

.gitignore

@@ -23,4 +23,7 @@ code_samples/_inline_php/
 *.egg-info/
 /doc/
 /llms.txt
+/developer/
+/user/
 /class_paths.json
+/user-docs/