The problem with something community driven is it needs to be kept up to date.
This is especially relevant as NETMF versions change, and was one of the things I had trouble with when trying out examples I found on the web. Someone posts some code that worked on 4.1 but not 4.2, but they don't mention the version they are using because it's the latest at the time. I come along with a 4.2 N+2 not knowing anything about NETMF versions and spend a couple of hours in google working it all out.
That's good knowledge to have but for those 2 hours I was beginning to think this was just a little too hard. The same can be said for the wiki, which doesn't mention the hardware being used in many places because when the article wa swritten only the N1 existed. I know it's a wiki but it's also a good example of how user generated content isn't kept up to date
My most recent example was the SPI pins on the N2 and N+2. They aren't the same as the N1/N+1, you need to look at the pin functions and decode the MOSI/MISO and map them to the N2/N+2. Every example blog post etc I found on google was using the N1/N+1 board, so even google doesn't help you out of that one
Not overly difficult, but for a beginner probably pretty tricky when they are still trying to get to grips with SPI itself.
Updating the firmware is another place where confusion reins in regards to N1 vs N2 boards. Plenty of people with N2 boards end up with the Atmel tools installed and find they don't work. Then ask or keep googling until they find the ST tools
All that I think would be useful in any documentation. Some of it perhaps in a FAQ listed at the top of the page with home/hardware/projects etc. Perhaps the best idea is to look over all the sticky posts in the forums and evaluate them for inclusion in a FAQ.