Bundle breadcrumb may be confusing

[MrYamous]

Historically, Symfony projects were organized as bundles.
Today this is no longer the case but the term is still used to designate some packages made for Symfony.

In some places in the documentation, in the breadcrumb for example, I find that the two are mixed up and I think this can be confusing.

Lets take an exemple, Best Practices For Reusable Bundles which refers to bundles as packages but I if click on "Bundles" I'm redirected to a page that deals with the old system and says that it should no longer be used.

I also noticed main bundle documentation, which refers to old system, is accessible from index in the Architecture section but it seems outdated.

I can understand removing pages from the documentation might be a problem, but couldn't we find a solution to make this old bundle system less visible, remove it from the index, and improve the breadcrumb of pages that deal with bundles as packages?
Like by introducing a new page about main differences between PHP packages and Symfony Bundles, and using this new page in breadcrumb as top level of relevant pages.

[javiereguiluz]

I don't fully understand this. The caution message in the bundles page says that "using bundles in your own app is no longer recommended" ... but bundles are not deprecated at all. They are still recommended e.g. when creating reusable code for multiple projects (i.e. third-party bundles).

I think we should update that page to merge everything about creating bundles for Symfony apps in a single page. And, modernize the contents a bit (and add important missing contents like creating functional tests in bundles with a micro kernel app).