We (OpenTelemetry Docs Team) want to implement a policy for blogs, that that blog posts, in contrast do doc pages, are fixed in time -- they rot (quoting @chalin here via open-telemetry/opentelemetry.io#3493). Kubernetes has implemented such a feature in their blog already, see https://kubernetes.io/blog/2020/06/30/sig-windows-spotlight-2020/ for example (there is a box at the top stating This article is more than one year old. Older articles may contain outdated content. Check that the information in the page has not become incorrect since its publication.)

Before copying the docsy blog base template into our site layout (and with that lose potential future changes without manually updating), I was wondering if this is a feature that might be worthwile to be added to docsy?

Here's how it looks for kubernetes/website: https://github.com/kubernetes/website/blob/d0cf73f310eedb198203a6109fd8accfac60e954/layouts/blog/baseof.html#L34

Tasks

• Base support:
  • [feat] Add base support of td-content-after-header hook #2192
  • Add link def to CHANGELOG and clean up whitespace #2193
• TBC: a template specific for outdated blog posts, but my feeling is that I want to experiment a bit more with options before Docsy considers settling on a proposal (if at all).