asafm commented on issue #19912:
URL: https://github.com/apache/pulsar/issues/19912#issuecomment-1485347249
Thanks for the feedback @momo-jun.
From the looks of it, the doc website allows 2 depth level, that means the
left pane will have:
Getting Started Guide
- Consume and Produce messages using the CLI
- Developer Getting Started
- Operator Getting Started
Then each section will have the heading it contains per the TOC (depth level
3 will be H1, ...).
Regarding your second question on what to do with existing Getting Started
section.
Running pulsar locally and Docker is included in the CLI section.
running pulsar in K8s is included in Operator Getting Started
"Run a Pulsar cluster locally with Docker Compose" is actually missing
How about to tackle this we'll change the TOC to:
- `1.1 Starting Pulsar locally`
- `1.1.1. Standalone mode`
Here we’ll explain the standalone mode and explain two ways to start
pulsar on your development machine. In each section, we’ll show how to view the
logs to check if Pulsar started ok.
- `1.1.1.1 Using release binary`
- `1.1.1.1.1. Downloading`
- include a very short description of the various folders
you unpacked (one paragraph tops)
- `1.1.1.1.2. Running`
- `1.1.1.2. Using Docker`
- `1.1.2. Cluster mode (Docker Compose)`
Here we’ll take the content we have on the site showing how to start
a Pulsar Cluster locally using Docker compose
--
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]
