tisonkun opened a new issue, #17409: URL: https://github.com/apache/pulsar/issues/17409
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### What issue do you find in Pulsar docs? The current [Get Started page for local cluster](https://pulsar.apache.org/docs/next/getting-started-standalone) is too much redundant than it should be. Most users want a short happy path to boot a Pulsar cluster and play with it by producing and consuming messages. Although, the current page begins the "Start Pulsar standalone" at almost 2/3 below the whole page. 1. We don't have to teach users to install JDK on M1. They can Google it, and there're a large portion of users who don't use M1. At least troubleshooting should go at last. 2. We don't have to mention how to install connectors or offloaders, it's unused on the quickstart page. We can mention them on the overview/quickstart page of connectors and offloaders. 3. We don't have to talk in detail about the layout of the binary release directory. It's intuitive and can be read from their name. 4. Currently, if you go through the page, you won't get the message consumed as it said. Because we don't even produce any message yet. Also, Pulsar CLI has some significant arguments to play with basic messaging, like how to consume from Earliest, how to keep consuming messaging instead of consuming only one message, and how to produce multiple messages in one turn. I have a draft to rewrite the section. ### What is your suggestion? I'll make a draft patch to cover all of the topics listed above in a few days. cc @merlimat @Anonymitaet @momo-jun @lhotari @codelipenghui ### Any reference? _No response_ ### Are you willing to submit a PR? - [X] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
