SatyamPandey-07 opened a new issue, #12154: URL: https://github.com/apache/seatunnel/issues/12154
### Search before asking - [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. ### Description According to the SeaTunnel connector documentation specifications (issue #4544), connector documentation pages should maintain consistent structure across the repository, including explicit engine compatibility sections (## Support Those Engines in English, ## 引擎支持 in Chinese) and practical FAQs addressing frequent configuration scenarios. Currently, several connector documents lack these standard engine support sections and FAQ guidance in both English and Chinese: - RabbitMQ (docs/en/connectors/source/Rabbitmq.md, docs/en/connectors/sink/Rabbitmq.md, docs/zh/connectors/source/Rabbitmq.md, docs/zh/connectors/sink/Rabbitmq.md) - Milvus (docs/en/connectors/source/Milvus.md, docs/en/connectors/sink/Milvus.md, docs/zh/connectors/source/Milvus.md, docs/zh/connectors/sink/Milvus.md) - Email (docs/en/connectors/sink/Email.md, docs/zh/connectors/sink/Email.md) This issue proposes standardizing these 10 documentation files by adding: 1. Explicit engine support matrices (Spark, Flink, SeaTunnel Zeta). 2. Comprehensive FAQs addressing common operational questions (parallelism constraints, vector data types, gRPC rate limits, attachment formats, and error handling). ### Usage Scenario Users exploring SeaTunnel connectors can quickly determine engine compatibility at a glance and resolve common configuration questions without having to inspect Java connector source code. ### Related issues #4544 ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
