-
Notifications
You must be signed in to change notification settings - Fork 258
Add a migration best practices guide #16646
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Documentation ReviewI've reviewed PR #16646 which adds a comprehensive migration best practices guide. Overall, this is excellent documentation that fills an important gap in the migration journey. The content is well-structured, practical, and actionable. Issues FoundBroken LinksLine 14 ( Wait - actually, I need to verify this is a Hugo-style trailing slash link, which should work. Let me note it as something to verify during build. Lines 464, 491 ( Lines 487-489 ( Style IssuesLine 337 ( Positive Observations✅ Front matter is complete with proper title, meta_desc, h1, and menu configuration Content QualityThe guide excels at:
Minor RecommendationsConsider these enhancements (not blocking):
Verification NeededDuring
Hugo's link checking should catch any 404s. This is high-quality documentation that will significantly help users navigate the migration journey. The practical, real-world focus is exactly what's needed. @claude if you'd like me to review any revisions or provide additional feedback on specific sections. |
|
Your site preview for commit dea2d94 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-16646-dea2d940.s3-website.us-west-2.amazonaws.com. |
|
Your site preview for commit 114cf61 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-16646-114cf61d.s3-website.us-west-2.amazonaws.com. |
No description provided.