Skip to content

refactor: move docs from cpp/docs/ to docs/ at repo root#2845

Open
bansiesta wants to merge 8 commits into
mavlink:mainfrom
bansiesta:move-docs-to-root
Open

refactor: move docs from cpp/docs/ to docs/ at repo root#2845
bansiesta wants to merge 8 commits into
mavlink:mainfrom
bansiesta:move-docs-to-root

Conversation

@bansiesta
Copy link
Copy Markdown
Collaborator

Summary

  • Move VitePress docs site from cpp/docs/ to docs/ at the repo root, since docs now cover more than just C++ (Python, Swift, etc.)
  • Update docs_deploy.yml CI workflow paths, working-directory, and artifact path
  • Update path filters in linux.yml, macos.yml, windows.yml, fuzzing.yml
  • Update .gitignore entries for node_modules, cache, and dist
  • Update README.md references
  • Update VitePress edit-on-GitHub links

Note: cpp/tools/generate_docs.sh already referenced ../docs/ so no change needed there.

Test plan

  • CI docs build passes with new path
  • VitePress edit links point to correct GitHub path

🤖 Generated with Claude Code

@bansiesta bansiesta force-pushed the move-docs-to-root branch from 1c6cc98 to b0d650e Compare April 6, 2026 00:38
@julianoes julianoes requested a review from hamishwillee April 7, 2026 21:29
julianoes
julianoes previously approved these changes Apr 7, 2026
Copy link
Copy Markdown
Collaborator

@julianoes julianoes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's try it out. Actually, let me build it locally and see how it looks first.

@julianoes julianoes mentioned this pull request Apr 12, 2026
6 tasks
@hamishwillee
Copy link
Copy Markdown
Collaborator

Ping me when you really want a review, with some expectations - i.e. you just want a sanity check of the concept or whatever.

@julianoes
Copy link
Copy Markdown
Collaborator

Thanks @hamishwillee. What's missing is the overall docs explaining what this is, how we move forward with the new Python wrappers, etc.

Comment thread docs/en/index.md
- [MAVSDK-CSharp](https://github.com/mavlink/MAVSDK-CSharp) (2019): Proof of concept.
- [MAVSDK-Rust](https://github.com/mavlink/MAVSDK-Rust) (2019): Proof of concept.

## New Python Wrappers (`mavsdk` and `aiomavsdk`)
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JonasVautherin we need to go through this.

bansiesta and others added 8 commits April 30, 2026 20:46
The docs cover more than just C++ (Python, Swift, etc.), so move
the VitePress site to the repo root level.

Update CI workflows (docs_deploy.yml, linux.yml, macos.yml,
windows.yml, fuzzing.yml), .gitignore, README, and VitePress
edit-on-GitHub links accordingly.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Add py/tools/generate_markdown.py: AST-based markdown generator
  (no import of packages required)
- Add py/tools/generate_docs.sh: called by root tools/generate_docs.sh
- Generate API reference for all 36 plugins into
  docs/en/python/api_reference/{mavsdk,aiomavsdk}/
- Update docs/en/python/index.md and SUMMARY.md
- Add root tools/generate_docs.sh orchestrator
- Clean RST inline markup (:class:, :meth:) and fix mixed indentation
  in generated docstrings

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
SCRIPT_DIR is cpp/tools/ — one level up landed at cpp/ not the repo
root. Go up two levels to reach docs/en/cpp/api_reference/.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Filter out CStruct classes, from_c_struct/to_c_struct methods,
and destroy() from generated docs. Replace ctypes.c_void_p with
Handle in method signatures.
Replaces the minimal stub with a comprehensive overview page covering
what the new Python packages are, how they differ from MAVSDK-Python
(direct C library binding vs gRPC+server), when to use mavsdk vs
aiomavsdk, installation, and a developer note on the AST-based doc
generator.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds a dedicated "About This Documentation" section to docs/en/index.md
explaining why the docs were moved from cpp/docs/ to the repository root
(single PR can update code and docs together), and a "New Python Wrappers"
section covering:

- What mavsdk and aiomavsdk are (direct libcmavsdk bindings, no gRPC)
- How they differ architecturally from MAVSDK-Python
- The migration path and long-term direction (intended to replace MAVSDK-Python)
- A navigation table so readers can find the right section quickly
- Contributor guidance for where to place new documentation

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants