This might be basic to you, but as I go through a process to architect a SharePoint site to support users of MS Project, MS Project Server, Planning Tools, Cost Tools, etc. A technical audience that will seek How-To tools use and Process guidance.
How do you more experienced architects/admins parse the data that can go in either a wiki, a blog, a list or library? Is there rhyme or reason to the approach? I can probably more easily separate the data that goes into a wiki. But when it comes to informing the users of tools usage and business cycle processes I see blur'd lines.
For example if I have a "how-to do X" process document, it is easy to see that it can go into a library of knowledge. But might it also go to a Blog? Or would you generally use the blog to inform that the process is in the "How-to" library?
What types of data do you all put in the different sharepoint features I am asking about?
Any guidance is appreciated!