Introduce VitePress documentation using @cakephp/docs-skeleton#1055
Draft
Introduce VitePress documentation using @cakephp/docs-skeleton#1055
Conversation
There was a problem hiding this comment.
Pull request overview
This PR migrates the CakePHP Migrations plugin documentation from Sphinx/RST to VitePress/Markdown, powered by a shared @cakephp/docs-skeleton theme package. The old RST files, Python config, and Docker-based docs builder are removed in favor of a Node.js-based VitePress setup.
Changes:
- Converts all documentation from RST to Markdown format, adds a new
upgrading.mdguide, and removes the old Sphinx configuration - Introduces VitePress configuration with CakePHP branding via
@cakephp/docs-skeleton, including sidebar TOC, version picker, and theme setup - Removes the old
docs.Dockerfilefor Sphinx-based builds
Reviewed changes
Copilot reviewed 21 out of 23 changed files in this pull request and generated 10 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/package.json | New npm package with VitePress and docs-skeleton dependencies |
| docs/.vitepress/config.js | VitePress config with project-specific overrides |
| docs/.vitepress/theme/index.js | Re-exports CakePHP theme |
| docs/.vitepress/toc_en.json | Sidebar navigation structure |
| docs/en/*.md (new) | Markdown versions of all documentation pages |
| docs/en/*.rst (deleted) | Removed old RST documentation files |
| docs/en/conf.py, docs/config/ (deleted) | Removed Sphinx configuration |
| docs/en/contents.md | Table of contents in markdown |
| docs/en/upgrading.md | New 4.x→5.x upgrade guide |
| docs/.vitepress/cache/deps/* | Build cache artifacts (should not be committed) |
| docs/.gitignore | Git ignore for node_modules and public |
| docs.Dockerfile | Removed old Sphinx Docker build |
Files not reviewed (1)
- docs/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds VitePress-based documentation for this project, powered by the new distributable CakePHP configured VitePress theme
@cakephp/docs-skeletonthat provides CakePHP branding, shared assets, and sensible defaults out of the box.The skeleton follows VitePress's official distributable theme pattern, so the setup here is minimal:
@cakephp/docs-skeleton/configwith project-specific overridesvitepress dev/build/previewcommands — no custom wrappers or env varsnpm updateBefore i address the other versions i want to make sure that we have 5.x handled properly.
@LordSimal it would be great if you could introduce a dokku dockerfile to deploy this one? I removed the docs.Dockerfile from this branch but it can be introduced again using the same naming if needed.
Additionally, (also) after this is done we should swap the main doc repo's to the new node based plugin first as it is a lot easier to maintain like this.