Last updated: 2026-03-08. Structure follows: wp-marketing-docs-best-practices.md (15-section sequence).
HASMaster Plugin is the operating layer for the HASMaster environment: it adds the structured content model (custom post types + taxonomies), the guided journey engine, and the admin tools that keep everything consistent over time. For the presentation layer (styling, layouts, directory UX), see: HASMaster Block Theme.
Section 1: Navigation Bar
Links: Features | How It Works | Pricing | Docs | Support Primary CTA: [Get HASMaster Plugin] Behavior: Sticky on scroll
Section 2: Hero
Headline:
The Schema + Journey Engine for Home Automation Knowledge
Subheadline:
Turn “I want to automate X” into a structured scenario with constraints, components, a confirmed recommendation, and setup-ready documentation.
Primary CTA: [Get the Plugin] Secondary CTA: [View Live Demo]
Hero visual: [Screenshot: journey step page with progress + confirmed outcomes]
Trust strip (below hero):
- Purpose-built content types for home automation (not generic blogging)
- Taxonomy spine that stays consistent as your content grows
- Journey orchestration that captures decisions and produces a plan
- Optional AI add-on for stage-aware assistance (BYOK)
Section 3: Social Proof Strip
[PLACEHOLDER — collect after launch]
- Home Assistant-first content model (documentation + planning workflows)
- Tested on WordPress 6.9 / PHP 8.3
- Pairs with HASMaster Theme for best front-end directory UX
Section 4: Problem / Pain Statement
Headline: WordPress can publish home automation content. It cannot manage home automation knowledge.
Body: A device is not just a post. A use case is not just a tag. Real automation work depends on compatibility, protocols, platform constraints, and the setup path you will actually take.
Most sites end up as scattered posts, inconsistent categories, and one-off pages that don't connect to each other. Even worse, when you rename a category or adjust your model, the whole system drifts out of sync.
HASMaster Plugin solves the operating layer: it gives you a stable data model, a taxonomy spine, and a guided journey engine that captures decisions and produces a consistent, repeatable outcome.
Section 5: Solution Overview / Core Value Proposition
Headline: One plugin that turns decisions into an implementation plan.
4 pillars (icon + headline + 1 sentence each):
| Icon | Pillar | What it does | |——|——–|————–| | [Schema] | Purpose-built schema | Registers the core content types and taxonomies for devices, use cases, guides, software, and infrastructure | | [Journey] | Journey orchestration | Guides users stage-by-stage, records inputs, and keeps progress coherent across steps | | [Scenario] | Scenario capture | Stores what was required vs. what the user already has, plus the confirmed recommendation you will actually implement | | [Tools] | Day-2 operations | Admin tooling for taxonomy management, pipeline runs, validation, and cleanup tasks |
Looking for the presentation layer? The plugin is the engine; the theme is the interface. See: HASMaster Block Theme.
Section 6: Feature Highlights
Feature 1: Content Model for Home Automation Purpose-built content types and a taxonomy spine designed for compatibility, setup complexity, and real-world constraints. Not a blog category system pretending to be a knowledge base.
Feature 2: Journey Stages that Produce a Plan Users move through stages like Inspired Design → Define Constraints → Select Components → Set Up. Each stage has a clear objective, captures structured inputs, and advances progress only when confirmed.
Feature 3: “Owned vs Required” Inventory Capture The journey captures what the user already has (and wants to keep) vs. what must be added. Recommendations exclude already-owned components by default.
Feature 4: Confirmed Recommendation Output After Select Components, the system produces a plain-language summary of the recommended devices, software, and infrastructure, with checkboxes for user confirmation. That confirmed bundle becomes the baseline for Set Up.
Feature 5: Admin Tools and Pipelines Operational tools for keeping taxonomy and content consistent as the library grows, plus pipeline-backed ingestion/update workflows for devices, guides, and references.
Feature 6: Optional AI Add-On (BYOK) Stage-aware assistance that uses the scenario context to guide users, without turning your site into an ungrounded chat experience.
Section 7: How It Works
Step 1: Build a structured library (devices, use cases, guides) using the HASMaster content model.
Step 2: Run a guided journey for a single use case scenario and capture constraints, owned inventory, and preferences.
Step 3: Synthesize a recommendation: what is required to solve the problem, what is already owned, and what the user should buy or configure.
Step 4: Confirm the recommendation with the user (checkbox validation + notes).
Step 5: Use the confirmed recommendation as the baseline for Set Up and documentation generation.
Section 8: What the Plugin Does (and Does Not) Do
It does:
- Model home automation knowledge as structured content (CPTs + taxonomies)
- Drive stage-based journeys with progress tracking and stored outcomes
- Store scenario history: inputs, decisions, confirmed recommendations
- Provide admin tools for ongoing maintenance and content consistency
It does not:
- Control your smart home directly (it documents and plans; Home Assistant executes)
- Force a specific theme (but the HASMaster Theme is optimized for the model)
Section 9: Technical Specs (for Builders)
Content types: Purpose-built post types for devices, use cases, guides, software, and infrastructure.
Taxonomies: A taxonomy spine for organizing by domain, protocol, integrations, setup difficulty, compatibility, and more.
Blocks (optional):
- Taxonomy and directory navigation blocks
- Journey navigation/progress blocks
- AI assistant blocks (if the add-on is installed)
REST API:
- Content types and taxonomies exposed via WordPress REST API (for headless and internal tooling)
- Optional AI proxy endpoint (add-on):
hasmaster/ai-assistant/v1/chat
Developer hooks:
- Filters/actions for extending taxonomies, journey stages, and recommendation rendering
Section 10: Testimonials / Reviews
[PLACEHOLDER — collect after launch]
Section 11: AI Prompt Governance (Reliability by Design)
Headline: Prompt quality is engineered, not improvised.
Body: HASMaster treats prompts as a governed artifact: stage templates, schema contracts, pre-release checks, and runtime signals. This keeps recommendations consistent as your taxonomy evolves.
Governance flow:
flowchart LR D["Design Decisions"] --> M["Decision-to-Prompt Matrix"] M --> S["Prompt Standard + Stage Templates"] S --> A["Prompt Authoring"] A --> L["Prompt Lint Checks"] L --> E["Scenario Evaluation Suite"] E --> G["Release Gate"] G --> R["Runtime Deployment"] R --> T["Telemetry + Policy Signals"] T --> V["Review + Refinement"] V --> D
What this delivers:
- More consistent stage behavior and fewer regressions
- Better grounding in captured scenario context (owned vs. required)
- A prompt process you can audit, not trial-and-error tuning
Section 12: Pricing
Proposed pricing — to review and confirm before launch.
| Product | Price | Notes | |———|——-|——-| | HASMaster Plugin (core) | [TBD] | Includes 12 months updates | | AI Assistant Add-On | [TBD] | One-time, BYOK (requires an orchestrator endpoint) | | Optional: Theme bundle | [TBD] | See theme details: HASMaster Block Theme |
AI Add-On model: BYOK (Bring Your Own Key) is the default. Your site stays self-hosted; you choose your endpoint (local or hosted) and provide credentials in settings.
Section 13: FAQ
Q: Do I need the HASMaster Theme to use the plugin? A: No. The plugin provides the schema and engine and works with any theme. The HASMaster Theme is optimized to present the model (directories, filters, journey UX).
Q: Does HASMaster control my devices? A: No. HASMaster helps you design, document, and plan. Home Assistant (or your platform of choice) runs the automations.
Q: What is a “scenario”? A: One complete walkthrough of a specific use case (constraints, owned inventory, recommendation, and setup baseline) stored so you can revisit it later.
Q: What WordPress and PHP versions are required? A: WordPress 6.6+, PHP 8.1+. Tested on WordPress 6.9 / PHP 8.3.
Q: Is my data stored on your servers? A: No. HASMaster is self-hosted. Content and scenario history remain in your WordPress database.
Section 14: Final CTA
Headline: Stop rebuilding infrastructure. Start capturing real automation decisions.
Body: HASMaster Plugin gives you the schema, journeys, and scenario history needed to turn home automation into something you can manage over time.
Primary CTA: [Get the Plugin] Secondary CTA: [Read the Docs]
Section 15: Footer
Standard footer with:
- Logo + tagline: "Life Automated."
- Links: Features | Demo | Pricing | Docs | Blog | About
- Social: YouTube (HASMaster_1000) | GitHub
- Legal: © 2026 HASMaster