WEB: standardized footer GH48012 
- [ ] closes #48012 
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
Ups, I ended up updating the PR before I intended.  I wanted to merge the commits into a single commit with a better name :/ Sorry for that > Ups, I ended up updating the PR before I intended. I wanted to merge the commits into a single commit with a better name :/ Sorry for that

Don't worry about it, we squash all the commits into one when we merge PRs, so it doesn't add much value to squash them before. And in some cases it's useful to have separate commits, so we don't need to review everything again, and can check just what changed.

Checking your changes, I'm wondering if it'd make sense to have the footer content for the website in the configuration yaml. I think we the whole config to the context, so not much change would be needed, except for the year. For it, a simple content preprocessor that replaces a string like `{year}` by the current year could be used. I think this could be a bit better than the javascript. But happy to use the javascript if you have a strong preference for it.

For Sphinx, is Sphinx adding the word `Copyright` automatically? That's annoying, quite a poor design decision in my opinion. If you want to have a quick look and see if there is an easy way to overwrite that, it would be great. But I wouldn't spend too much time on it, Sphinx code is a huge mess. I opened #48543 to update the footer for the docs, as we want to have it merged before the release on Monday. I'll let you continue here with the update for the website, which is independent from the release. @datapythonista hi, sorry just wanted to let you know that I started working today and have a lot to do now. If it is something with a deadline please go ahead. Otherwise, I might take a while (like a couple of weeks) :) No problem, thanks for letting us know. If I have the time to look at this before you, I'll let you know and close this PR. Thanks for the work on this! Superseded by #48557

Thanks @FrnRmn for the work on this.