diff --git a/src/modules/wds/agents/saga-analyst.agent.yaml b/src/modules/wds/agents/saga-analyst.agent.yaml index 8f59dfb6..d26d138b 100644 --- a/src/modules/wds/agents/saga-analyst.agent.yaml +++ b/src/modules/wds/agents/saga-analyst.agent.yaml @@ -31,16 +31,21 @@ agent: I ask one question at a time and listen deeply to your answer. **When responding to user ideas or questions, I follow this pattern:** - 1. **Acknowledge** - "I hear you asking about..." or "That's an interesting idea..." - 2. **Summarize** - "So you're thinking that..." or "What I'm understanding is..." - 3. **Confirm understanding** - "Is that right?" or "Am I understanding correctly?" - 4. **Then explore solutions** - Only after confirming understanding do I offer options or suggestions + 1. **Listen and reflect naturally** - Reflect back what I hear in my own words, as a human + colleague would. Never use technical labels like "Acknowledging:" or "Summarizing:" or scripted + phrases. Trust myself to word acknowledgments naturally and as human as possible. Be an + intentional listener, not a technical processor. + 2. **Confirm understanding** - Ask naturally if I understand correctly, then wait for confirmation + before moving forward + 3. **Then explore solutions** - Only after confirming understanding do I offer options or suggestions - I never jump straight to bullet lists or solutions. I always acknowledge, summarize, and confirm - understanding first. This ensures we're truly aligned before moving forward. + I never jump straight to bullet lists or solutions. I always listen, reflect back what I hear + in natural conversation using my own words, and confirm understanding first. This ensures we're + truly aligned before moving forward. I reflect back what I hear to ensure I understand before moving forward. This reflection happens - before any solution exploration. + naturally - like talking with a colleague who's really listening, not a technical system + processing information. I trust myself to find the right words in the moment. I'm professional, direct, and efficient. I'm nice but I play no games - we're here to get things done. Analysis should feel like working with a skilled colleague, not a therapy session. @@ -78,26 +83,28 @@ agent: working_rhythm: | When we work together: 1. You share an idea or question - 2. I acknowledge what you've said - 3. I summarize to show I understand - 4. I confirm: "Is that right?" or "Am I understanding correctly?" - 5. Once confirmed, we explore solutions together - 6. I structure insights into clear documentation + 2. I listen and reflect back what I hear naturally, in my own words + 3. I confirm understanding naturally, then wait for your confirmation + 4. Once confirmed, we explore solutions together + 5. I structure insights into clear documentation What works well: - - Acknowledging before responding - - Summarizing to confirm understanding - - Confirming before exploring solutions + - Listening intentionally and reflecting back naturally in my own words + - Trusting myself to find the right words in the moment + - Confirming understanding before moving forward - One question at a time keeps things focused - Building together feels collaborative + - Pausing to confirm before moving to the next question What tends to feel less collaborative: - Jumping straight to bullet lists or solutions - - Not acknowledging the user's idea first - - Not summarizing or confirming understanding - - Listing many questions (feels like a survey) + - Using technical labels like "Acknowledging:" or "Summarizing:" or scripted phrases + - Not reflecting back what I hear in natural conversation + - Not confirming understanding before moving forward + - Listing many questions at once (feels like a survey) - Generating without checking in - Moving too fast without reflection + - Asking follow-up questions before confirming the current answer menu: - trigger: workflow-status diff --git a/src/modules/wds/examples/WDS-Presentation/docs/1-project-brief/01-product-brief.md b/src/modules/wds/examples/WDS-Presentation/docs/1-project-brief/01-product-brief.md new file mode 100644 index 00000000..e875d22d --- /dev/null +++ b/src/modules/wds/examples/WDS-Presentation/docs/1-project-brief/01-product-brief.md @@ -0,0 +1,726 @@ +# WDS Presentation Page - Product Brief + +**Project:** WDS Official Presentation Page +**Date:** December 24, 2025 +**Author:** Saga WDS Analyst Agent +**Status:** In Progress + +--- + +## Project Vision + +Create the official WDS presentation page for Whiteport.com that serves as the entry point for designers and entrepreneurs to understand, learn, and adopt the WDS methodology. + +**Primary Audience:** Designers (UX, product, visual) +**Secondary Audience:** Entrepreneurs, system owners, clients + +**Core Message:** WDS is an end-to-end design methodology that makes designers indispensable by delivering value through structured, actionable specifications—not through speed, but through responsibility and excellence. + +--- + +## Project Background & Complexity + +### The Challenge We're Solving + +This page must address multiple complex positioning challenges simultaneously: + +**For Designers - The Paradigm Shift:** + +The fundamental challenge is that WDS represents a complete shift in how designers work. It's not an incremental improvement to existing tools—it's a transformation of the designer's role itself. + +- **Not a tool, but a methodology:** Most designers look for tools that solve a fraction of their process (prototyping, wireframing, handoff). WDS is an end-to-end solution covering the entire journey from idea to maintenance. We must help designers see this isn't about adding another tool to their stack—it's about changing how they approach their entire craft. + +- **Moving into the codebase:** Traditional design happens in visual tools (Figma, Sketch, Adobe). WDS requires designers to "move into" the codebase itself—working in IDEs and GitHub where their work lives alongside code. This is counterintuitive and requires a mindset shift. We must acknowledge this challenge while showing why it's worth it. + +- **Text-based interfaces:** The workflow requires working in text-based environments. This feels counterintuitive for designers who are naturally drawn to visual software and "touching and feeling" their designs. We must be honest about this, not pretend it's simple. + +- **The call to adventure, not ease:** We're not positioning WDS as "simple and intuitive." Instead, we're calling designers to the adventure of taking responsibility for product success. The right designers will appreciate going "pro" and serving as linchpin actors who bridge business and user goals. + +**The Designer Profile We Seek:** + +We're looking for designers who: +- See both business goals and user goals clearly +- Have a bleeding passion for creating the optimal meeting between them +- Wish to serve clients and teams by becoming linchpin actors +- Are willing to stand up and take responsibility for product success +- Understand that sometimes fast stands in the way of what matters +- Want to deliver real value, not just quick iterations + +**Key Message:** "WDS is for people and services that mean business." + +**For Entrepreneurs/Clients - Counter to "Vibe Coding":** + +Entrepreneurs and clients are falling for cheap, unrealistic proposals from "vibe coding" tools that promise quick results without depth. + +- **The uncomfortable truth:** It's an uncomfortable position to be the realist in the room, but it's the right position. Fast is shallow. Real takes effort. Services that actually work need to function, not just look nice—this is a magnitude more complicated than rapid prototyping. + +- **The vibe coding problem:** Today's vibe coding tools don't want users to be successful—they want users to keep burning tokens. "Done" is not their goal; "feeling like you're getting there" is what they aim at. + +- **The alternative narrative:** Attention to detail from the start will get you there. Screen by screen, interaction by interaction. You'll get a result that works and flies, not just looks nice. Having a skilled designer in the ride is your best chance to get there. + +- **The designer as guide:** The designer is your guide on dark waters. When you don't know where you're going or what to do, the designer's process leads the way. Not through glamorous prototypes that sound shallow, but through craft perfected through decades and supercharged by AI. + +**Key Message:** "WDS is an insurance plan and a healthy meal plan. It's nutritious and healthy with no extra calories that will clog your arteries. Just what your project needs. Not glamorous, not a promise of quick fix. But through excellence and best practices." + +### Why This Positioning is Difficult + +We must balance seemingly contradictory messages: +- Acknowledge challenges WITHOUT discouraging people +- Be realistic about effort WITHOUT making it seem impossible +- Counter "vibe coding" WITHOUT directly criticizing competitors +- Call to responsibility WITHOUT sounding preachy +- Show depth and seriousness WITHOUT overwhelming beginners +- Serve both audiences (designers + entrepreneurs) WITHOUT diluting message + +### Our Approach + +**No Criticism of Other Technologies:** +We will not criticize other tools or techniques directly. Instead, we focus entirely on WDS benefits and challenges, breaking challenges into clear, structured steps. + +**Focus on Value:** +The power comes from being IDE-based with agents that can be molded and enhanced for each project or organization. This flexibility and depth is our strength. + +**Truth in Positioning:** +We acknowledge this isn't easy or simple. But we show the value is worth the effort, and we provide clear structure to make it achievable. + +--- + +## Current Page Analysis & Constraints + +### Reference: Existing WDS Course Page + +![Current WDS Page Structure](../Resources/WhiteportLegacyPage.jpg) + +The current page (shown above) is built on WordPress and serves as a template for the WDS course presentation. This existing structure provides both opportunities and constraints for our new page. + +### Current Page Structure + +**1. Header & Navigation** +- Whiteport logo (left) +- Navigation menu: Start, Agency, Projects, Services, Solutions, Manifesto, Blog, Contact +- Social media icons (right) + +**2. Hero Section** +- Deep blue background with illustration +- Large headline: "Whiteport Design Studio, WDS" +- Tagline: "FREE AND OPEN SOURCE DESIGN AND STRATEGY AI AGENTS FOR OCDACID DESIGNERS EVERYWHERE!" +- Body text explaining the course concept +- Primary CTA button: "GET INFO 2025. FREE AT GITHUB" + +**3. Benefits Section (Three Columns)** +- Pink/purple icons +- Three value propositions: + - "Master sketching by hand" + - "Solve problems together" + - "Prompt more effectively" +- Each with descriptive text +- Blue link at bottom: "FOLLOW THE 5000 PEOPLE WHO LEARNED HOW TO SKETCH BY HAND WITH MASTER ANENER, THE FOUNDER OF WHITEPORT" + +**4. Two-Column Section** +- Left column: "Whiteports Design Studio" + - "For designers everywhere" + - "Get given here" (text area for main content) +- Right column: "Course program" + - Course description + - Session listings (1-4) with pink circular icons + - Session titles and descriptions + - Blue CTA button: "CLAIM YOUR SEAT NOW" + +**5. "Get your seat now!" Section** +- Three checkmarks with benefits: + - "Choose your time and place" + - "Get a supportive network" + - "Get your personal follow up & feedback" +- Large pricing: "190€" +- Blue button: "CLAIM YOUR SEAT NOW!" +- PayPal logo +- "LET US KNOW YOUR INVOICE DETAILS" + +**6. Footer Section** +- Dark blue background +- "Contact us" heading +- About text (left side) +- Two circular profile photos (Mårten and colleague) +- Contact details: Names, titles, emails, phone numbers +- Bottom bar: Copyright, social links + +### Constraints We Must Work Within + +**Technical Constraints:** + +1. **WordPress Platform** + - Must work within WordPress page editor capabilities + - Limited to WordPress formatting options + - Need paste-ready editor code for quick deployment + +2. **Template Reuse** + - Using existing template structure to reduce development cost + - Cannot do major structural changes + - Must adapt content to fit existing layout patterns + +3. **Left Column Content Area** + - Main editable area is left column in two-column section + - This is where we'll place most custom content + - WordPress editor code must be carefully formatted for this area + +**Design Constraints:** + +1. **Existing Visual Language** + - Deep blue hero background + - Pink/purple accent colors for icons + - Illustration style (person with tablet) + - Blue CTA buttons + - Circular profile photos + +2. **Layout Patterns** + - Hero with right-side illustration + - Three-column benefit cards + - Two-column main content area + - Stacked session/module listings with icons + - Pricing/CTA section + - Footer contact section + +**Content Constraints:** + +1. **Pricing Section** + - Current page has pricing (190€) + - WDS is free and open-source + - Need to adapt this section for different purpose (perhaps "Get Started" CTAs instead) + +2. **Course vs. Method Page** + - Current page is course-focused + - Our page is method presentation + course access + - Must balance methodology explanation with course promotion + +3. **Session Listings** + - Current format shows 4 sessions + - We have 17+ modules (though only 2 complete) + - Need to show completed modules + indicate more coming + - May need to adapt visual presentation + +### Opportunities Within Constraints + +**What Works Well:** + +1. **Hero Section:** Perfect for WDS positioning message +2. **Three-Column Benefits:** Ideal for "The WDS Difference" section +3. **Two-Column Layout:** Left column can contain full methodology explanation, agents section, and installation guide +4. **Session Listings:** Can be adapted for course modules with YouTube embeds +5. **Footer Contact:** Good for Mårten bio and Whiteport information + +**Creative Solutions Needed:** + +1. **Course Modules in Tables:** We can use WordPress table formatting within the left column to present course modules with YouTube embeds, descriptions, and GitHub links + +2. **Agent Presentations:** Can use heading hierarchy + formatted text in left column to introduce each agent with personality and role + +3. **Installation Checklist:** Can use WordPress checklist or ordered list formatting with links to Module 02 lessons + +4. **Testimonials:** Can adapt the three-column section or create new section using WordPress column blocks + +5. **BMad Method Subsection:** Can use nested headings and formatted text to explain foundation + +### Deliverable Requirements + +To work within these constraints, our specifications must include: + +1. **WordPress Editor Code Blocks** + - Ready to copy-paste into WordPress page editor + - Properly formatted headings (H2, H3, H4) + - Links formatted as WordPress links + - Lists (ordered, unordered, checklists) in WP format + - Tables for course modules (if needed) + - YouTube embeds with proper WP shortcode + +2. **Content Sections Mapped to Template Areas** + - Hero content (headline, tagline, body, CTA text) + - Three-column benefits content + - Left column main content (methodology, agents, installation) + - Right column course modules (adapted session format) + - Adapted pricing/CTA section (free, get started) + - Footer content (bio, contact) + +3. **Visual Element Specifications** + - Icon selections (where needed) + - Image placements + - Button text and links + - Color usage (within existing palette) + +### Success Criteria Considering Constraints + +The page is successful if we: + +1. **Communicate WDS Value** within template structure limitations +2. **Present Course Modules** effectively in session listing format +3. **Explain Methodology** clearly in left column content area +4. **Maintain Visual Consistency** with existing Whiteport design language +5. **Provide Paste-Ready Code** that works immediately in WordPress +6. **Deliver Quickly** by reusing template (low cost, fast deployment) +7. **Allow Future Updates** as more course modules complete + +--- + +## Page Structure & Information Architecture + +Using Action Mapping model to identify user actions and required information for each section. + +--- + +### SECTION 1: HERO SECTION + +**User Action Goal:** Understand what WDS is and decide to explore further + +**What Users Need to Learn:** +- What WDS is (in one clear statement) +- Who should care about it +- Why it matters (value proposition) +- Where to go next (GitHub repository) + +**Information to Provide:** +- Headline: Clear statement of what WDS is +- Subheadline: Who it's for (designers, entrepreneurs) +- Description: The paradigm shift (design → specification → product) +- Value statement: Why this matters (responsibility, excellence, results) +- Primary CTA: "Explore on GitHub" (link to repository) +- Secondary CTA: "Read WDS Articles" (link to filtered blog posts) + +**Success Metric:** User understands WDS concept and clicks through to GitHub or continues reading + +--- + +### SECTION 2: WHAT IS WDS + +**User Action Goal:** Understand the WDS methodology and its foundation + +**What Users Need to Learn:** +- The paradigm shift in design process +- That WDS is built on proven BMad Method (credibility) +- The relationship between design (WDS) and development (BMM) +- That this is a serious, established methodology with 25 years of experience + +**Information to Provide:** + +#### Main Explanation +- **The Paradigm Shift:** + - The design becomes the specification + - The specification becomes the product + - The code is just the printout + +- **What WDS Delivers:** + - End-to-end solution (idea → maintenance) + - Conceptual specifications (100% actionable) + - Designer as linchpin (bridge business + user needs) + - Why-based specifications (WHAT + WHY + WHAT NOT TO DO) + +#### Subsection: "Standing on the Shoulders of Giants" + +**User Action Goal:** Trust that WDS is credible and proven + +**What Users Need to Learn:** +- WDS is built on BMad Method (established development methodology) +- Mårten's 25 years of design experience added to proven framework +- In v6: BMM module handles development, WDS handles design +- The integration is seamless and complete + +**Information to Provide:** +- Brief explanation of BMad Method (AI-augmented development framework) +- Open-source, proven, not "BS Mårten cooked up" +- WDS as design module within larger ecosystem +- v6 architecture: WDS (design) → BMM (development) +- Link to BMad Method documentation + +**Success Metric:** User trusts WDS credibility and understands the ecosystem + +--- + +### SECTION 3: THE WDS DIFFERENCE + +**User Action Goal:** Quickly grasp the three key benefits + +**What Users Need to Learn:** +- WDS is comprehensive (not just one tool) +- Specifications are immediately actionable +- Designers become strategic leaders (linchpins) + +**Information to Provide:** +Three columns with icons/visuals: + +1. **End-to-End Solution** + - Not rapid prototyping or single-purpose tool + - Full journey: idea → specification → development → maintenance + - Designers work in codebase, not separate from it + +2. **100% Actionable Specifications** + - Conceptual specifications ready for AI or human teams + - No interpretation needed + - Unified IDs, error states, multi-language content included + +3. **Designer as Linchpin** + - Bridge business goals and user needs + - Responsibility for product success + - Serve team as strategic guide + +**Success Metric:** User sees unique value and wants to learn more + +--- + +### SECTION 4: MEET THE WDS AGENTS + +**User Action Goal:** Understand how agents guide through phases and relate to them as teammates + +**What Users Need to Learn:** +- WDS uses specialized agents for different phases +- Each agent has personality, expertise, and specific role +- Agents guide, don't dictate +- The phases are covered through agent collaboration + +**Information to Provide:** + +Each agent presented with: +- Agent name + icon + tagline +- Role/personality description (relatable, human) +- Phases they guide +- What you create together + +#### Saga the Analyst 📚 +_"The one who tells your product's strategic story"_ + +**Role:** Business Analyst + Product Discovery Expert + +**Phases Guided:** +- Phase 1: Product Brief +- Phase 2: Trigger Mapping + +**What You Create:** +- Strategic foundation +- Target users and personas +- Business goals connected to user needs +- Trigger maps showing psychological drivers + +**Why Saga Matters:** Helps uncover the story of why your product exists and who needs it + +--- + +#### Freyja the Designer ✨ +_"The one who brings clarity through design"_ + +**Role:** UX Designer + Design System Expert + +**Phases Guided:** +- Phase 4: UX Design (Scenarios) +- Phase 5: Design System (optional) + +**What You Create:** +- Page specifications with object IDs +- Interactive prototypes +- Component libraries +- Visual specifications that guide development + +**Why Freyja Matters:** Transforms ideas into detailed, beautiful specifications that developers can implement perfectly + +--- + +#### Idunn the PM ⚔️ +_"The strategic leader who plans the path forward"_ + +**Role:** Product Manager + Technical Planner + +**Phases Guided:** +- Phase 3: Platform Requirements +- Phase 6: PRD Finalization + +**What You Create:** +- Technical architecture decisions +- Complete PRD (Product Requirements Document) +- Implementation roadmap +- Handoff packages for development + +**Why Idunn Matters:** Ensures technical feasibility and organizes design work for smooth development + +--- + +#### Mimir the Orchestrator 🧙 +_"The wise one who coordinates the whole journey"_ + +**Role:** Project Orchestrator + Workflow Guide + +**What Mimir Does:** +- Guides you through WDS workflow +- Routes you to appropriate agents +- Keeps project status and progress +- Helps choose which phases you need + +**Why Mimir Matters:** Your entry point and guide through the entire WDS process + +**Success Metric:** User understands agent roles and sees them as helpful guides, not technical systems + +--- + +### SECTION 5: FROM DESIGN TO DEVELOPMENT + +**User Action Goal:** Understand how design deliveries transition to implementation + +**What Users Need to Learn:** +- Design work doesn't stop at handoff +- BMM agents handle breakdown, development, testing +- The transition is seamless because specifications are complete +- WDS + BMM = complete product journey + +**Information to Provide:** + +**The Journey:** +1. WDS agents guide design phases +2. Design deliveries created (PRD, specifications, prototypes) +3. BMM agents take over for development +4. BMM handles: epic breakdown, story creation, implementation, testing +5. Continuous feedback loop between design and development + +**BMM Agents (Brief Introduction):** +- Dev agents: Break down PRD into implementable stories +- Development agents: Write code based on specifications +- QA agents: Test against design specifications +- [Link to BMad Method documentation for full details] + +**Why This Matters:** +- Designers remain in control of creative vision +- Specifications are so clear, implementation is straightforward +- No "lost in translation" between design and development +- AI can implement perfectly because intent is captured + +**Success Metric:** User understands complete workflow and sees how WDS fits into larger process + +--- + +### SECTION 6: COURSE MODULES + +**User Action Goal:** Access learning resources and start learning WDS + +**What Users Need to Learn:** +- Course modules exist to teach WDS step-by-step +- Modules 01-02 are complete and ready +- More modules are in development +- Each module has video, lessons, and GitHub resources + +**Information to Provide:** + +**Table Format with Columns:** +- Module Number/Name +- Status (Complete / In Progress / Coming Soon) +- YouTube Video Embed (if available) +- Brief Description +- Links (GitHub lessons, NotebookLM resources) + +**Completed Modules:** + +#### Module 01: Why WDS Matters +- **Status:** ✅ Complete +- **Video:** [YouTube embed] +- **Description:** Learn why designers are indispensable in the AI era. Understand the paradigm shift from prototyping to specification-driven design. +- **Topics:** Factory mindset vs linchpin mindset, AI threats and opportunities, becoming irreplaceable +- **Links:** [GitHub Module 01] | [NotebookLM Resources] + +#### Module 02: Installation & Setup +- **Status:** ✅ Complete +- **Video:** [YouTube embed] +- **Description:** Get WDS running on your machine. Step-by-step guide to GitHub, IDE setup, and agent activation. +- **Topics:** GitHub setup, IDE installation, cloning repository, initializing WDS, activating Mimir +- **Links:** [GitHub Module 02] | [Quick Checklist] + +**In Development:** + +#### Module 03: Alignment & Signoff +- **Status:** 🔄 In Development +- **Description:** Learn to create alignment documents and secure stakeholder commitment before starting design work. + +#### Module 04: Project Brief +- **Status:** 🔄 In Development +- **Description:** Create strategic foundation through conversational discovery with Saga. + +[Continue listing remaining modules with "Coming Soon" status] + +**Note:** "We're developing these modules in collaboration with designers like you. More modules added regularly." + +**Success Metric:** User clicks to watch videos or access GitHub lessons + +--- + +### SECTION 7: QUICK START INSTALLATION + +**User Action Goal:** Get WDS installed and ready to use + +**What Users Need to Learn:** +- The 5 essential steps to get started +- Each step has detailed instructions available +- It's achievable (not overwhelming) + +**Information to Provide:** + +**Installation Checklist:** +(Each item links to detailed Module 02 lesson) + +□ **Step 1: Set Up GitHub Account** + → [Detailed Guide: GitHub Setup] + +□ **Step 2: Install IDE (Cursor Recommended)** + → [Detailed Guide: IDE Installation] + +□ **Step 3: Clone WDS Repository** + → [Detailed Guide: Git Cloning] + +□ **Step 4: Initialize WDS in Your Project** + → [Detailed Guide: WDS Initialization] + +□ **Step 5: Activate Mimir Orchestrator** + → [Detailed Guide: Agent Activation] + +**Time Required:** ~30 minutes for complete setup + +**Support Available:** [Link to Discord/Community] | [Troubleshooting Guide] + +**Success Metric:** User completes setup or bookmarks checklist for later + +--- + +### SECTION 8: WHAT OUR USERS SAY + +**User Action Goal:** Build trust through social proof + +**What Users Need to Learn:** +- Real designers use and value WDS +- Results are tangible (quotes will show specific benefits) +- Community exists + +**Information to Provide:** + +**Testimonial Carousel Structure:** +(Ready for quotes to be added) + +- Profile photo (circular) +- Quote text +- Name +- Title/Role +- Company (optional) + +**Placeholder Content:** +"Testimonials from designers and teams using WDS will appear here. If you've tried WDS, we'd love to hear your story!" + +[Link to: Share Your WDS Story] + +**Success Metric:** User gains confidence in WDS through peer validation + +--- + +### SECTION 9: GET STARTED NOW + +**User Action Goal:** Take immediate action (GitHub, course, or community) + +**What Users Need to Learn:** +- Multiple entry points available +- Choose path based on readiness level + +**Information to Provide:** + +**Three Clear CTAs:** + +1. **Explore WDS on GitHub** + - "Browse the repository, read documentation, and clone WDS" + - [Button: View on GitHub] + +2. **Start the Course** + - "Learn WDS methodology through guided modules" + - [Button: Begin Module 01] + +3. **Join the Community** + - "Get help, share work, connect with other designers" + - [Button: Join Discord/Community] + +**Additional Resources:** +- [WDS Workflows Guide] +- [Example Projects] +- [FAQs] + +**Success Metric:** User takes action through one of the three paths + +--- + +### SECTION 10: FOOTER + +**User Action Goal:** Find additional information or contact + +**Information to Provide:** + +**About Section:** +- Brief bio of Mårten Angner (creator) +- Whiteport agency information +- Mission statement: "Free and open-source for designers everywhere" + +**Links:** +- GitHub Repository +- BMad Method +- Whiteport.com +- Blog/Articles +- Contact + +**Social Media:** +- LinkedIn +- Twitter/X +- YouTube +- Discord + +**Legal:** +- Open-source license information +- Privacy (if applicable) + +**Success Metric:** User finds needed information or contact method + +--- + +## Page Technical Requirements + +**Platform:** WordPress +**Template:** Existing WDS Course page template +**Editor:** WordPress page editor + +**Specifications Should Include:** +- WordPress editor code (paste-ready) +- For course modules: YouTube embeds in tables +- Formatted text with proper headings (H1, H2, H3) +- Links formatted as WordPress links +- Button CTAs with proper styling + +**Deliverable Format:** +- Markdown specification (this document) +- WordPress editor code blocks (ready to paste) +- Content in English +- Links to GitHub, course modules, resources + +--- + +## Success Criteria + +**Page is successful if:** +1. Designers understand WDS value and credibility (not just another tool) +2. Entrepreneurs understand how WDS supports their projects +3. Users can easily find and access course modules +4. Clear path to installation and first use +5. Trust is established through BMad foundation and methodology depth +6. Page loads quickly (WordPress template reuse) +7. Content is paste-ready for WordPress deployment + +--- + +## Next Steps + +1. ✅ Complete Product Brief (this document) +2. Create Trigger Map (Phase 2) +3. Create page specifications with content (Phase 4) +4. Generate WordPress editor code +5. Test in WordPress staging +6. Deploy to Whiteport.com + +--- + +**Document Status:** Draft for review +**Next Review:** After Trigger Mapping phase +**Last Updated:** December 24, 2025 + diff --git a/src/modules/wds/00-getting-started/00-about-wds.md b/src/modules/wds/get-started/00-about-wds.md similarity index 100% rename from src/modules/wds/00-getting-started/00-about-wds.md rename to src/modules/wds/get-started/00-about-wds.md diff --git a/src/modules/wds/00-getting-started/where-to-go-next.md b/src/modules/wds/get-started/where-to-go-next.md similarity index 100% rename from src/modules/wds/00-getting-started/where-to-go-next.md rename to src/modules/wds/get-started/where-to-go-next.md