momo-jun commented on issue #19912:
URL: https://github.com/apache/pulsar/issues/19912#issuecomment-1485194859
Hi Asaf, thanks for proposing this improvement. Generally it looks good. I
support the motivation.
Structure-wise, I have a couple of questions.
1. Is it the TOC inside an all-in-one topic or the TOC of the left
navigation? In other words, did you plan to provide an all-in-one Getting
Started topic covering three subheadings, or three topics for three specific
types of readers? It seems to be one topic in your proposal, which may blur the
learning path of different roles. For example, as an operator, will they still
go through `Consume and Produce messages using the CLI` or jumpstart from
`Deploy helm charts to k8s`?
2. What is the content mapping of existing topics? IIUC, the new structure
covers the following three topics. What's your plan to do with `Docker Compose`?
```
1. Consume and Produce messages using the CLI // containing both
`getting-started-standalone` and `getting-started- docker`
2. Get started for Devs
4. Get started for Ops // containing `getting-started-helm`
```
--
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]
