Yu

1. How about not deleting 2.8.1/2.8.2/2.8.3/2.9.1/2.9.2/2.9.3/2.10.1 docs since there might be some occurrences referencing them? We can just not show them. 2. How about adding some explanations for this PR...

> How about not deleting 2.8.1/2.8.2/2.8.3/2.9.1/2.9.2/2.9.3/2.10.1 docs since there might be some occurrences referencing them? We can just not show them. Keeping these obsolete docs may confuse contributors and lead...

> @Anonymitaet adding `deprecated` to those folders will change the URLs of doc pages, which also breaks the external references. If that's the case, I think I will also have...

Thanks for your contribution! LGTM from the technical writing perspective 😊

@momo-jun a soft reminder: here is a PR w/ doc-required label, could u pls follow up? Thanks

Feedback from @BewareMyPower: Hi, I'm reporting a bug of the new website again:joy:The rendering of the REST API is wrong. See https://pulsar.apache.org/docs/next/schema-manage/#topic-level. We can see `GET /admin/v2/topics/:tenant/:namespace/:topic`. However, the original...

@urfreespace OK, thanks!

@momo-jun I check some occurrences on `master`, and they do not function well. For example:  https://pulsar.apache.org/docs/next/admin-api-functions Can you take a look? Thank you!

@momo-jun your PR was merged 3 hours ago and the website build was done 4 hours ago, maybe that is the reason why the new changes do not take effect....

@momo-jun do you update all occurrences only for `master` or `master + other versions`?