Should add common pitfalls to some of the concepts pages and suggested practices

[johnwunder]

E.g.

• Data markings
• Instances vs. patterns
• ID namespaces (using example rather than a producer prefix)

[benjaminxscott]

Does the page not cover them sufficiently?

[johnwunder]

New idea: maybe we need a "top 10 mistakes in using STIX" page? Or "12 ways to get the most out of your threat intelligence in STIX"? Basically some succinct way of addressing the most common problems we see.

Obviously this is a stop-gap until the language can be redesigned to help people avoid them more naturally.

[benjaminxscott]

Hmm, if there's serious concerns from a bunch of varied user demographics, suggest doing a user-feedback sprint with a small set of enthusiastic users and focusing on changing the things that are most do-able and widest impact.

Having a 'top 10 mistakes' seems backtrack-y and unreasonable - like I wouldn't expect Chrome devs to have a writeup for "top 5 reasons why you're using tabs wrong" , they would instead make UI changes based on objective user feedback and A|B trials

relevant