Adding sponsors to the docs.

[Kludex]

Discussed in https://github.com/encode/starlette/discussions/2695

^{Originally posted by **tomchristie** September 19, 2024} Quoting from #2680... > I'm making some changes to the Starlette documentation to make it more modern and appealing. > > I intend to do the same with Uvicorn, and I intend to add a sponsors tab. Yep, adding sponsors to the Starlette docs would be fantastic. I'd suggest [a unified approach across the encode docs](https://github.com/encode/template/issues/1)? Perhaps let's take an agile approach and deal with this incrementally. We could start with a unified approach for httpx, starlette, and uvicorn... * https://www.python-httpx.org/ (Docs have a sponsor tab) * https://www.uvicorn.org/ (Docs have a sponsor tab) * https://www.starlette.io/ Perhaps we could start with... * Use the same layout for the Starlette docs as Uvicorn and HTTPX. * Add "Fund Encode" links pointing to the [sponsorship page](https://github.com/sponsors/encode)?

[stankudrow]

Agree, need some help?

[lealre]

Just to clarify, when you mention a unified approach for httpx, Starlette, and Uvicorn, do you mean moving the navigation area from the top to the left sidebar, similar to what is done in httpx and Uvicorn? Is that correct?

Let me know if this is the right direction.

[Kludex]

On master, I've changed the layout of Starlette to match HTTPX.

I think we need to have a Sponsor section in the beginning, like Django REST Framework has.