Pelican blog post frontmatter specification and validation rules. Defines required metadata fields, naming conventions, and i18n linking rules for ja-jp/en-us bilingual blog posts. Use when generating, reviewing, or validating blog post markdown files.
Specification for blog post metadata in this Pelican-based bilingual blog.
Every blog post file MUST start with the following metadata block. No --- fences — just plain Key: value lines:
Title: {title}
Date: {YYYY-MM-DD}
Slug: {slug}
Lang: {ja-jp or en-us}
Category: {category}
Tags: {comma-separated tags}
Summary: {summary}
After the last metadata line, leave one blank line, then begin the article body.
| Field | Required | Rules |
|---|---|---|
Title | Yes | Descriptive and concise. Written in the target language (Japanese for ja-jp, English for en-us). |
Date | Yes | YYYY-MM-DD format. The date the content was written or researched. |
Slug | Yes | Lowercase, hyphen-separated. Must be identical across ja-jp and en-us versions for Pelican i18n_subsites linking. Example: finops-ai-agent |
Lang | Yes | Exactly ja-jp or en-us. |
Category | Yes | Default: notebook. Use lowercase. |
Tags | Yes | Comma-separated, lowercase. Example: azure, aks, monitoring |
Summary | Yes | 1-2 sentence abstract in the target language. |
| Field | Usage |
|---|---|
Status | draft to hide from published output. Omit for published posts. |
Modified | YYYY-MM-DD format. Set when updating an existing post. |
Authors | Author name. Only needed if different from the default. |
Slug and Date.content/posts/ja-jp/<slug>.md and content/posts/en-us/<slug>.mdTitle and Summary must be localized to each language — not transliterated.--- fences around metadataDate is valid YYYY-MM-DDLang is exactly ja-jp or en-usSlug is lowercase, hyphen-separated, no special charactersSlug matches between ja-jp and en-us filesTags are comma-separated and lowercaseSummary is present and conciseTitle: AKS 監視構成案レビュー（Azure Monitor / Managed Prometheus）
Date: 2026-03-05
Slug: aks-monitoring-architecture-review
Lang: ja-jp
Category: notebook
Tags: azure, azure-monitor, aks, prometheus, grafana, observability
Summary: AKS の監視構成案について Azure Monitor 観点で実現性・注意点・コスト最適化ポイントを整理。
Title: AKS Monitoring Architecture Review (Azure Monitor / Managed Prometheus)
Date: 2026-03-05
Slug: aks-monitoring-architecture-review
Lang: en-us
Category: notebook
Tags: azure, azure-monitor, aks, prometheus, grafana, observability
Summary: Review of AKS monitoring architecture proposals from Azure Monitor perspective covering feasibility, caveats, and cost optimization.