Anonymitaet commented on PR #462:
URL: https://github.com/apache/pulsar-site/pull/462#issuecomment-1471059775

   @momo-jun thanks for your feedback!
   
   > Using "coming soon" looks good to me as long as the content can be 
available before the next feature release. If not, it may set higher 
expectations for users. WDYT?
   
   +1 since engineers (@maxsxu @nodece @ericsyh) plan to [contribute it to 
Pulsar in 
March](https://lists.apache.org/thread/bdmpdyq711znhsc2h73j9y9xl5ozjm26). In 
this case, the pros outweigh the cons. Hope this way can help us get some 
earlier feedback from users.
   
   ===================
   
   > Find a more prominent place in the left navigation for the ["Get started" 
page](https://pulsar.apache.org/docs/next/reference-cli-get-started/) of CLI 
tools, e.g., the "Tutorial" category. The content on the "Get started" page is 
a tutorial, while the "Reference" category serves as a dictionary.
   
   Ideally, there should be a specific guide called "Pulsar CLI" in parallel to 
"Pulsar API". This "Get Started" should be put in "Pulsar CLI > pulsar-admin" 
rather than ["Reference > CLI > Get 
started"](https://pulsar.apache.org/docs/next/reference-cli-get-started/) and 
["Tutorials"](https://pulsar.apache.org/docs/next/how-to-landing/). 
   
   Now the structure is in chaos somehow but I agree that relocating this "Get 
Started" to "Tutorials" is a better way as a temporary workaround. I'll do that.
   
   ===================
   
   > Nest the following topics under the "feature" to make the navigation menu 
MECE.
   
   These contents (in green box) should be optimized. +1 on this suggestion as 
a way to categorize contents logically temporarily. I'll move them.
   
   <img width="264" alt="image" 
src="https://user-images.githubusercontent.com/50226895/225478417-20c2cb38-f1e0-43ac-9bc0-6e2e850c7575.png";>
   


-- 
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]

Reply via email to