Tracking Issue for Moving Source of Docs to the Site Repo

[tisonkun]

Search before asking

• I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?

Mailing thread: https://lists.apache.org/thread/89wl112cflvtoyfg3l7kglr1dozsljm9

What is your suggestion?

1. Move the website's content to the root level, then we have a first-class Docu&yarn-based JS project layout. It's more convenient and familiar to related developers.
2. Host the source of docs in the site repo (apache/pulsar-site) instead of under site2 folder in the main repo and do content sync.

• Migrate build site scripts to pytools #19186
• Stop sync docs from the main repo #19091
• Remove docs from the main repo #19092
• Lift site folder to the top level #19090
• Install Ducoment bot for the site repo #19103
• Update contribution guide according to the move of source of docs #19111
• Add build stage without push in the site pre-commit workflow #19185
• [Doc][improve] Auto-detect broken links and integrate into CI process #18026
• Re-evaluate navbar. Certain topics deserve to be more prominent, like the security, use cases, and ecosystem.

Any reference?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[tisonkun]

Closed as all subtasks are done.

@michaeljmarshall I think the navbar issue is not strongly related to this movement; maybe I will create a new issue later.