Create threat-modeling-for-designers.md file to continue our conversation on how we might shape this concept/resource for product designers, and eventually, for the design chapter in general
Organize the repo for easier finding, i.e. create docs folder
AC
[x] The file organization makes sense, and does not break wiki
[x] The threat-modeling-for-designers.md doc is reviewed for typos, "hmm, content hierarchy could be better", etc.
Why and how: (See commits below for details)
threat-modeling-for-designers.md
file to continue our conversation on how we might shape this concept/resource for product designers, and eventually, for the design chapter in generaldocs
folderAC
threat-modeling-for-designers.md
doc is reviewed for typos, "hmm, content hierarchy could be better", etc.