Content Model
Documentation Posts
References are standard WordPress post entries distinguished by a meta key:
_id86_content_type = instant-documentation
The child theme filters homepage cards and the Fuse.js search index against this marker. Ordinary blog posts without it are excluded from the documentation experience.
Source Metadata
Each documentation post carries two additional meta keys for sync tracking:
| Key | Purpose | Example |
|---|---|---|
_id86_source_path | Repository-relative Markdown source path | code/git/git-cheat-sheet.md |
_id86_source_hash | SHA-256 content hash for change detection | b5a15644535cd33c42322bed4c8361285c21daf621fddcf297739b0067944aa1 |
Categories
The four topic categories are used consistently across the site:
| Slug | Display Name | Current Post Count |
|---|---|---|
code | Code | 2 |
devops | DevOps | 1 |
english | English | 1 |
seo | SEO | 1 |
Categories determine:
- The hero quick-topic links.
- The niche card section (4 cards, one per category).
- The color accent on each card (via
.id86-code,.id86-devops,.id86-english,.id86-seoCSS classes). - The category archive pages.
Post Views
Each single post view increments post_views_count post meta. This is used by the optional popular-post query via the order_by_views GenerateBlocks class.
Markdown Source Repository
The Markdown source of truth lives at:
/home/rezriz/github/ID86-instant-documentation
Repository: github.com/donnyaw/ID86-instant-documentation
Content is authored in Markdown and synchronized to WordPress. The sync tooling preserves the source path and hash metadata so updates remain idempotent.
Content Templates
Single posts use two GeneratePress Elements:
- #Single Post Title (ID 3663, Page Hero): Breadcrumbs, H1 title, author, date.
- #Single Post Content (ID 1371, Content Template): Featured image, post content, tags, related posts, comments.