momo-jun opened a new issue, #18151: URL: https://github.com/apache/pulsar/issues/18151
### 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? Schema content is scattered and not easy to read and understand, including: 1. The overall Information Architecture can be better organized and reused. 2. Similar to the authentication section, the schema examples for multi-language clients can be incorporated into the `schema` chapter and only keeps a link in the `Client Libraries` chapter. ---- also has a dependency on this [client doc issue](https://github.com/apache/pulsar/issues/17302). 3. Administrative tasks using APIs should be relocated to the `Admin Interfaces` chapter. 4. Outdated content needs a revisit and refresh. ### What is your suggestion? WIP: The content mapping will be elaborated here soon by doing a structured redesign. ### Any reference? The applied methodology and expected outcome for refactoring the IA and content are similar to the following chapters: * [Functions](https://pulsar.apache.org/docs/next/functions-overview) implemented in https://github.com/apache/pulsar/pull/15975 * [Security](https://pulsar.apache.org/docs/next/security-overview) implemented in * https://github.com/apache/pulsar/pull/17615 * https://github.com/apache/pulsar/pull/17666 * https://github.com/apache/pulsar/pull/17808 * https://github.com/apache/pulsar/pull/18035 ### 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]
