Skip to main content

Overview

Purpose​

ID86 is a search-first documentation hub. The homepage gets visitors to a relevant reference quickly through a prominent search bar and topic cards. WordPress publishes and manages the references; GitHub Markdown is the pre-publication and archival source, while WordPress Gutenberg is authoritative for published content.

The experience is built on two non-negotiable commitments: the UI/UX must be outstanding — simple, modern, and user-oriented — and the site must be fast and genuinely useful.

Vision​

Make trustworthy, practical technical references easy to find and fast to apply. ID86 helps a visitor move from a concrete question to a usable answer without forcing them through long, generic tutorials.

The interface should feel outstanding and effortless: simple, modern, and deliberately user-oriented. Every screen is designed around the visitor — calm, clean, and free of noise — so nothing stands between them and a usable answer.

Mission​

  • Publish concise references for Code, DevOps, AI, and Security.
  • Make search the primary path to content.
  • Keep each page actionable: explain the task, show the command or pattern, and avoid unnecessary prose.
  • Deliver an outstanding, simple, and modern UI that is user-oriented at every step.
  • Maintain a calm, accessible interface that works equally well on desktop and mobile.
  • Use a simple, lightweight tech stack that stays fast and maintainable.
  • Keep the site fast and useful: quick load times, minimal friction, and answers worth keeping.

SCS integration (SEO Content Systems)​

ID86.net is also an SCS-registered site (site_id: id86, prefix ID, host GC-US-M10). Content authored through SCS is stored as a single Markdown file with a brief half (<!-- scs:brief -->) and an article half (<!-- scs:article -->); only the article half is published. SCS front matter is a superset of the ID86 contract — the standard ID86 fields (title, description, category, tags, content_type, status, date, slug) remain the publication contract, and the nested scs: block is consumed by SCS. ACF fields (content_type hub/pillar/cluster/supporting, primary_keyword, semantic_tags, parent post IDs) and the portable wpw_* review gate are provided by the wpstrategist-seo-architecture and wpstrategist-review-gate plugins.

See Content Sync Pipeline → SCS-authored content and Markdown Authoring → SCS integration.

Guide Sections​

SectionFolderContents
2. Design System02-design-systemBrand System, CSS System, Hero Section, Topic Cards & Reference Sheets, Subscribe Bar, Search Command Palette, Footer, Templates, Recommendations Page, Task Checklists
3. Content03-contentContent & Audience, Content Model, Article Body Elements, Meilisearch Search, Content Register, Content Types
4. WP Ops04-wp-opsProduction Stack, Cache & Access, Server Infrastructure, LiteSpeed Cache CLI, BetterLinks & Affiliate Links, Content Sync Pipeline, Code Block Rendering, Development Workflow
5. Development05-developmentChild Theme, Theme Deployment, GeneratePress Elements, Navigation & Menus, Dark Mode
6. Conversion06-conversionSubscription Workflow, Storage & Settings, Contact Form, Monetization & Disclosures
7. SEO & Analytics07-seo-analyticsSearch Engine Indexing, GSC & GA4 Setup, SEO Metadata Automation, Glossary SEO
8. Cheatsheet08-cheatsheetScripts & Commands, Markdown Authoring, WP-CLI