npm - whiteport-design-studio - Versions diffs - 0.1.0 → 0.2.0 - Mend

whiteport-design-studio 0.1.0 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1282) hide show

package/src/workflows/2-trigger-mapping/document-generation/steps-c/step-01-generate-hub.md DELETED Viewed

@@ -1,188 +0,0 @@
-# Step 01: Generate 00-trigger-map.md (Hub & Navigation)
-**Goal:** Create the main entry point with Mermaid diagram and on-page summaries
----
-## Purpose
-The hub document serves as:
-1. **Visual entry** - Mermaid diagram at top
-2. **Quick reference** - On-page summaries for all sections
-3. **Navigation menu** - Links to detailed documents
-4. **Strategic overview** - Key transformation and flywheel
----
-## Document Structure
-### 1. Header Section
-```markdown
-# Trigger Map: [Project Name]
-> Visual overview connecting business goals to user psychology
-**Created:** [Date]
-**Author:** [Name] with Saga the Analyst
-**Methodology:** Based on Effect Mapping (Balic & Domingues), adapted for WDS framework
-```
----
-### 2. Mermaid Diagram
-<action>Load mermaid-diagram/instructions.md to generate the diagram</action>
-**Requirements:**
-- Gold highlighting for PRIMARY GOAL (BG0)
-- Light gray professional styling
-- All nodes have proper padding (`<br/>`)
-- Emojis: ✅ for wants, ❌ for fears
-- Exactly 3 drivers per persona
-- Proper connections: BG→PLATFORM→TG→DF
----
-### 3. Summary Section
-**Include:**
-```markdown
-## Summary
-**Primary Target:** [Primary Persona Name] - [one-line transformation]
-**The Flywheel:**
-1. ⭐ **[Primary Goal Title]** (THE ENGINE - [X] months)
-2. 🚀 **[Secondary Goals Summary]** ([Target numbers] - [X] months)
-3. 🌟 **[Tertiary Goals Summary]** ([Benefits for community] - [X] months)
-**Key Transformation:** Transform [persona] from [current state] to [desired state] by [addressing core needs].
-```
----
-### 4. Detailed Documentation (Menu Section)
-**For each section, provide:**
-- Link to document
-- Brief description (1 line)
-- Key bullet points visible on page (3-5 points)
-**Structure:**
-```markdown
-## Detailed Documentation
-### Business Strategy
-**[01-Business-Goals.md](01-Business-Goals.md)** - Vision, objectives, and success metrics
-[Include on-page summary with:]
-- Vision statement (1 sentence)
-- Priority Tiers (3 tiers with key numbers)
----
-### Target Users
-**[02-[Name]-the-[Role].md](02-[Name]-the-[Role].md)** - Primary target persona
-[Include on-page summary with:]
-- Profile (1-2 sentences)
-- Positive Drivers (3 bullets)
-- Negative Drivers (3 bullets)
-- Transformation (1 line)
----
-[Repeat for secondary and tertiary personas]
----
-### Strategic Implications
-**[05-Key-Insights.md](05-Key-Insights.md)** - Design and development priorities
-[Include on-page summary with:]
-- Primary Development Focus (5 key areas)
-- Critical Success Factors (3-5 bullets)
-- Emotional Transformation Goals (3-5 bullets)
-```
----
-### 5. How to Read the Diagram
-```markdown
-## How to Read the Diagram
-The trigger map connects business goals (left) through the platform (center) to target user groups (right) and their driving forces (far right).
-**Priority:**
-- ⭐ **Gold box** = PRIMARY GOAL ([Goal name] - THE ENGINE)
-- 🚀 **Gray boxes** = Supporting goals driven by [primary goal]
-- 🌟 **Gray boxes** = Opportunities created for community members
-**Driving Forces:**
-- ✅ **Green checkmarks** = Positive goals (what users want)
-- ❌ **Red X marks** = Negative goals (what users fear/avoid)
-```
----
-### 6. Footer
-```markdown
----
-_Generated with Whiteport Design Studio framework_
-_Trigger Mapping methodology credits: Effect Mapping by Mijo Balic & Ingrid Domingues (inUse), adapted with negative driving forces_
-```
----
-## On-Page Summary Guidelines
-**Each menu item MUST include:**
-1. **Link with description** - What the document contains
-2. **On-page content** - Key information visible without clicking
-3. **Proper formatting** - Use bold, bullets, clear structure
-**Why on-page summaries?**
-- Users can scan the whole trigger map without clicking
-- Quick reference for key information
-- Navigation menu + content in one place
----
-## Example Implementation
-See example in: `examples/` folder
-**Key features:**
-- ~220-250 lines total
-- Mermaid diagram at top
-- Summary with transformation focus
-- Each persona gets on-page bullets
-- Clean navigation flow
----
-## Output
-<output>✅ Hub document created with diagram and navigation!</output>
-Store as: `00-trigger-map.md` in trigger map folder
----
-## Next Step
-<output>Ready for Step 2: Generate Business Goals Document</output>
-<action>Load and execute: step-02-generate-business-goals.md</action>
-Do NOT skip ahead.

package/src/workflows/2-trigger-mapping/document-generation/steps-c/step-02-generate-business-goals.md DELETED Viewed

@@ -1,231 +0,0 @@
-# Step 02: Generate 01-Business-Goals.md
-**Goal:** Create comprehensive objectives document with vision, SMART goals, and flywheel
----
-## Purpose
-Document the strategic foundation:
-- Vision statement (where we're going)
-- Business objectives (how we measure success)
-- Priority tiers (what matters most)
-- The flywheel (how it all connects)
-- Success metrics alignment (personas → objectives)
----
-## Document Structure
-### 1. Header
-```markdown
-# Business Goals & Objectives
-> Strategic goals and measurable objectives for [Project Name]
-**Document:** Trigger Map - Business Goals
-**Created:** [Date]
-**Status:** COMPLETE
-```
----
-### 2. Vision Statement
-```markdown
-## Vision
-**[Insert vision statement from workshop]**
-[Should be 1-2 sentences describing the ultimate goal/transformation]
-```
----
-### 3. Business Objectives (3 Priority Tiers)
-**Structure with clear hierarchy:**
-```markdown
-## Business Objectives
-### ⭐ PRIMARY GOAL: [Title] (THE ENGINE)
-- **Statement:** [What we're building]
-- **Metric:** [How we measure it]
-- **Target:** [Specific number]
-- **Timeline:** [X months]
-- **Impact:** This drives ALL other objectives - this is the key to expansion
-```
-**Follow with SECONDARY and TERTIARY tiers:**
-```markdown
----
-### 🚀 [SECONDARY GOALS CATEGORY] (Driven by [Primary Goal])
-**Objective 1: [Title]**
-- **Statement:** [What we're achieving]
-- **Metric:** [How we measure]
-- **Target:** [Number]
-- **Timeline:** [X months from launch]
-[Repeat for all secondary objectives: 2, 3, 4...]
----
-### 🌟 [TERTIARY GOALS CATEGORY] (Real-World Benefits for Members)
-**Note:** These are opportunities [Product] creates FOR the community members - [benefit description].
-**Objective X: [Title]**
-- **Statement:** [What members get]
-- **Metric:** [How we measure member success]
-- **Target:** [Number]
-- **Timeline:** [X months]
-- **Benefit to Members:** [Career/personal growth impact]
-[Repeat for all tertiary objectives]
-```
----
-### 4. The Flywheel Section
-**Explain how goals connect:**
-```markdown
-## The Flywheel: How Goals Connect
-**THE ENGINE (Priority #1):**
-- [Primary goal number] [primary goal description]
-- Timeline: [X] months
-- These [users] [action that drives everything]
-- They create the flywheel that drives ALL other objectives
-**[Secondary Category] (Priority #2):**
-- Driven BY the [primary goal achievers]
-- [List key targets with numbers]
-- Timeline: [X] months
-- Focus: [What this tier achieves]
-**[Tertiary Category] (Priority #3):**
-- Real-world benefits FOR community members
-- [List key opportunities]
-- Timeline: [X] months
-- **Key benefit**: [How members' lives improve]
-```
----
-### 5. Success Metrics Alignment
-**Show how personas connect to objectives:**
-```markdown
-## Success Metrics Alignment
-### How Trigger Map Connects to Objectives (Properly Prioritized):
-**⭐ PRIMARY: Creating Awesome [Users] Who Become [Champions] → Achieves:**
-- ✅ **[Number] [champions]** (THE ENGINE - [Persona] becomes one of them naturally)
-- ✅ [Action 1]
-- ✅ [Action 2]
-- ✅ [Natural outcome]
-- **Timeline: [X] months**
-- **This drives ALL other objectives**
-**🚀 SECONDARY: [Champions] Drive [Product] Adoption → Achieves:**
-- ✅ [Objective 1] ([champions] spread the word)
-- ✅ [Objective 2] ([champions] demonstrate value)
-- ✅ [Objective 3] ([champions] create engagement)
-- **Timeline: [X] months**
-**🌟 TERTIARY: [Product] Success Creates Opportunities for Community → Achieves:**
-- ✅ [Opportunity 1] (members [benefit])
-- ✅ [Opportunity 2] (members [benefit])
-- ✅ [Opportunity 3] (members [benefit])
-- **Timeline: [X] months**
-- **Benefit: [Impact on members' lives/careers]**
-**The Trigger Map IS the Strategic Foundation - And Prioritization Matters**
-The page must empower [Primary Persona] → make [them] awesome → [they] naturally become [champions] → [champions] drive adoption → adoption creates opportunities for all members.
-```
----
-### 6. Related Documents Footer
-```markdown
-## Related Documents
-- **[00-trigger-map.md](00-trigger-map.md)** - Visual overview and navigation
-- **[02-[Primary].md](02-[Primary].md)** - Primary persona
-- **[03-[Secondary].md](03-[Secondary].md)** - Secondary persona
-- **[04-[Tertiary].md](04-[Tertiary].md)** - Tertiary persona [if exists]
-- **[05-Key-Insights.md](05-Key-Insights.md)** - Strategic implications
----
-_Back to [Trigger Map](00-trigger-map.md)_
-```
----
-## Key Requirements
-**Language:**
-- ✅ "Create awesome [users]" NOT "convert users"
-- ✅ "Naturally become [champions]" NOT "make them champions"
-- ✅ Empowering, organic growth language
-**Priority Clarity:**
-- PRIMARY GOAL clearly marked as THE ENGINE
-- SECONDARY driven by primary
-- TERTIARY benefits FOR members (not company revenue)
-**SMART Objectives:**
-- Specific: Clear statement
-- Measurable: Defined metric
-- Achievable: Realistic target
-- Relevant: Ties to vision
-- Time-bound: Specific timeline
-**Flywheel Logic:**
-- Shows causal relationships
-- Emphasizes natural emergence
-- Makes primary goal's importance clear
----
-## Example
-See: `examples/WDS-Presentation/docs/2-trigger-map/01-Business-Goals.md`
-**Key features:**
-- ~150-160 lines
-- 3 clear priority tiers
-- 6-8 total objectives
-- Flywheel explanation
-- Success metrics show persona → objective connections
----
-## Output
-<output>✅ Business goals document created with flywheel!</output>
-Store as: `01-Business-Goals.md` in trigger map folder
----
-## Next Step
-<output>Ready for Step 3a: Generate Primary Persona</output>
-<action>Load and execute: step-03a-generate-primary-persona.md</action>
-Do NOT skip ahead.

package/src/workflows/2-trigger-mapping/document-generation/steps-c/step-03a-generate-primary-persona.md DELETED Viewed

@@ -1,96 +0,0 @@
-# Step 03a: Generate Primary Persona Document
-**Goal:** Create detailed profile for the PRIMARY target user
----
-## Purpose
-Create the PRIMARY persona document - the most important user who will transform into a champion.
-**Focus:** Most detail, full transformation journey, champion creation
----
-## Input Required
-From trigger map YAML:
-- `targetGroups.primary` section
-- Name, role, type, roleInFlywheel
-- 6 drivingForces (3 wants, 3 fears)
----
-## Template Reference
-Use the comprehensive persona document template:
-`templates/persona-document-template.md`
-This template provides the complete structure for sections 1-13.
----
-## File Naming
-```
-02-[Name]-the-[Role].md
-```
-**Example:** `02-Sarah-the-Student.md`
----
-## Key Requirements
-**Length:** ~250-375 lines
-**Tone:**
-- Rich, nuanced, human
-- Not "converting" but "creating awesome"
-- Natural language, storytelling
-**Driving Forces:**
-- Each must have **[Product] Promise**
-- Show how product addresses each driver
-- Be specific and actionable
-**Transformation:**
-- PRIMARY persona gets full BEFORE/AFTER section
-- Show emotional journey, not just functional
-- Use emojis to show emotional states
----
-## Primary-Specific Section
-**Include:** "Role in Flywheel: Creating Awesome [Personas] Who Become [Champions]"
-Show:
-- The natural evolution from user to champion
-- What they need to see on product page
-- Focus on transformation and champion creation
-- How they naturally advocate after transformation
----
-## Example
-Reference: `examples/WDS-Presentation/docs/2-trigger-map/02-Stina-the-Strategist.md` (PRIMARY - 282 lines)
----
-## Output
-<output>✅ Primary persona document created: `02-[Name]-the-[Role].md`</output>
-Store as: `02-[Name]-the-[Role].md` in trigger map folder
----
-## Next Step
-<output>Ready for Step 3b: Generate Secondary Persona</output>
-<action>Load and execute: step-03b-generate-secondary-persona.md</action>
-Do NOT skip ahead.

package/src/workflows/2-trigger-mapping/document-generation/steps-c/step-03b-generate-secondary-persona.md DELETED Viewed

@@ -1,104 +0,0 @@
-# Step 03b: Generate Secondary Persona Document
-**Goal:** Create detailed profile for the SECONDARY target user
----
-## Purpose
-Create the SECONDARY persona document - the validator who needs to trust the product.
-**Focus:** Validation strategy, trust building, evaluation process
----
-## Input Required
-From trigger map YAML:
-- `targetGroups.secondary` section
-- Name, role, type, roleInFlywheel
-- 6 drivingForces (3 wants, 3 fears)
----
-## Template Reference
-Use the comprehensive persona document template:
-`templates/persona-document-template.md`
-This template provides the complete structure for sections 1-13.
----
-## File Naming
-```
-03-[Name]-the-[Role].md
-```
-**Example:** `03-Marcus-the-Mentor.md`
----
-## Key Requirements
-**Length:** ~250-375 lines
-**Tone:**
-- Rich, nuanced, human
-- Not "converting" but "creating awesome"
-- Natural language, storytelling
-**Driving Forces:**
-- Each must have **[Product] Answer**
-- Show how product addresses each driver
-- Be specific and actionable
-**Validation:**
-- Focus on what builds trust
-- Show the evaluation journey
-- Address skepticism and concerns
----
-## Secondary-Specific Section
-**Include:** "Validation Strategy"
-Show:
-- What they need to see about the product
-- Conversion path: Discovery → Evaluation → Adoption → Advocacy
-- Focus on validation and trust building
-- How product proves its value to them
----
-## Example
-Reference: `examples/WDS-Presentation/docs/2-trigger-map/03-Lars-the-Leader.md` (SECONDARY - 316 lines)
----
-## Output
-<output>✅ Secondary persona document created: `03-[Name]-the-[Role].md`</output>
-Store as: `03-[Name]-the-[Role].md` in trigger map folder
----
-## Next Step
-**If Tertiary persona exists:**
-<output>Ready for Step 3c: Generate Tertiary Persona</output>
-<action>Load and execute: step-03c-generate-tertiary-persona.md</action>
-**If NO Tertiary persona:**
-<output>Ready for Step 4: Generate Key Insights Document</output>
-<action>Load and execute: step-04-generate-key-insights.md</action>
-Do NOT skip ahead.

package/src/workflows/2-trigger-mapping/document-generation/steps-c/step-03c-generate-tertiary-persona.md DELETED Viewed

@@ -1,96 +0,0 @@
-# Step 03c: Generate Tertiary Persona Document (Optional)
-**Goal:** Create detailed profile for the TERTIARY target user
----
-## Purpose
-Create the TERTIARY persona document - the beneficiary who discovers value organically.
-**Focus:** Benefits discovery, recognition journey, word-of-mouth potential
----
-## Input Required
-From trigger map YAML:
-- `targetGroups.tertiary` section (if exists)
-- Name, role, type, roleInFlywheel
-- 6 drivingForces (3 wants, 3 fears)
----
-## Template Reference
-Use the comprehensive persona document template:
-`templates/persona-document-template.md`
-This template provides the complete structure for sections 1-13.
----
-## File Naming
-```
-04-[Name]-the-[Role].md
-```
-**Example:** `04-Emma-the-Enthusiast.md`
----
-## Key Requirements
-**Length:** ~250-375 lines
-**Tone:**
-- Rich, nuanced, human
-- Not "converting" but "creating awesome"
-- Natural language, storytelling
-**Driving Forces:**
-- Each must have **[Product] Answer**
-- Show how product addresses each driver
-- Be specific and actionable
-**Discovery:**
-- Focus on organic value recognition
-- Show the appreciation journey
-- Emphasize benefits FOR members
----
-## Tertiary-Specific Section
-**Include:** "How [Persona Name] Discovers [Product] Value"
-Show:
-- The recognition path
-- Journey: Experience → Recognition → Appreciation → Word of Mouth
-- Focus on benefits and organic discovery
-- How they become advocates without being "targeted"
----
-## Example
-Reference: `examples/WDS-Presentation/docs/2-trigger-map/04-Felix-the-Full-Stack.md` (TERTIARY - 375 lines)
----
-## Output
-<output>✅ Tertiary persona document created: `04-[Name]-the-[Role].md`</output>
-Store as: `04-[Name]-the-[Role].md` in trigger map folder
----
-## Next Step
-<output>Ready for Step 4: Generate Key Insights Document</output>
-<action>Load and execute: step-04-generate-key-insights.md</action>
-Do NOT skip ahead.