remove pandas API from the documentation

[12rambau]

As suggested in the associated PR, I dropped the use of the pandas API to create the API page. Instead I kept the copy/pasted example (so that people know how it could look like when using templates).
Also I added an extra API page to the documentation to showcase the methods exposed by pydata_sphinx_theme.

Fix #1309

[drammock]

actually I just approved but it looks like this page is still there?

https://pydata-sphinx-theme--1330.org.readthedocs.build/en/1330/examples/example_pandas.html

[12rambau]

that was on purpose. This is entirely copy/pasted in our doc so whatever happens to pandas this page will continue to work. As it's a rather complete example of what a doc page could look like, I find it interesting to keep it.

What I focused on is the pages that were based on API doctrings i.e. raising error whenever pandas was updated.

I'm +1 to keep it.

[drammock]

that was on purpose. This is entirely copy/pasted in our doc so whatever happens to pandas this page will continue to work.

OK I understand that motivation, but the occasional changes to the expected warnings are not what #1309 complains about. It is about including docs from other packages in our own docs (irrespective of whether they're copy-pasted or "live"). And I think my points in #1309 still stand:

• Given how widely used the theme is now (>6k users according to GitHub) I feel like we can trust that someone will tell us if things don't look good in their API docs
• I'm dubious as to how diligent we are at scrutinizing those pages during PR reviews anyway

As it's a rather complete example of what a doc page could look like, I find it interesting to keep it.

OK but why not just look at https://pandas.pydata.org/docs/ then?

[12rambau]

OK but why not just look at https://pandas.pydata.org/docs/ then?

One could argue that we have no guarantee the pydata projects will always use the last version, unlike this page.

[drammock]

thx @12rambau