-
Notifications
You must be signed in to change notification settings - Fork 15.2k
Specifying dates for blog posts #53897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
lmktfy
left a comment
There was a problem hiding this 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
|
/hold OK to unhold at any time, but I think this should merge at the same time as PR #53902 (or an equivalent update). |
| 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. |
There was a problem hiding this comment.
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
| 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. |
|
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. |
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