Skip to content

Conversation

@shivansh-gohem
Copy link
Contributor

Hi @eeshaanSA and @khanhtc1202,

As discussed in issue #6124, this PR adds the new "Contribute to PipeCD Documentation" guide.

Following the project's documentation workflow, I've added the new file (contributing-documentation.md) to both:

  • docs/content/en/docs-dev/
  • docs/content/en/docs-v1.0.x/

This new page provides a clear guide for new contributors, covering:

  • Where to find the documentation files
  • How to build the site locally (make run/site)
  • The standard PR process for doc changes

Here is a screenshot of the new page running locally:

Screenshot 2025-10-27 162727

Please let me know if you'd like any changes!

@shivansh-gohem
Copy link
Contributor Author

Hi, @khanhtc1202 could you please review my pr

@khanhtc1202
Copy link
Member

As discussed in the issue, I think you need to relocate the file under /docs-dev/contribution-guidelines/ directory (same level with contributing.md and architecture-overview.md, isn't it?
cc @eeshaanSA
ref: #6124 (comment)

@shivansh-gohem
Copy link
Contributor Author

Thanks for the review, @khanhtc1202!

I've moved the file into the contribution-guidelines directory for both docs-dev and docs-v1.0.x as requested. Please let me know if this is correct!!

## How to submit your changes (The PR Process)

1. **Create a Branch:** Create a new branch for your changes (e.g., `git checkout -b my-docs-fix`).
2. **Make Your Changes:** Edit the necessary documentation files. If you are fixing an issue in the current documentation, remember to edit the file in both the `/docs-dev/` and the latest `/docs-v1.0.x/` folders.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
2. **Make Your Changes:** Edit the necessary documentation files. If you are fixing an issue in the current documentation, remember to edit the file in both the `/docs-dev/` and the latest `/docs-v1.0.x/` folders.
2. **Make Your Changes:** Edit the necessary documentation files. If you are fixing an issue in the current documentation, remember to edit the file in both the `/docs-dev/` and the latest `/docs-vx.y.z/` folders.

nits, since we maintain both v0.55.x and v1.0.x in the meantime.

## How to submit your changes (The PR Process)

1. **Create a Branch:** Create a new branch for your changes (e.g., `git checkout -b my-docs-fix`).
2. **Make Your Changes:** Edit the necessary documentation files. If you are fixing an issue in the current documentation, remember to edit the file in both the `/docs-dev/` and the latest `/docs-v1.0.x/` folders.
Copy link
Member

Choose a reason for hiding this comment

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

@shivansh-gohem
Copy link
Contributor Author

Thanks, @khanhtc1202! I've applied the suggested text change to both files!!

Copy link
Contributor

@eeshaanSA eeshaanSA left a comment

Choose a reason for hiding this comment

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

Additionally, it would be also great to explicitly mention that our documentation resides on https://pipecd.dev, our website.


Welcome! We are so happy you're interested in helping improve our documentation. Your contributions make the project better for everyone.

This guide explains how you can submit documentation changes.
Copy link
Contributor

Choose a reason for hiding this comment

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

"how you can contribute to the PipeCD Documentation"

@eeshaanSA
Copy link
Contributor

@shivansh-gohem Sorry for the delay in response.

The overall structure looks good, just some minor changes and this should be merged into the main. Thank you for your contribution. 👍

@shivansh-gohem
Copy link
Contributor Author

Thank you, @eeshaanSA! I appreciate the feedback. I've just pushed a commit that applies both of your suggestions to the files. Thanks for guiding this!

Signed-off-by: Shivansh Sahu <sahushivansh142@gmail.com>
Signed-off-by: Shivansh Sahu <sahushivansh142@gmail.com>
Signed-off-by: Shivansh Sahu <sahushivansh142@gmail.com>
@shivansh-gohem
Copy link
Contributor Author

Thanks, @eeshaanSA! I've updated the metadata in both files to include description and the correct weight: 4.

I've also rebased the branch to resolve the 'out-of-date' warning. Please let me know if this looks good!

@eeshaanSA
Copy link
Contributor

eeshaanSA commented Nov 14, 2025

@shivansh-gohem, please take a look at the metadata from other files on the documentation. Here is one for reference. I understand it can be overwhelming, but it is fairly easy once you take a look.

Signed-off-by: Shivansh Sahu <sahushivansh142@gmail.com>
shivansh-gohem and others added 2 commits November 15, 2025 15:33
…documentation.md

Co-authored-by: Eeshaan Sawant <100678386+eeshaanSA@users.noreply.github.com>
Signed-off-by: shivansh-gohem <sahushivansh142@gmail.com>
Signed-off-by: Shivansh Sahu <sahushivansh142@gmail.com>
@shivansh-gohem
Copy link
Contributor Author

Hi @eeshaanSA, thank you for all the help! I've just pushed the final metadata fix to both files, matching your suggestion. I believe it's all correct now.

@eeshaanSA
Copy link
Contributor

eeshaanSA commented Nov 15, 2025

LGTM 🚀 with nits

cc @khanhtc1202

…documentation.md

Co-authored-by: Eeshaan Sawant <100678386+eeshaanSA@users.noreply.github.com>
Signed-off-by: shivansh-gohem <sahushivansh142@gmail.com>
Signed-off-by: Shivansh Sahu <sahushivansh142@gmail.com>
@shivansh-gohem
Copy link
Contributor Author

All changes are done!!

@eeshaanSA
Copy link
Contributor

eeshaanSA commented Nov 17, 2025

Thanks @shivansh-gohem

Copy link
Contributor

@eeshaanSA eeshaanSA left a comment

Choose a reason for hiding this comment

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

LGTM 🚀

@eeshaanSA
Copy link
Contributor

@shivansh-gohem check out the EPIC issue, maybe there are more sections you can help on. 👀

Signed-off-by: Shivansh Sahu <sahushivansh142@gmail.com>
Copy link
Member

@khanhtc1202 khanhtc1202 left a comment

Choose a reason for hiding this comment

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

Thanks @shivansh-gohem 🙌

@khanhtc1202 khanhtc1202 enabled auto-merge (squash) November 24, 2025 06:08
@khanhtc1202 khanhtc1202 merged commit ea02853 into pipe-cd:master Nov 24, 2025
43 checks passed
@github-actions github-actions bot mentioned this pull request Dec 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants