Перейти к содержимому
Community226

Promotional Content

Это содержимое пока не доступно на вашем языке.

Campaign and promotional material (announcements, launch content, partner co-marketing) follows the same rules as any other media content: character facts from Mascot Book, brand facts from Brand Book, cited not restated.

  • Promotional content may combine institutional Brand voice (for the offer/announcement itself) with character-voiced elements (Sol Mamy reacting to or presenting the promotion) — see Voice & Tone in Media for how to keep the two distinguishable.
  • Any imagery uses canonical or approved-variant mascot appearance.
  • Mascot Book — Costume & Design System’s “Event-specific variants” table covers two promotional/campaign contexts specifically — Business/formal (occasion: partnership announcements; same base palette, unchanged, with a subtle formal accent only) and Travel (occasion: partnership/expansion announcements; not a costume change, a change of environment/location instead). Cite that table for these two contexts rather than improvising a costume/context treatment. That table also lists Special campaign (occasion: ad hoc) as explicitly “not yet defined” — do not fill that row here; it remains a real, disclosed gap in Mascot Book, not this book’s to resolve.

Beyond the two promotional-relevant rows cited above, no dedicated promotional-content copy templates or campaign-format guidance (e.g. offer structure, CTA conventions) exist yet at the brand level. The entire Event-specific variants table this cites is itself still “proposed, not yet owner-confirmed” per Mascot Book’s own heading — treat these as working guidance, not settled canon.

  • Do not let promotional urgency justify an off-model mascot depiction (one deviating from her canonical appearance — see Mascot Book — Visual Identity) or an invented brand claim.

Part of the SOLMEME Brand Documentation System. Content status (Canonical/Proposed/Open/etc.) is this book’s own axis; ownership/rights are separate — see OWNERSHIP_AUTHORITY.md at the documentation system’s root.