MotirBuilding in public
MOTIR · moooon
onMotir
You’re viewing a public project. Anyone can view it — no account needed. Sign in to submit, upvote, or comment on requests.View-only — you can’t edit work items
MOTIR-1144

8.3.4 Content — motir-marketing landing copy + positioning (idea · import-existing · tracker-first audiences)

Done
Description

Type: content · Executor: coding_agent · Repo: motir-marketing. The targetRepo pin is deliberately NOT set yet — motir-marketing is not among the workspace's connected repositories (gh repo list moooon-B-V, 2026-08-26), and an unknown pin fails the whole approve in resolveAuthoredTargetRepoInProject. Pin it once MOTIR-1455 provisions and connects the repo.

▶ SWEPT 2026-08-26. Like its sibling MOTIR-1143, this card's title was corrected by the 2026-06-30 replan and its body was not. It still delivered "the root generateMetadata title/description" and "locale strings in messages/en.json" — both motir-core paths, for copy that now ships in motir-marketing, whose i18n arrangement is that repo's own (established by MOTIR-1152, which scaffolds it). And it addressed a single hero CTA, where the landing now carries three doors.

What to write

Every word on the motir.co landing, laid out by MOTIR-1143, for three audiences rather than one:

audiencethe door they readwhat the copy must do
has an idea, no codethe idea hero (primary)invite them to type the thing they want built, and say what happens next (Motir drafts the plan, then agents take over the work)
has a codebase or a tracker"Import an existing project" (secondary)name the sources concretely — a repo, Jira, Linear — so the reader recognises themselves
wants the tracker, no AI"Start free" (tertiary)make it plain that Motir is a complete project-management tool on its own, and that AI planning is something you turn to, not something you must pass through

Positioning is fixed and non-negotiable: the THREE pillars. Motir is the "AI planning, project-management and agent orchestration platform". Use all three; dropping agent orchestration is incomplete. And the agent takes over the work — design, decisions, content, tests, code — so never call it a "coding agent" in customer-facing copy.

Terminology is locked: "work item", never "issue". Open-core is a positioning asset, not a footnote — say that the project-management core is open source.

This is the COPY artifact MOTIR-1143 lays out and MOTIR-1152 wires. It relates to 8.6 (Go-to-market), which owns the canonical positioning for the first audience; if 8.6 is not final, draft to the three-pillar framing above and flag the dependency in the deliverable.

Acceptance criteria

  • Hero headline + lede, the idea box's label / placeholder / submit CTA, and the two secondary door rows' labels and one-line descriptions — one set per audience in the table above, none of the three left to the implementer.
  • Feature-block copy for all three pillars (AI planning · project management · agent orchestration), stated in that framing; the open-core line; footer / legal microcopy.
  • The idea box's non-happy states are written, not just the happy one: submitting, and the message shown when the cross-origin draft POST fails.
  • Root SEO <title> + meta description copy supplied for motir.co.
  • Terminology compliant — "work item" not "issue"; the agent "takes over the work", never "coding agent"; the three-pillar tagline appears intact.
  • Delivered as the en-locale strings in motir-marketing, in whatever catalogue arrangement MOTIR-1455's scaffold establishes, with the en baseline byte-identical for later i18n threading. No motir-core file is touched.
  • Cross-reference to 8.6 positioning noted, and explicitly flagged if 8.6 is not yet final.

Context refs

  • MOTIR-1143 — the layout this copy fills · MOTIR-1152 — the build that wires these strings into the page (downstream of this card, not a prerequisite)
  • MOTIR-1455 — provisions the repo (blocked on the ADR MOTIR-2854)
  • MOTIR-655 — the tracker first-run the "Start free" copy promises
  • EVIDENCE, not deliverables (they live in motir-core): messages/en.json — the voice and the locked glossary to match · design/onboarding-entrance/design-notes.md — the entrance copy the hero must read continuously with