Skip to content

Conversation

@meganelacheny
Copy link
Collaborator

@meganelacheny meganelacheny commented Apr 28, 2025

  • Update Overview section to mention status & centralised save button
  • Update Guideflow
  • Update & rewrite "Editing content-types" section
  • Update screenshot in "Editing content-types" section
  • Update & rewrite "Deleting content-types" section
  • Update screenshot in "Deleting content-types" section
@meganelacheny meganelacheny added pr: updated content PRs updating existing documentation content flag: merge pending release Pending Strapi Release source: CMS labels Apr 28, 2025
@meganelacheny meganelacheny self-assigned this Apr 28, 2025
@meganelacheny meganelacheny requested a review from pwizla as a code owner April 28, 2025 12:50
@vercel
Copy link

vercel bot commented Apr 28, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 28, 2025 9:04am
@pwizla pwizla added the temp - port to docs-next (Temporary label) The content of this PR should be ported to docs-next.strapi.io label Apr 29, 2025
pwizla pushed a commit that referenced this pull request Apr 29, 2025
@pwizla pwizla removed the temp - port to docs-next (Temporary label) The content of this PR should be ported to docs-next.strapi.io label Apr 29, 2025
Base automatically changed from cms/CTB-revamp to main April 30, 2025 14:30
@pwizla pwizla added this to the 6.3.2 milestone May 28, 2025
@pwizla pwizla removed the flag: merge pending release Pending Strapi Release label May 28, 2025
@pwizla pwizla merged commit 7899017 into main May 28, 2025
4 of 5 checks passed
@pwizla pwizla deleted the cms/CTB-revamp-stable branch May 28, 2025 14:02
@github-actions
Copy link

🎯 Strapi Documentation Style Review

Automated analysis using Strapi's 12 Rules of Technical Writing

🚀 Enhanced Mode: GitHub API diff analysis
🔍 Scope: Only lines modified in this PR
📊 Repository: strapi/documentation
🎯 PR: #2480

📊 Analysis Results

  • Files analyzed: 1
  • Total issues: 0
  • Critical errors: 0 🚨
  • Warnings: 0 ⚠️
  • Suggestions: 0 💡

🎉 Perfect! Your documentation changes follow all 12 technical writing rules.

✨ What this means:

  • No "easy/difficult" language that might discourage readers
  • Professional, neutral tone maintained
  • Clear, structured content that follows best practices
  • Ready to merge! 🚀

🤖 This is an automated review using GitHub API for maximum precision.

📚 Resources:

🎯 Only issues on lines modified in this PR are shown.
🔧 Manually triggered for PR #2480

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr: updated content PRs updating existing documentation content source: CMS

2 participants