Skip to content

Conversation

@Andygol
Copy link
Contributor

@Andygol Andygol commented Jan 3, 2026

Description

This PR introduces changes to the recommendations for placing blog posts in subfolders according to year. This will make it easier to organise blog posts in the future. More specific requirements have also been added regarding how to indicate (or not indicate) the date for draft posts.

RE PR #53736

Issue

Closes: #53735

@k8s-ci-robot k8s-ci-robot requested a review from tengqm January 3, 2026 09:43
@k8s-ci-robot k8s-ci-robot added the language/en Issues or PRs related to English language label Jan 3, 2026
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign urvashi0109 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 3, 2026
@netlify
Copy link

netlify bot commented Jan 3, 2026

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit f94742a
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/6958e4aad3d1e20008c3ac14
😎 Deploy Preview https://deploy-preview-53897--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Member

@lmktfy lmktfy left a comment

Choose a reason for hiding this comment

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

Thanks.

However, I would not want to merge this as is / without more planning:

  • avoid reformatting the parts of the page you don't change
  • we should combine this with a cut over plan about when the blog team will cut over to this new way of working

@lmktfy
Copy link
Member

lmktfy commented Jan 3, 2026

/hold

OK to unhold at any time, but I think this should merge at the same time as PR #53902 (or an equivalent update).

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 3, 2026
Comment on lines +150 to +158
In the GitHub repository, click the **Create new file** button. Name the file
with the blog post in the format
`/content/blog/en/blog/_posts/YYYY/YYYY-00-00-abbreviated-post-title.md`, where
`…/YYYY/…` is the subfolder containing posts for the corresponding year, and
`YYYY-00-00` is part of the file name until the publication date is determined,
after which it will be replaced with the specific publication date. In case you
need to add additional images, charts, etc. to your blog post, create a folder
`/content/blog/en/blog/_posts/YYYY/YYYY-00-00-abbreviated-post-title/` with the
file `_index.md` and additional files for your post.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

It seems that PR #53902 uses a slightly different approach to naming files.

If the decision is made to use it as a basis, the text should be changed as follows

Suggested change
In the GitHub repository, click the **Create new file** button. Name the file
with the blog post in the format
`/content/blog/en/blog/_posts/YYYY/YYYY-00-00-abbreviated-post-title.md`, where
`…/YYYY/…` is the subfolder containing posts for the corresponding year, and
`YYYY-00-00` is part of the file name until the publication date is determined,
after which it will be replaced with the specific publication date. In case you
need to add additional images, charts, etc. to your blog post, create a folder
`/content/blog/en/blog/_posts/YYYY/YYYY-00-00-abbreviated-post-title/` with the
file `_index.md` and additional files for your post.
In the GitHub repository, click the **Create new file** button. Name the file
with the blog post in the format
`/content/blog/en/blog/_posts/YYYY/abbreviated-post-title.md`, where
`…/YYYY/…` is the subfolder containing posts for the corresponding year. In case you
need to add additional images, charts, etc. to your blog post, create a folder
`/content/blog/en/blog/_posts/YYYY/abbreviated-post-title/` with the
file `_index.md` and additional files for your post.

@lmktfy
Copy link
Member

lmktfy commented Jan 4, 2026

I think we should match how the other PR does it, and then that will also match with how the contributor site does it.

See https://github.com/kubernetes/contributor-site/tree/b09fbcbe3b84572be247f53386099eba86fa1c19/content/en/blog/2025 for an example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. language/en Issues or PRs related to English language size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Place blog posts in the respective subfolder according to the year of publication.

3 participants