Skip to content

Add Guideflows to feature pages #2473

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Apr 22, 2025
Merged

Add Guideflows to feature pages #2473

merged 1 commit into from
Apr 22, 2025

Conversation

@meganelacheny
Copy link
Collaborator

Add Guideflow (Light + Dark) for:

  • Content History
  • Draft & Publish
  • i18n
  • Media Library
  • RBAC
  • Releases
  • Review Workflows
@meganelacheny meganelacheny added internal PRs created by the Strapi core team source: CMS labels Apr 18, 2025
@meganelacheny meganelacheny added this to the 6.2.1 milestone Apr 18, 2025
@meganelacheny meganelacheny requested a review from pwizla April 18, 2025 13:47
@meganelacheny meganelacheny self-assigned this Apr 18, 2025
@vercel
Copy link

vercel bot commented Apr 18, 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 Apr 18, 2025 1:47pm
pwizla
pwizla approved these changes Apr 22, 2025
View reviewed changes
Copy link
Collaborator

@pwizla pwizla left a comment

Choose a reason for hiding this comment

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

🫶 🚀
@pwizla pwizla merged commit 58852cb into main Apr 22, 2025
6 checks passed
@pwizla pwizla deleted the cms/feature-guideflows branch April 22, 2025 15:12
@pwizla pwizla changed the title CMS docs: add Guideflows in feature pages Add Guideflows to feature pages Apr 22, 2025
@pwizla pwizla added the pr: updated content PRs updating existing documentation content label Apr 22, 2025
@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: #2473

📊 Analysis Results

  • Files analyzed: 7
  • 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 #2473
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal PRs created by the Strapi core team pr: updated content PRs updating existing documentation content source: CMS

2 participants

@meganelacheny @pwizla