Integrate repositories documentation into the documentation website

[bcastets-robotiq]

• I updated the documentation website to retrieve documentation of all repositories.
• A table is automatically generated to sumup the software tools available for each product
• A contribute file have been written to explain the documentation procedure
• The example section have been removed because it is empty.

[mbegin-robotiq]

Added three commits to this branch

While reviewing, I pushed a few changes on top of the existing work:

• 3f564d5 — Fix broken footer link to removed /docs/drivers page
  The footer "Drivers" link still pointed at /docs/drivers, which this PR deletes. With onBrokenLinks: 'throw', that made docusaurus build (and the deploy workflow) fail on every page. Repointed it to /docs/intro, the docs entry point that now hosts the generated tools table. This is what was blocking the production build.

• ae30f4c — Add preview.sh
  One-command wrapper around the local workflow documented in docs/contribute.mdx: syncs submodules, installs deps if missing, and starts the dev server. Usage: ./preview.sh [port].

• 81f91a5 — Add CI pipeline (.github/workflows/ci.yml)
  Runs npm ci → npm run build → npm test on every PR to main. The build step fails on broken links/anchors; the new npm test (scripts/check-build.js) smoke-tests the output (key pages present + tools table injected into the intro page). Intended to be a required status check for merging. Verified it fails without the footer fix above and passes with it.

The remaining items I found are posted as separate review comments above rather than changed here, since they warrant a decision (taxonomy grouping, generated-file/gitignore cleanup, orphan pages, the /docs/hardware HTML warning, GraspGen spelling, clickable-vs-static homepage cards, and gating broken anchors).

[ebarnett3]

autres commentaires mineurs de claude:

## Plausible (real mechanism, needs a future input to trigger)

5. **`scripts/sync-external-docs.js:111`** — single-file sync jobs rewrite relative image links to GitHub `blob/` URLs, which serve HTML, not image bytes. No current synced README has images, but the first upstream README that adds one renders broken; use `raw.githubusercontent.com`.

6. **`scripts/generate-tools-table.js:66`** — `docHref` only escapes spaces; a future folder containing `#`, `?`, or `%` emits a corrupt link and fails the whole build via `onBrokenLinks: 'throw'` (the `C++` handling itself is correct).

7. **`scripts/generate-tools-table.js:42`** — hand-rolled frontmatter regex keeps quotes and mishandles colons in titles (`title: "Foo: bar"` → wrong column key). All current titles parse fine; gray-matter is already in the lock file transitively and would make this robust.

8. **`scripts/sync-external-docs.js:84`** — the leading-H1 strip regex anchors at byte 0, so a README starting with a badge or blank line before its `# Title` keeps the H1 → duplicate heading on the page.

## Minor

- CI checks out submodules twice (`submodules: true` in checkout + the script's `git submodule update --init --force`).
- `fetch-depth: 0` in ci.yml is unnecessary (build never uses history).
- `prestart`/`prebuild` are copy-pasted identical strings; factor into one script.
- Each tool `index.mdx` is read from disk twice per table generation (`readFrontmatterTitle` + `readCompactBadge`).

[bcastets-robotiq]

Merci pour la revue du code. C'est la première fois que je passe au travers de ce process de PR, ca va peut etre me prendre du temps de comprendre comment le compléter. Je me lance !

[ebarnett3]

Merci pour la revue du code. C'est la première fois que je passe au travers de ce process de PR, ca va peut etre me prendre du temps de comprendre comment le compléter. Je me lance !

Généralement, si t'es d'accord avec les revues tu peux déléguer les changements à claude. Il peut aider pour répondre quand t'es pas d'accord aussi!