Open
Conversation
…ollaborative_solutions Added <!-- CP-STEPS-START:slug --> / <!-- CP-STEPS-END:slug --> markers around all Control Panel procedural blocks in 59 guides across the email_and_collaborative_solutions product family. Subproducts covered: common_email_features, email_pro, microsoft_exchange, microsoft_office, migrating, mx_plan, troubleshooting, zimbra. Markers are HTML comments — invisible in rendered output.
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.
What type of Pull Request is this?
Description
CP-STEPS marker extraction — web_cloud/email_and_collaborative_solutions
Added / HTML comment markers around all Control Panel procedural blocks in 60 guides across the email_and_collaborative_solutions product family.
Subproducts covered: common_email_features, email_pro, microsoft_exchange, microsoft_office, migrating, mx_plan, troubleshooting, zimbra.
Markers are invisible in rendered output and serve as durable anchors for the NM migration pipeline — downstream agents use them to locate and replace CP-specific content with New Manager equivalents.