Best way to organise content I am making a site which will deal with various micro-topics about a subject.

Each subject will have the following:
i) A backgrounder (one-time)
ii) A news blog (obviously recurring)
iii) FAQs (basically static)
iv) Set of links / documents (static too, but can simply be updated)

My problem is about organising the content.

(A) First option
* Every topic itself will be a taxonomy term
* Create 4 content types: backgrounder, blog, faqs, links


First, the problem here is that soon I'll run into probably a few thousand topics i.e. a few thousand taxonomy terms.
Second, since each term page will have to serve as the homepage for that topic, I have no clue how to organise such a page.


(B) Second option
* Each topic will be a node.
* Each facet (backgrounder, blog, faqs, links) will be CCK fields.


First, the problem here is that it would probably look awful, if the newsblog becomes longwinding.
Second, managing this might become difficult.
Third, since most of the content will be CCK inputs, the actual node area might not have any content. Searc indexing becomes a hassle.


Right now I am quite clueless.

Any advice towards the right direction would be of great help.



Subir
First off, this isn't really a question that has a single correct answer.

It is really up to the site builder as to how they want it to work and it depends greatly on the use cases of the site and any business rules related to the content.

As such, it isn't the best question for a site like this, however I will say a couple of things:


Having thousands of taxonomy terms is ok if your content requires it. You might have a thousands of taxonomy terms and tens or hundreds of thousands of nodes. That's fine.
The second option you mention doesn't sound like a good idea. Mainly the use of fields as blogs etc. doesn't sound right conceptually. Plus handling revisions, permissions, comments for blog posts etc. is going to be a hassle to say the least.
The first option mentioned doesn't necessarily have to have the term page as the topic homepage. It could be done other ways, like having the backgrounder node as the topic homepage or using a views page with arguments to be the homepage.
Another possible solution is to have the backgrounder node be the home page and link everything to that via an entity reference field, removing the need for taxonomy at all.
As for laying out the home pages, consider using the panels or context modules combined with views.


These are not nearly all the possibilities, there are a bunch of other ways things could be done, so you can see you will not be able to get someone to give you a definitive answer.