Skip to content

Commit b7901cb

Browse files
committed
Push date to 2025-12-22
1 parent 88ebdea commit b7901cb

File tree

2 files changed

+16
-2
lines changed

2 files changed

+16
-2
lines changed

.github/instructions/website.blog.instructions.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ date: YYYY-MM-DD
1919
description: "SEO-optimized summary (150-160 characters)"
2020
authors: [author-key] # From blog/authors.yml
2121
tags: [tag1, tag2] # From blog/tags.yml
22+
draft: false # Optional: set to true to hide from production
2223
---
2324
```
2425

@@ -30,6 +31,18 @@ tags: [tag1, tag2] # From blog/tags.yml
3031
- [ ] `authors`: Valid keys from `blog/authors.yml`
3132
- [ ] `tags`: Valid keys from `blog/tags.yml`
3233

34+
### Blog Post Date
35+
36+
The publish date is determined by the **folder name** (e.g., `2025-12-19-my-post/index.md`). Docusaurus extracts the date from folder/filename patterns like `YYYY-MM-DD-slug` or `YYYY/MM/DD/slug`. If you specify a `date` in front matter, it **overrides** the folder-derived date.
37+
38+
**Important**: Unlike Jekyll, Docusaurus does **NOT** hide future-dated posts. All posts are published immediately when deployed, regardless of date. To prevent premature publishing:
39+
40+
- Use `draft: true` in front matter to exclude from production builds (visible only in dev)
41+
- Use `unlisted: true` to hide from listings but keep accessible via direct link
42+
- Alternatively, keep the post in a separate branch until ready
43+
44+
**Before merging**: If PR review takes longer than expected and the folder date becomes stale, update the folder name (or add a `date` override in front matter) to reflect the actual publish date. Posts should show the date readers will see them, not when they were originally drafted.
45+
3346
## Content Structure
3447

3548
### Required Pattern
@@ -248,7 +261,8 @@ See our previous post on [AKS networking fundamentals](/2024/01/15/aks-networkin
248261

249262
## Common Mistakes to Avoid
250263

251-
**Future-dated posts**: Will not appear on site until publish date
264+
**Future-dated posts without `draft: true`**: Docusaurus publishes all posts immediately—use `draft: true` to hold back unready content
265+
**Stale dates from long PR reviews**: Update the folder name or add `date` front matter before merging if the original date is now in the past
252266
**Missing truncate marker**: Full post shows on listing page
253267
**Bare URLs**: Always use `[text](url)` syntax
254268
**Locale based URLs**: Use generic links (no `/en-us/`)

website/blog/2025-12-16-deploy-aks-automatic-terraform-helm/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Deploy Apps to AKS Automatic with Terraform and the Helm Provider"
3-
date: 2025-12-16
3+
date: 2025-12-22
44
description: "Learn how to deploy AKS Automatic with the AzApi provider for Terraform and configure the Helm provider for Azure RBAC token-based authentication."
55
authors: [paul-yu]
66
tags: [aks-automatic, developer, best-practices]

0 commit comments

Comments
 (0)