I agree that most of this can be pulled into the component documentation and I will make the relevant changes especially now they are not all single page docs with @drak's changes. @weaverryan do you think the bare bones cookbook article should be a new one, it feels like it will overlap with the existing one on using compiler passes for tags quite a bit?

However since some more general issues have been raised about what belongs in which section then here is my opinion on that for what its worth. I agree that things that are relevant to components and not bundles should go in the components section. I think though that anything that relies on bundles and interaction between different components belongs in the cookbooks. I appreciate that you do not really need the full stack framework to use bundles since they are handled by ```HttpKernel\Kernel``` but essentially the full stack framework is the use of the bundles with the components and the other libraries included in the standard distribution. Yes you can use bundles with the components but you can also use third party libraries with the components and we should not document that in the components section. I think something in the HttpKernel component documentation about using bundles should be sufficient with a note to say that the cookbook section will have documentation relating to the use of these bundles.

I do think that there are several cookbook articles on the service container (and quite possibly others) that can now be moved into the component section as they really do just relate to the component and not its place in the full stack framework e.g. use of parent services, factories etc. I will look at moving these if this makes sense. I do think that there are a few issues to consider with this type of reorganisation though:

1) If there is to be quite a bit of reorganisation of cookbook articles into the component section then it should be done in a fairly short space of time and then well publicised - moving articles around here and there will harm the usability of the docs if articles people have read disappear and they have to hunt for the information.

2) If articles are to be moved then is there anything in place to deal with redirecting the urls since people will have bookmarked them, linked to them etc.?

3) I'm not sure that at the moment it is sufficiently clear that if someone is using the full stack framework that the components section contains a lot of information that will be relevant to them leading to people not looking in that section because they are not using the components as components and missing a lot of relevant documentation.

Has an approach of what should go where now that the components section is in place been decided upon, I am concerned that lots of little bits of reorganisation are going to take place, which are sometimes counter productive because of differing opinions on what should go where to the detriment of the end user. Not sure this is the best place to discuss this though :)

Also whilst I am churning out my opinions on organisation, it did occur to that at the moment there is nothing in the cookbook section to distinguish between the articles that will be relevant to the vast majority of use cases and those that are not as they cover areas that are not typcial of most apps or are most relevant to bundle maintainers.