mdmdcraft.aiSimple markdown conversion
All docsLog inSign Up
HomeAll docs

Documentation

Design phase 1: IA and user flows

mdcraft.ai Phase 1 — Information Architecture and User Flows#

Objective#

Define a clear site structure and end-to-end flows for acquisition, activation, and conversion.

Information architecture#

/
|- Hero (promise + quick start)
|- Product workflows
|- Quality proof
|- Templates/style proof
|- Pricing preview
|- Privacy and docs
`- Footer

/workbench
|- Conversion mode (Markdown->PDF | PDF->Markdown beta)
|- Input area (upload/paste/editor)
|- Live preview/output panel
|- Controls (theme, paper, spacing, toc/header-footer)
|- Risk scan (reverse beta)
|- Export/download actions
`- Upgrade nudges (contextual)

/pricing (or pricing section first, dedicated page later)
|- Plan comparison
|- Feature gates
|- FAQ
`- Upgrade CTA

/docs/*
`- trust and technical proof content
  • Workbench
  • Product
  • Pricing
  • Docs

Primary CTA in header:

  • Start converting (homepage)
  • Open workbench (docs/internal pages)

Contextual navigation#

Within workbench:

  • mode switch
  • section anchors/tabs: Input, Preview, Controls, Export

User flows#

Flow A: First-time visitor -> first export (primary)#

  1. Land on homepage
  2. See clear promise + quick-start module above fold
  3. Upload .md or paste markdown
  4. Enter workbench with preloaded input
  5. Review live preview
  6. Export PDF
  7. See post-export next step (Save preset / Try Pro)

Goal:

  • minimize time to first successful export

Flow B: Returning/power user -> repeat export#

  1. Land on homepage or direct /workbench
  2. Choose mode immediately
  3. Reuse known controls/template
  4. Export quickly

Goal:

  • low-friction repeated behavior and retention

Flow C: Reverse conversion beta with review#

  1. Enter PDF -> Markdown (Beta) mode
  2. Upload text-first PDF
  3. Receive extracted markdown + risk scan
  4. Resolve flagged issues in editor
  5. Export markdown

Goal:

  • preserve trust with honest quality signaling

Flow D: Free -> paid expansion#

  1. User hits meaningful limit (usage, premium style, batch, branding)
  2. Sees value-contextual upgrade prompt
  3. Opens pricing details with plan fit guidance
  4. Upgrades

Goal:

  • convert after value proof, not before

Page role definitions#

Homepage role#

  • communicates category and quality
  • creates first action (upload/paste)
  • channels advanced work to workbench

Workbench role#

  • performs the core job
  • demonstrates product depth and reliability
  • drives repeat usage and paid conversion

Docs role#

  • credibility, transparency, and technical trust

Event instrumentation plan (for later implementation)#

  • homepage_quickstart_viewed
  • homepage_upload_started
  • homepage_paste_started
  • workbench_loaded_with_input
  • preview_rendered
  • export_pdf_clicked
  • export_pdf_success
  • reverse_mode_entered
  • reverse_risk_warning_seen
  • reverse_export_success
  • upgrade_prompt_viewed
  • upgrade_clicked

IA acceptance criteria#

  1. New users can identify start action in <= 5 seconds.
  2. Users can move from homepage to first preview in <= 2 interactions.
  3. Workbench clearly separates forward conversion and reverse beta.
  4. Pricing/upgrade path is visible but not intrusive before first value moment.