matrix-spec/layouts/_partials/spec-content.html

{{- /* Shared render for spec pages: title, optional description, endpoints list, body, and last-mod info. */ -}}
<div class="td-content">
  <h1>{{ .Title }}</h1>
  {{ with .Params.description }}<p class="page-description">{{ . | markdownify }}</p>{{ end }}

  {{ partial "endpoints-toc.html" . }}

  {{ .Content }}

  {{ partial "page-meta-lastmod.html" . }}
</div>
Place the endpoints list just under the description of each API We needed to override Docsy's default page renderers to show it. Because the Client-Server API uses a different render chain than the other endpoint pages, we have to override two of Docsy's pages (`content.html` and `single.html`). In order to reduce duplication, we then put the shared content into a `spec-content.html` partial. 2025-12-05 16:46:03 +01:00			`{{- /* Shared render for spec pages: title, optional description, endpoints list, body, and last-mod info. */ -}}`
			`<div class="td-content">`
			`<h1>{{ .Title }}</h1>`
Move each spec's intro above the endpoints list This just looks visually nicer. You have an introduction paragraph, then the list of endpoints, then the spec. 2025-12-05 16:47:08 +01:00			`{{ with .Params.description }}<p class="page-description">{{ . \| markdownify }}</p>{{ end }}`

Place the endpoints list just under the description of each API We needed to override Docsy's default page renderers to show it. Because the Client-Server API uses a different render chain than the other endpoint pages, we have to override two of Docsy's pages (`content.html` and `single.html`). In order to reduce duplication, we then put the shared content into a `spec-content.html` partial. 2025-12-05 16:46:03 +01:00			`{{ partial "endpoints-toc.html" . }}`

			`{{ .Content }}`

			`{{ partial "page-meta-lastmod.html" . }}`
			`</div>`