# Factronics USA — Project Instructions

## Must-Read Rules
- `01_knowledge_base/rules/Factronics_Linx_Naming_Rule.md` — Every CTA must name a real Linx product. Read before writing any marketing content.
- `01_knowledge_base/rules/Factronics_Compliance_Language.md` — Approved compliance language for marketing copy.
- `01_knowledge_base/rules/Factronics_Event_Email_Blast_Rule.md`: every event, expo, trade show, or booth email blast must use the value-first, gated-form pattern. Read before writing any event email or promo.

## Knowledgebase
- `01_knowledge_base/00-07.*` — Numbered research docs (buyer psychology, channel acquisition, messaging blocks)
- `01_knowledge_base/research-and-notes/` — Coordenadas-authored analysis and documentation: playbook, AI visibility report, email sequences, case studies, landing page strategy, competitor analyses, Linx product summaries, raw marketing brain text dump. Rule of thumb: if we wrote/synthesized it, it's here. The event and expo email playbook lives at `Factronics_Event_Expo_Email_Playbook.md`. The outbound call cadence email templates live at `Factronics_Cold_Call_Cadence_Email_Templates.md`, with the token reference and the per-rep meeting links.
- `01_knowledge_base/source_materials/` — Raw third-party material we did not create: OEM product PDFs, supplier research, supplier product images (organized per-supplier under `supplier-images/`, including Linx — no supplier's images should sit loose at the root level).
- `02_brand_kit/logos/` — Logo files (SVG + PNG), favicon
- `02_brand_kit/partner_logos/` — Supplier/partner logo files
- `02_brand_kit/product_visuals/` — Solution category thumbnails
- `02_brand_kit/design_sheets/` — Empty, pending `SOP_Brand_Diagnostic.md`
- `02_brand_kit/Factronics_brand_guide.html` — Full brand guide
- `02_brand_kit/Factronics_Brand_Kit.md` — Brand Kit (colors, fonts, logo specs) — canonical copy; do not recreate a duplicate in `01_knowledge_base/`
- `Factronics_marketing_brain.html` — Full Marketing Brain interactive document
- `Factronics_MasterStrategyDoc.html` — Master Strategy Document (if exists)
- `04_hl_subaccount_config/` — GoHighLevel subaccount setup output (`hl-subaccount-setup` skill)

## Website Project
- `factronicsusa.com` is a **WordPress** site (Astra theme, Rank Math SEO, LiteSpeed), not a
  static/React build. The blog lives at `/blog-events/`. Posts are published from WP admin.
- Publishing is a manual WP admin step. Hosting is cPanel (`rs5-or`) with Coordenadas access.
- The site exposes a WP REST/MCP endpoint (`/wp-json/mcp`, Elementor MCP composer), but it
  requires an application password. No factronics app password is configured in this repo.
- There is no local site project for this brand. Do not look for a Vite/React app. Content
  work (blog posts, prompts, briefs) is authored in this brand folder and handed off for
  publishing. See `05_projects/VACC_Backlink_Sprint/PUBLISH_PACKAGE.md` for the publish
  handoff pattern.

## Brand
- Colors: Blue #0D70CC, Navy #00337A, Lime Green #C7D759
- Fonts: Inter (primary), Sarala (secondary)
- No em dashes or en dashes in copy — use periods, commas, or "and"
- Hormozi-style direct response copy