Community resources / third-party packages page maintained by the Steering Council

[tim-schilling]

Hi all!

The Steering Council wants to help improve the visibility of community resources (think djangopackages.com) and third-party packages within the Django ecosystem. We feel that the best first step is to have a simple page that highlights several of these. We're working on some basic designs and will be putting them forth (see #1907 as the first step to getting a branch where this work will occur).

If someone is UI inclined and available to help, please respond here for us to reach out if/when we'd need help!

On the topic of resources, we want to be clear that the collection of resources will managed only by the Steering Council. The goal here is to limit the number of requests that will come in asking add to the list. We have tossed around the idea of including a footnote on the section to state that this list is fixed by the Steering Coucil.

The other thing we want to explore is setting up the Steering Council as codeowners for the area of the code base that handles this page. That way if a PR does come in, we can address it.

Please let us know what concerns or questions you have!

[sarahboyce]

I think we could be inspired by/copy the approach of Laravel here 👀

Notice that they have:

• "Ecosystem" in the footer of their website, this lists some packages: https://laravel.com/
• A "Packages" section in their docs (check the navigation drop down): https://laravel.com/docs/11.x/

They have a page per package with extensive docs (e.g. https://laravel.com/docs/11.x/valet#main-content)
I think we'd have 1 page with all the packages with a short intro and links to their documentation
I would recommend this to be in the Django docs, possibly in "topics", because this means it is searchable.
I think adding a link to this 1 page (whether we call it packages or ecosystem) on the header or footer of djangoproject.com is also nice.

Anyway, this would be my suggestion 😁

[frankwiles]

Work in Progress mockup of what we're thinking. The gray boxes are to be tables/lists of the items. Nothing set in stone, just the rough sketch of where we think we're heading.

[carltongibson]

@frankwiles I bootstrapped a view/template combo and pushed it to a sc-ecosystem-page branch

Compare view