Hi folks,
I was searching for that recent “community packages” page that was setup and Google directed me to this page which I didn’t know existed: External packages | Django documentation | Django
2 packages are under Django but the 3rd is under Jazzband.
Should they be part of the newer Ecosystem page here Django Community | Django? It feels a bit confusing having 2 but I guess more importantly is that one or the other may be missed if the user lands on a certain page.
Also while we’re on the topic that Ecosystem page doesn’t have those header link thingies.
I tried to look for the page under doc/ but realised it’s managed in the website code … I might try and check that out later when I have some spare time and see if it can be updated but if someone knows off the bat whether it’s doable or just wants to quickly do it then 
@steering_council Would you have a recommendation here? I’m asking since you have been working quite actively on package promotion.
Note that the header links got added recently by @adamghill
So that External Packages page seems to be for packages that have been pulled out of core over time, so they serve slightly different purposes, but I would be fine with moving those three packages to the Ecosystem page and redirecting this page to it.
Seems like contrib comments package is no longer maintained.
But I think there’s room for documentation like this. This is what I’d like to see more of rather than less, but in this current shape it feels unexpected.
Following up on this, and after having raised this in the recent Steering Council meeting, we agreed to shuffle things around and remove references to unmaintained packages: Relocated content from docs/topics/external-packages.txt where appropriate. by nessita · Pull Request #20507 · django/django · GitHub