docs: add Dutch WooCommerce v6 migration page - #207
Merged
Conversation
Adds /nl/documentatie/10.woocommerce-v6.0.html describing the migration from plugin v4 to v6: what changed, when to switch, and a step-by-step upgrade guide (backup, staging test, manual install, settings checklist). Also fixes the broken releases GitHub shield on the v5 page (trailing slash in the repo attribute caused a 404 badge). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
✅ Deploy Preview for myparcel-developer-portal ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Adds /documentation/10.woocommerce-v6.0.html as the English counterpart and links both pages via the languages frontmatter. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
NabDevs
approved these changes
Aug 5, 2026
FreekVR
requested changes
Aug 5, 2026
FreekVR
left a comment
FreekVR
left a comment
Contributor
There was a problem hiding this comment.
Some small suggestions and double-checks. Looks good overall.
The comments I made are also relevant for the corresponding Dutch translations.
- Nuance the carrier capabilities claim: only existing options are unlocked via the MyParcel API; new carriers and shipment options still arrive with plugin updates - Add a note for Belgian SendMyParcel users about the plugin rename, advising to contact support before migrating - Soften the test-label costs claim: costs differ per carrier Applied to both the English and Dutch versions. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
FreekVR
approved these changes
Aug 6, 2026
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
3 participants
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.
What
Adds a new Dutch documentation page at
/nl/documentatie/10.woocommerce-v6.0.htmlthat guides WooCommerce merchants through the migration from plugin v4 to v6:Also fixes the broken releases GitHub shield on the v5 page (trailing slash in the
repoattribute caused a 404 badge); the new page uses the fixed attribute as well.Why
We will show a notice in the v4 plugin advising merchants to upgrade to v6 ahead of the September store release. That notice needs a documentation page to link to, describing the differences and every migration step.
How to test
Run
yarn devand open/nl/documentatie/10.woocommerce-v6.0.html. Verified locally: page renders with the portal styling, shields resolve (releases badge shows v6.7.3), note containers and the comparison table render correctly, and the page is picked up by the sidebar.