Community Help – Advanced Operations Pack
This document completes the Community Help system by defining three advanced operational layers:
1. Contributor Playbooks
2. CMS / Odoo Website Implementation Checklist
3. Service Packaging Informed by Search Intelligence
Together, these sections ensure Community Help remains scalable, controlled, and commercially aligned as BUSATX grows.
SECTION 1: Contributor Playbooks
Purpose
Contributor Playbooks ensure that anyone creating Community Help content—internal staff or approved partners—produces material that is consistent, compliant, and publishable without rework.
Who This Applies To
- Internal BUSATX staff
- Technical contributors
- Approved partners or contractors
Anyone writing Community Help content must follow this playbook.
Contributor Workflow
1. Identify a valid help topic based on:
- Repeated client questions
- Search intelligence
- Known Odoo limitations
2. Confirm the topic fits Community Help boundaries
3. Draft content using the required article structure
4. Apply approved escalation language (if applicable)
5. Submit for review against publishing rules
Mandatory Article Checklist
Before submission, every article must confirm:
- Correct section: Forum → Community Help
- Approved category only
- No internal system names
- No sales or CTA language
- Required article structure followed
- Escalation language matches approved library
Articles failing any item must be revised.
Common Contributor Mistakes
- Writing marketing-style content
- Including step-by-step proprietary workflows
- Referencing internal tools or systems
- Over-explaining custom solutions
Community Help explains *concepts and behavior*, not implementations.
Authority
Editors have final authority. Content that does not comply is rejected, not patched.
SECTION 2: CMS / Odoo Website Implementation Checklist
Purpose
This checklist ensures Community Help content is implemented in the CMS or Odoo Website **without polluting navigation, headers, or menus**.
Global CMS Rules
- Community Help content must never generate header links
- Community Help content must never appear in dropdowns
- Categories must not be exposed as menus
If a CMS setting violates these rules, it must be disabled.
Required CMS Settings (Per Article)
- Section: Forum
- Subsection: Community Help
- Menu placement: None
- Featured in header: Disabled
- Sitemap inclusion: Enabled
- Search indexing: Enabled
Category Configuration
- Categories are metadata only
- Categories must not auto-generate pages unless filtered views are required
- Category URLs must remain under /forum/community-help/
URL & SEO Validation
- URL follows approved structure
- No internal naming conventions
- Slug matches article title intent
Pre-Publish Validation
Before publishing:
- Confirm no new menu items were created
- Confirm header navigation unchanged
- Confirm article is discoverable via search
Ongoing Safeguards
- Restrict menu-edit permissions
- Periodically audit navigation
- Lock Community Help templates
SECTION 3: Service Packaging Informed by Search Data
Purpose
This section defines how Community Help analytics are translated into **formal BUSATX service offerings**, without exposing sales logic in public help content.
Input Signals
Use the following signals:
- High-frequency search terms
- Zero-result searches
- Repeated navigation loops
- Long time-on-page on limitation-heavy articles
These signals represent unmet or advanced needs.
Service Identification Process
1. Group signals by theme
2. Confirm the theme represents a recurring business problem
3. Validate that the problem cannot be solved via standard configuration alone
4. Define a service offering internally
Community Help content remains unchanged.
Example Mappings (Internal Only)
- Estimating searches → Estimating System Design
- Job costing searches → Job Costing Architecture Review
- Performance searches → Performance Audit & Optimization
- Security searches → Security & Governance Review
Packaging Rules
- Services must be named clearly and conservatively
- Avoid productized-sounding names in public
- Define scope, exclusions, and prerequisites internally
Separation of Concerns
- Community Help educates
- Sales materials convert
- Analytics inform strategy
These functions must remain separate.
Review Cadence
- Quarterly review of analytics-to-service alignment
- Annual retirement or consolidation of low-demand services
Final Authority Statement
This Advanced Operations Pack completes the Community Help system.
All Community Help content, contributors, analytics usage, and service alignment must comply with the rules defined herein.
*End of Community Help – Advanced Operations Pack*
<p>Related: <a href="/forum/community-help-3/community-help-154">Community Help</a>, <a href="/forum/community-help-3/community-help-publishing-contribution-rules-155">Community Help – Publishing & Contribution Rules</a>.</p>