Mismatched publication date in blog file name

[dipesh-rawat]

This is a Bug Report

A recent blog file name (2024-04-28-contribute-as-sig-docs-reviewer.md) does not accurately reflect the publication date.

Problem:

A recent mirrored blog file name 2024-04-28-contribute-as-sig-docs-reviewer.md does not reflect the actual publication date and may cause confusion. To maintain accuracy and clarity, we need to update the file name to reflect correct pulbished date (2024-05-16). This will ensure that our file naming conventions are up-to-date and align with our publication practices.

Proposed Solution:

We should update the filename to reflect the correct publication date.

To resolve this issue, follow these steps to update the blog file name with the correct publication date:

• Locate the existing blog file named 2024-04-28-contribute-as-sig-docs-reviewer.md (link here).

• Rename the file to 2024-05-16-contribute-as-sig-docs-reviewer.md to match the current publication date.

- Current Name: content/en/blog/_posts/2024-04-28-contribute-as-sig-docs-reviewer.md

+  Updated Fixed Name: content/en/blog/_posts/2024-05-16-contribute-as-sig-docs-reviewer.md

Page to Update:

• Markdown source: 2024-04-28-contribute-as-sig-docs-reviewer.md

• Blog link: https://kubernetes.io/blog/2024/05/16/contribute-as-sig-docs-reviewer/

Additional Information:

/kind bug
/priority backlog
/language en
/area blog
/triage accepted
/good-first-issue

ℹ️ This task is ideal for a new contributor to pick up as it's a straightforward fix that introduces them to the repository's structure and contribution process. If you have already contributed to Kubernetes documentation in the past, we encourage you to give others the opportunity to get involved. This task presents an excellent entry point for newcomers to make their initial contribution to the project!

[k8s-ci-robot]

@dipesh-rawat:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

This is a Bug Report

A recent blog file name (2024-04-28-contribute-as-sig-docs-reviewer.md) does not accurately reflect the publication date.

Problem:

A recent mirrored blog file name 2024-04-28-contribute-as-sig-docs-reviewer.md does not reflect the actual publication date and may cause confusion. To maintain accuracy and clarity, we need to update the file name to reflect correct pulbished date (2024-05-16). This will ensure that our file naming conventions are up-to-date and align with our publication practices.

Proposed Solution:

We should update the filename to reflect the correct publication date.

To resolve this issue, follow these steps to update the blog file name with the correct publication date:

• Locate the existing blog file named 2024-04-28-contribute-as-sig-docs-reviewer.md (link here).

• Rename the file to 2024-05-16-contribute-as-sig-docs-reviewer.md to match the current publication date.

- Current Name: content/en/blog/_posts/2024-04-28-contribute-as-sig-docs-reviewer.md

+  Updated Fixed Name: content/en/blog/_posts/2024-05-16-contribute-as-sig-docs-reviewer.md

Page to Update:

• Markdown source: 2024-04-28-contribute-as-sig-docs-reviewer.md

• Blog link: https://kubernetes.io/blog/2024/05/16/contribute-as-sig-docs-reviewer/

Additional Information:

/kind bug
/priority backlog
/language en
/area blog
/triage accepted
/good-first-issue

ℹ️ This task is ideal for a new contributor to pick up as it's a straightforward fix that introduces them to the repository's structure and contribution process. If you have already contributed to Kubernetes documentation in the past, we encourage you to give others the opportunity to get involved. This task presents an excellent entry point for newcomers to make their initial contribution to the project!

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dipesh-rawat]

If you have previous experience with contributing to Kubernetes documentation, kindly leave this issue available for new contributors to tackle.

ℹ️ This task is ideal for a new contributor to pick up as it's a straightforward fix that introduces them to the repository's structure and contribution process. If you have already contributed to Kubernetes documentation in the past, we encourage you to give others the opportunity to get involved. This task presents an excellent entry point for newcomers to make their initial contribution to the project!

[ricardoamaro]

Thank you for creating this @dipesh-rawat !

[Shubham82]

closing this issue, as it is resolved by PR #46411
Thanks!
/close

[k8s-ci-robot]

@Shubham82: Closing this issue.

In response to this:

closing this issue, as it is resolved by PR #46411
Thanks!
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.