mirror of
https://github.com/sotashimozono/obsidian-remote-ssh.git
synced 2026-07-22 06:52:07 +00:00
d71bf7cdf3
Per the new Head.tsx dispatch, declare structured-data type per page
via `schema:` frontmatter:
TechArticle (4 pages):
- architecture/shadow-vault (already had frontmatter)
- architecture/release-pipeline (already had frontmatter)
- architecture/collab (added frontmatter from scratch)
- architecture/perf (added frontmatter from scratch)
Article (10 pages — 9 EN cookbook recipes + 1 JA twin):
- cookbook/raspberry-pi-vault (en + ja)
- cookbook/ssh-keygen
- cookbook/share-via-tailscale
- cookbook/systemd-managed-daemon
- cookbook/backup-restore
- cookbook/host-migration
- cookbook/hardware-key
- cookbook/reverse-proxy
- cookbook/multi-vault
`architecture/collab.md` and `architecture/perf.md` previously had no
frontmatter at all — the H1 was their de-facto title. Adding minimal
frontmatter (title matches the H1 verbatim, plus tags + schema +
description). Slug and rendered title unchanged.
The cookbook landing (cookbook/index.md) and architecture landing
(architecture/index.md) keep their default non-schema state — they
are navigational pages, not articles.
Once the docs site rebuilds, Google's Rich Results Test should
recognise these as valid Article / TechArticle entities.
|
||
|---|---|---|
| .. | ||
| cookbook | ||
| getting-started | ||
| migration | ||
| operations | ||
| security | ||
| comparison.md | ||
| faq.md | ||
| index.md | ||