Added Fellow call for applicant banner.

[sarahboyce]

Homepage:

Documentation:

---

Note that we can put it in more places but I think this is a reasonable start
This idea came from @knyghty when I mentioned that blog articles can get "lost" if we have several posts

[alexgmin]

I'm assuming this should have been an <h1> from the start instead of a <p>?

[sarahboyce]

Well spotted, it should be a <p> tag. Bad copy and paste from a previous commit 👍

[SaptakS]

I feel putting the call for applicant link in the same space as "Documentation" with a dash might not be the best UI (I personally feel I would be confused, since I would think that the text after dash usually would denote an internal page title).
Maybe something more like this makes sense? Thoughts?:

[sarahboyce]

I feel putting the call for applicant link in the same space as "Documentation" with a dash might not be the best UI (I personally feel I would be confused, since I would think that the text after dash usually would denote an internal page title). Maybe something more like this makes sense? Thoughts?:

This works!
I was copying what we have done previously for the PyCharm banner.

We do occasionally want to have this banner/CTA encouraging folks to do something (apply, donate, survey etc) so if you want to improve the design, I'm happy for you to suggest/push changes

I am hoping we put this in place by the end of the week 👍

[sabderemane]

Hey @sarahboyce 🤗
I join @SaptakS 's feedback and I have few additional feedbacks but I think it might better to provide them in the issue to ease the addition of a banner for every case, so we can merge this one to have it ASAP since the announcement was quite recent and we can improve the design and code for the PR in another PR 👌🏽

Does it render well in dark theme?

[SaptakS]

@sabderemane makes sense to me.

Does it render well in dark theme?

The background color doesn't change unlike the copy-banner, but renders fine apart from that.

[SaptakS]

I am going to approve and merge this PR given the urgency, and as mentioned in the comments, discuss a better approach for banners in a separate PR, that can be reused for later uses.