Purpose: Define a page concept through conversation, create visualization method based on need
This workflow activates when: User needs to define a page concept but doesn't have a visualization yet.
Goal: Define what the page IS, then choose how to visualize it.
Philosophy: The page (concept) comes first. Visualization (method) follows.
What is this page about?
Tell me in your own words:
Describe the page concept:
Store page_concept
How would you like to visualize this page?
[A] I'll draw a sketch (physical/digital) and upload it [B] Let's describe it verbally - I'll specify sections through discussion [C] Create a simple ASCII layout together [D] It's similar to another page I can reference [E] Generate HTML prototype - I'll screenshot it for documentation
Choice:
Store visualization_method
Based on user choice, load the appropriate flow:
| Choice | Flow | File |
|---|---|---|
| A | Sketch Path | flow-a-sketch.md |
| B | Verbal Specification | flow-b-verbal.md |
| C | ASCII Layout | flow-c-ascii.md |
| D | Reference Page | flow-d-reference.md |
| E | HTML Prototype | flow-e-html.md |
Load and execute the selected flow substep
The page is the conceptual entity:
The visualization is one representation:
The page comes first. Visualization follows.
Different projects need different approaches:
The workshop adapts to YOUR process.
This workshop creates:
Next workshops use:
Created: December 28, 2025 Purpose: Define page concept, choose visualization method Philosophy: Page first, visualization second Status: Ready for use