Repository navigation
docs: add DevOps platform and delivery best-practice series - #857
Merged
Merged
Conversation
yuzichen12123
marked this pull request as ready for review
October 20, 2026 04:55
This was referenced Oct 20, 2026
This branch was successfully deployed
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
1 participant
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.
The existing component guides leave readers to work out how project onboarding, build outputs, release approval, promotion, and GitOps fit together. This adds three English articles that provide the overall design, delivery choices, and shared-platform configuration, with links to versioned product guides and a clean companion sample repository.
The articles distinguish the target workflow from the sample's manual execution path, explain credential and policy boundaries, and leave environment-specific recovery and acceptance procedures explicit. Frontmatter uses Article and the ACP/DevOps products; translations and IDs remain generated by the repository workflow.
Validation: immutable dependency installation and the full knowledge-site build passed; metadata, relative links and anchors, five YAML examples, and publication-content checks passed. The companion repository contains one root commit and no imported PR history.
Keep this PR in Draft until the related additions to the versioned Pipelines and Connectors guides have been published and the linked pages and sections have been checked again. Successful HTTP responses alone do not establish that the expected content is live.