Add resources section to the documentation

[dr-rompecabezas]

Description

This PR adds a new "Resources" section to the documentation that provides a curated list of tutorials and talks about Django Debug Toolbar.

• The criteria used to select the links for inclusion were added to the page.
• The link to the new page was placed on the menu after all the links related to installation, configuration, and overview of the toolbar, and just above the changelog, i.e., the first "metadata" link.
• The changes were tested by building the docs locally with Sphinx.

Closes #2070

Checklist:

• I have added the relevant tests for this change.
• I have added an item to the Pending section of docs/changes.rst.

[dr-rompecabezas]

I see four lines are too long. I'll fix the issue right away.

[dr-rompecabezas]

The CI failed due to a spell check.

 resources.rst:34: : Spell check: Webapp: A Related Matter: Optimizing Your Webapp by Using Django Debug Toolbar.

I see no point in adding this word to spelling_wordlist.txt so I'll change it to "Web App" and try again.

[matthiask]

If you look at the test runs you can see that we have unrelated failures because of a CSP related change. Maybe the package has been upgraded and our tests aren't compatible yet? You could try running the tests locally using tox, maybe while regenerating the vent so that you get new versions of all dependencies. And maybe find a django-csp version which still works, and we can fix the underlying issue later?

[dr-rompecabezas]

@matthiask thanks for the feedback and pointers for investigating.

The error message in the test failures suggests our tests fail due to the middleware order.

The tests passed a few days ago with version 4.0b2 of the django-csp package. They are failing in the latest release 4.0b3.

See the commit that added the error message we see raised in our tests, as well as the related issue and discussion.

# csp/middleware.py
    @staticmethod
    def _csp_nonce_post_response() -> None:
        raise CSPNonceError(
            "The 'csp_nonce' attribute is not available after the CSP header has been written. Consider adjusting your MIDDLEWARE order."
        )

In our tests, we append the CSPMiddleware to the end of the list.

For example:

    @override_settings(
        MIDDLEWARE=settings.MIDDLEWARE + ["csp.middleware.CSPMiddleware"]
    )
    def test_exists(self):
    ...

That's as far as I've gotten. I will resume investigating later and may attempt to tweak the middleware order in our tests after researching further.

[tim-schilling]

I really like what you have here! This is excellent work. I've got thoughts on some things we may want to do differently. If you disagree, please let me know.

[tim-schilling]

I'll try to take a closer look at this over the weekend. I suspect there's a doc building error in this though. I think you might be able to reproduce it with tox -e docs. The syntax around :doc: doesn't look quite right to me, but I could be wrong.

I'm also going to add https://djangotv.com/videos/djangocon-us/2015/djangocon-us-2015-but-why-is-the-admin-slow-by-jacinda-shelly/ to the list of content. While it is a bit old, it looks like it covers a core aspect of how to use the toolbar as a debugging tool.

[tim-schilling]

Never mind on tox -e docs. That is passing. Did you happen to generate the docs locally to see how the page gets rendered?

[dr-rompecabezas]

Yes, I built the docs locally to check that everything rendered correctly.

[tim-schilling]

🚀 Thank you @dr-rompecabezas!