Thoughts on a WIKI?

[bmadcode]

Created an issue - #154

Thinking about enabling the wiki if there would be people interested in contributing - thinking it could be a better way to document certain types of things that come up repeatedly, without putting them into the docs itself.

What types of things?

• Suggested workflows to follow
• what and when to customize beyond the defaults
• Specific IDE/Agent/MCP setups and how to use BMad method
• Customizations people have made and why (simplified workflow, brownfield workflow, greenfield with no architecture, etc...)
• Tips and Tricks
• Commonly asked questions and answers.

I have not used the wiki feature before in github, so would love feedback on if its worth doing, easy to maintain and admin, and easy to allow group contributions. I am starting to find it hard to find ideas and information in the discussions, and I can see many of the same types of questions coming in repeatedly - where if there were a wiki, it might help people much more.

[wu1ff]

The more info you can get out the better imo. If I can pull a 220k + build out of your method, then your definitely onto something profound. After months of vibe coding, trying task manager, mcps, ect this method provides the best results then your definitely onto something. Its really not that difficult, just needs to be presented in a clear, concise method from start to finish. Your videos leave out important parts that you have to guess at atm. But once I understood the process oh boy did it take off from there. Your fing killing it!

[bmadcode]

wow, thank you. I know in the current state its a bit confusing to piece together - wanna make it much simpler ASAP