mdcraft.ai Phase 4 — Workbench Structure Redesign Concept#

Objective#

Make workbench the premium execution layer: fast for simple tasks, deep for advanced quality control.

Product role of workbench#

• primary environment for conversion execution
• place where quality differentiation is felt
• retention and monetization engine after first success

Workbench layout concept#

Top bar#

• mode switch: Markdown -> PDF / PDF -> Markdown (Beta)
• current file name and status
• export actions

Main canvas (two-column)#

Left: input and editing

• upload/paste controls
• markdown editor
• reverse extraction editor (in beta mode)

Right: output and controls

• live preview
• theme/layout controls
• risk scan and quick fixes (beta mode)

Bottom utility strip (optional)#

• warnings/errors
• processing state
• contextual upgrade hints

Information hierarchy by complexity#

Level 1 (always visible)#

• upload/paste
• preview
• export

Level 2 (easy controls)#

• theme preset
• paper size
• spacing density
• toc/page number toggles

Level 3 (advanced controls, expandable)#

• branding and style overrides
• reusable presets
• batch/automation entry points (future)

Forward conversion journey#

1. User provides markdown
2. Preview updates live
3. User adjusts essential controls
4. User exports PDF
5. User optionally saves/reuses setup

Design intent:

• confidence and speed without hiding quality controls

Reverse conversion beta journey#

1. User uploads PDF in beta mode
2. System outputs draft markdown + confidence warnings
3. User resolves flagged structures (table/list/code/headings)
4. User exports cleaned markdown

Design intent:

• transparent reliability with guided correction

UX components to standardize#

• mode switch chip group
• unified upload card
• editor panel shell
• preview viewport shell
• warning/risk cards
• quick-fix actions list
• export action group
• empty/loading/error/success states

State model requirements#

Workbench should explicitly handle:

• empty input
• parsing/rendering in progress
• successful preview render
• export in progress
• recoverable export failure
• reverse beta warning-heavy outputs

Monetization-ready structural hooks#

• reserve space for usage meter in top bar
• contextual paywall moments:
  • after repeated exports
  • when premium controls are clicked
  • when batch/branding features are requested

No aggressive blocking before first successful conversion.

Accessibility and quality requirements#

• keyboard-first navigation for primary controls
• visible focus states and clear status messaging
• readable contrast and spacing at all density levels
• stable layout under long documents and wide tables/code blocks

Workbench concept acceptance criteria#

1. First-time users can complete a forward conversion without confusion.
2. Power users can reach advanced controls without cluttering default view.
3. Reverse beta communicates confidence and required review clearly.
4. Workbench structure supports future plan-gated features without redesign.

Implementation status#

Iteration update (2026-03-10)#

• studio framing is now used in user-facing labels and CTAs
• workbench entry from homepage quick-start is live and mode-aware
• studio access banner now clarifies free-vs-pro model expectations