BMAD-METHOD/docs/learn/00-course-overview/03-support.md

129 lines
3.6 KiB
Markdown

# Getting Started: Support
**Help, community, and what other designers say**
---
## What Other Designers Say
### Testimonials
> "I was skeptical at first - another design methodology? But WDS changed how I think about my role. I'm no longer just making things pretty. I'm the strategic thinker who makes products come alive."
>
> **— Sarah K., Product Designer**
> "The 5x speed increase is real. But what surprised me most was how much clearer my thinking became. Writing conceptual specifications forced me to understand the 'why' at a deeper level."
>
> **— Marcus L., UX Lead**
> "I thought AI would replace me. WDS showed me how to make AI amplify my thinking instead. Now I'm the most valuable designer on my team."
>
> **— Priya S., Senior Designer**
> "The paradigm shift hit me in Module 4: my design IS the product. The code is just the printout. That completely changed how I approach every project."
>
> **— James T., Design Director**
_Note: More testimonials will be added as designers complete the course._
---
## Common Questions
### FAQ
**Q: Do I need to know how to code?**
A: No. WDS is about design thinking and specifications. AI handles the implementation.
**Q: What if I don't have a project to practice with?**
A: The course includes practice exercises. You can also use a hypothetical project or redesign an existing app.
**Q: Can I use this with my current design process?**
A: Yes! WDS complements existing processes. Many designers integrate it gradually.
**Q: Is this only for digital products?**
A: WDS is optimized for digital products, but the principles apply to any design work.
**Q: What if I get stuck?**
A: Each module includes clear examples and guidance. The AI assistant can help clarify concepts as you learn.
**Q: Do I need to complete all modules?**
A: No. The Quick Start path (4 modules) gives you enough to start applying WDS immediately.
**Q: Can I teach this to my team?**
A: Yes! WDS is open-source and free. Share it with your entire team.
**Q: How is this different from traditional design documentation?**
A: Traditional docs describe WHAT. WDS captures WHY + WHAT + WHAT NOT TO DO. This makes it AI-ready and preserves your design intent.
---
## Getting Help
### During the Course
**While learning:**
- Each module includes detailed examples
- AI assistants can clarify concepts in real-time
- Practice exercises with clear success criteria
**After completion:**
- GitHub Discussions for questions and sharing
- Community showcase of WDS projects
- Regular updates and new case studies
**Contributing:**
- WDS is open-source and welcomes contributions
- Share your case studies and learnings
- Help improve the course for future designers
---
## Support & Community
### Resources
**Documentation:**
- Full course materials in markdown
- NotebookLM integration for audio/video learning
- Workshop materials for team training
**Community:**
- GitHub Discussions for Q&A
- Project showcase and feedback
- Regular updates and improvements
**Open Source:**
- Free to use and share
- Contributions welcome
- Help shape the future of WDS
---
## Ready to Start?
You have everything you need:
- ✅ The skills (design thinking)
- ✅ The tools (paper + AI)
- ✅ The time (10 hours)
- ✅ The motivation (staying indispensable)
**Next step:** Start learning!
**[Start Module 01: Why WDS Matters →](../module-01-why-wds-matters/module-01-overview.md)**
Or review the full course structure:
**[← Back to Course Overview](00-course-overview.md)**
---
[← Back to Learning Paths](02-learning-paths.md) | [Start Learning →](../module-01-why-wds-matters/module-01-overview.md)