[Docs] Refactor Rocketmq documentation

[kaori-seasons]

At present, because rocketmq-site does not display according to the version number released by rocketmq, when users use it, they do not know whether a configuration item has been upgraded. Refer to kafka-site and pulsar-site。. Currently decided to refactor the 4.x version of the documentation

The work to be done in the first stage is as follows

1. Organize the configuration documents of the broker and client modules, and confirm with the community
2. Confirm the unit test of the broker and the client, and run the example. Locating and explaining key classes
3. Organize the documentation of nameserver

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

4. If there are some sub-tasks involved, use -[] for each sub-task and create a corresponding issue to map to the sub-task:

• sub-task1-issue-number: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

[LXPWing]

Cool I want to try it

[kaori-seasons]

Cool I want to try it

The tasks are being split recently, and it is expected that the specific sub-tasks will be improved before next Friday

[kaori-seasons]

According to the current release order of rocketmq, the documents of four versions of 4.6, 4.7, 4.8 and 4.9 are sorted at this stage. The official website homepage document is re-divided into five guide items: Quickstart , Configuration , Performance , Operations, Clients and API Docs Refer to the initial version of kafka (0.7) documentation Give an example of producer and consumer, and update the histogram of throughput comparison according to the stress test results

Currently only refactoring documentation for 4.9.3

• [ ] The client part is used to sort out the exmaples on the official website, such as sequence message examples, broadcast message examples, timing message examples, batch message examples, filter message examples, transaction message examples, etc. show here
• [ ] Design documentation reference here
• [ ] Operation document reference here
• [ ] Create a new tab named Use case, and combine the practice case of these with the practice case of Documentation
• [ ] Supplement API Docs document Currently client is only configured as Producer Configuration Hope to be able to follow the supplementary notes by flipping through the unit tests

[github-actions[bot]]

This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs.

[github-actions[bot]]

This issue was closed because it has been inactive for 3 days since being marked as stale.