THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
The website documentation of Kafka reside in a few different places.
Kafka Code Repository
...
- Kafka code repo has a /docs directory with the latest revision of the docs (not multiple versions, just one that matches the latest state of code).
- When you submit a code patch that requires doc modification, you modify all relevant files in same patch and they get reviewed and committed together (ideally).
- When you submit a doc patch alone, you modify all relevant files in docs/ directory and submit a patch.
- Broker/new producer/new consumer configuration docs are auto-generated from code. So for any changes, you need to modify the relevant java files (KafkaConfig.java, ProducerConfig.java, ConsumerConfig.java etc).
- Follow Contributing Code Changes for submitting above doc changes using Github pull requests.
- When we release, we copy the docs matching the release and commit to website git repo. We also do this occasionally to fix bugs in earlier docs.
- For older releases, contribute changes to the relevant branch of the release code repository and this will be pushed to the website git repo as needed.
Kafka Website Repository
- The website git repo hosts some of the Kafka website pages that are not included in the Kafka code repository.
- In some cases, like hot fixes, non-technical web page changes, we accept Github pull requests against website git repo.
Wiki Pages
- Some documentation are simply wiki pages. In that case, we simply modify the wiki pages. (You may need permission to modify the wiki pages. Please send email to dev@kafka.apache.org or users@kafka.apache.org asking for the permission.)