docs: translate the PipeCD plugin development book to English#6788
Closed
vanshika2720 wants to merge 2 commits into
Closed
docs: translate the PipeCD plugin development book to English#6788vanshika2720 wants to merge 2 commits into
vanshika2720 wants to merge 2 commits into
Conversation
Signed-off-by: Vanshika <pahalvanshikaa@gmail.com>
Contributor
|
@vanshika2720, the plugin development book/documentation planned under the LFX mentorship scope. Closing for now. |
Author
|
@rahulshendre Apologies. I was already aware this area is planned under the mentorship scope. I opened this PR only as a small proof of concept while exploring the “Plugin Development Book, Docs DX, and Adoption Growth” project idea and understanding the documentation workflow better nothing beyond that. I’ll avoid opening PRs in this area going forward and will focus on other good first issues instead |
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.
docs: Translate the Japanese PipeCD Plugin Development Book into English
Description
This Pull Request translates the comprehensive Japanese PipeCD Plugin Development Book:
by:
into English.
The translated book is hosted under a newly structured documentation path:
and serves as a step-by-step walkthrough and reference guide for developers building custom PipeCD plugins.
As PipeCD continues expanding its pluggable continuous delivery architecture, this book provides an important developer-focused resource covering the complete lifecycle of implementing a custom local file synchronization plugin using the official Go SDK.
Technical Highlights & Content Breakdown
The translated book consists of:
organized under a new Hugo documentation section.
Section Index (
_index.md)Added a new Hugo section index to:
weight: 10)under the:
documentation section.
Foundational & Architecture Guides (Chapters 1–6)
These chapters introduce:
Topics include:
FILE_DIFFFILE_SYNCFILE_ROLLBACKand deep dives into:
StagePluginDeploymentPluginLiveStatePluginwithin PipeCD’s pluggable architecture.
Core Development Walkthrough (Chapters 7–16)
Covers complete plugin implementation using the official Go SDK:
Topics include:
sdk.DeploymentPlugincontractconfigdeployTargetConfigapplicationConfigPipelineSyncQuickSyncExecuteStageEngine Implementation & Testing (Chapters 17–20)
Provides a full walkthrough of implementing the local file synchronization engine using Go standard library packages including:
io/fspath/filepathosDetailed implementations include:
listFilesdifferenceFilesisFileContentDifferentcopyFilesremoveFilesAlso covers robust implementations for:
FILE_DIFFFILE_SYNCFILE_ROLLBACKincluding rollback synchronization against:
instead of:
Integration & E2E Testing (Chapters 21–22)
Covers end-to-end local development and testing using:
Additional topics include:
pluginsblock in PipedQuality & Compliance Standards Met
Terminological Consistency
All translated terminology was aligned with official PipeCD architecture and documentation standards including:
SDK Stability Context
Added technical notes explaining SDK compatibility and architecture context around:
and SDK version:
Developers are encouraged to cross-reference:
for long-term compatibility awareness.
Code Integrity
Preserved all original:
without modification to maintain implementation correctness.
Formatting
Verified and formatted all modified files using:
to maintain documentation consistency and clean formatting.
DCO Compliance
All commits in this branch are signed off in compliance with:
How to Review / Preview
Switch to branch
Inspect translated documentation
Run local Hugo server
cd docs npm install npm run startThis verifies:
within the developer guide.