Docs

Website Strategy

Public positioning, audience, route model, and product-category strategy for Flowvec.

Source
docs/website-strategy.md
Status
public-safe curated extract

Flowvec Website Strategy

Flowvec is the public product front door for AI-assisted workflow engineering. The site should make the category legible, prove the current NiFi surface, and show Azure and Workato as honest preview Flow Vectors.

Core Positioning

Flowvec helps teams build, understand, and replatform integrations without hiding business rules inside unbounded generated code.

Position Website language
Product category The development layer for AI-assisted workflow engineering.
Business value Build and review workflow behavior before it becomes operationally important.
Platform optionality Keep delivering on a proven workflow foundation while the platform landscape changes.
Replatforming Extract graph topology, schemas, mappings, rules, dependencies, and runtime evidence before choosing what to preserve or rebuild.

What The Site Must Do

  1. Explain why workflow-engine development needs engine-aware tooling.
  2. Show concrete proof through the current NiFi demo.
  3. Present Azure and Workato as emerging preview Flow Vectors.
  4. Make replatforming and platform optionality first-class stories.
  5. Provide a catalogue structure that can grow beyond NiFi, Azure, and Workato.
  6. Keep hosted Managed NiFi separate from Flow Vector tooling.

Public Route Model

/                       homepage and Vector Path story
/flow-vectors/          product catalogue and maturity matrix
/demo/                  live and preview demo entry point
/design-guides/         engine-aware design guidance
/use-cases/             buyer and reviewer scenarios
/docs/                  public docs hub
/contact/               commercial and technical discovery

The public site should stay environment-neutral. Public HTML, metadata, docs, and bootstrap payloads must not expose local hosts, ports, container names, absolute machine paths, private identifiers, or internal upstream origins.

Audience Priorities

Audience What they need
Platform engineering Confidence that Flowvec can wrap current workflow engines without forcing immediate replacement.
Automation CoE Guardrails, reusable examples, review workflows, and governance language.
AI and agent teams Safe tool surfaces for inspecting, authoring, validating, and operating workflows.
Business reviewers Schema, mapping, rule, validation, and evidence views that do not require reading hidden code.
Migration leads Evidence that reduces the risk of replatforming an existing workflow estate.