Arkanza Marketing Knowledge Base

The single source of truth for how Arkanza’s marketing division thinks, decides, and operates.

What this is

A structured, Obsidian-friendly knowledge base built around eight core knowledge domains (01–08), plus a dedicated Partnerships domain (11 · affiliate & KOL, added in Phase 4 as a cross-cutting brand × channel motion) and the Roles & Operations overlay (09 · per-position operating systems, 10 · Tools). Brand and marketplace are handled as tags/metadata, not nested folders — this keeps the structure shallow and stops the brand × marketplace matrix from exploding into dozens of empty folders.

Two systems, one line between them

  • Custom App (Marketing HQ) = system of record. Live, operational, queryable data: SKUs, campaign status, KPI numbers, task assignments.
  • This KB / Obsidian = system of understanding. Durable knowledge: why we do things, playbooks, brand logic, post-mortems, strategy.

Rule of thumb: if it changes weekly and you’d want to filter or sort it, it belongs in the App. If it explains, teaches, or decides, it belongs here.

How to navigate

Start at 00_MASTER_MOC (the master Map of Content). Every domain folder has its own _MOC page that links to the notes inside it.

The one thing that keeps this alive

A KB doesn’t fail because the folder tree was wrong — it fails because nobody updates it. Every domain has a named owner and a review cadence. See KB_Governance.

Folder map

#DomainOwner (role)
01Company & StrategyMarketing Lead / Manager
02Brand GuidelinesBrand Strategist / Creative Leader
03Products & CatalogueMarketplace Ops
04Channels & MarketplacesChannel Specialists
05Playbooks & SOPsMarketing Lead
06CampaignsMarketing Manager / Lead
07Performance & DataMarketing Lead (+ future Data role)
08Team & PeopleMarketing Lead
11Partnerships (Affiliate & KOL)Marketplace & Affiliate Specialist + KOL
99Meta (conventions, templates, schema)Marketing Lead

Language note: structural/meta pages are in English; brand- and team-facing content pages (02, 05, campaign briefs) should be authored in Bahasa Indonesia.