[📑 Docs]: improve adeo case study

[derberg]

What Dev Docs changes are you proposing?

We have case study https://www.asyncapi.com/casestudies/adeogroup

• all links in https://github.com/asyncapi/website/blob/master/config/casestudies/adeo.yml and in https://github.com/asyncapi/website/blob/master/public/resources/casestudies/adeo/asyncapi.yaml that point to https://deploy-preview-921--asyncapi-website.netlify.app should be changed to https://asyncapi.com/
• in file https://github.com/asyncapi/website/blob/master/config/casestudies/adeo.yml under versioning extend the text to not only contain the current text but also show example of version of schema in an example like:

  {
    "namespace": "com.adeo.casestudy.costingrequest",
    "type": "record",
    "name": "CostingRequestPayload",
    "version": "1.1.0",
    "fields": [ ... ]
  }
  
  

Code of Conduct

• I agree to follow this project's Code of Conduct

[mediba123]

Update links: All links in the adeo.yml and asyncapi.yaml files that point to https://deploy-preview-921--asyncapi-website.netlify.app/ should be changed to https://asyncapi.com/.

[janvi01]

Hey @derberg I would like to work on this.

[AnimeshKumar923]

• in file https://github.com/asyncapi/website/blob/master/config/casestudies/adeo.yml under versioning extend the text to not only contain the current text but also show example of version of schema in an example like:

  {
    "namespace": "com.adeo.casestudy.costingrequest",
    "type": "record",
    "name": "CostingRequestPayload",
    "version": "1.1.0",
    "fields": [ ... ]
  }
  

I don't think this part has been resolved, as I've done nothing to this part of the issue. I currently don't have the required knowledge to work upon this. Require assistance...

[derberg]

2nd bullet point not implemented yet

[derberg]

@AnimeshKumar923 do you want to try to do it?

what basically has to be done is this versioning should be changed from one-line-string to multi-line-string

here you have an example of multiline string with code sample and the same has to be done. So current text:

Versioning is based on git tags. The schema version pushed to Confluent Schema Registry 
matches the git tag version of the product. Every schema has a `version` information 
that matches with product tag version.

and we need:

Versioning is based on git tags. The schema version pushed to Confluent Schema Registry 
matches the git tag version of the product. Every schema has a `version` information 
that matches with product tag version.

Example Avro schema with version information:
    ```json
    {
      "namespace": "com.adeo.casestudy.costingrequest",
      "type": "record",
      "name": "CostingRequestPayload",
      "version": "1.1.0",
      "fields": [ ... ]
    }
    ```

does that help?

[AnimeshKumar923]

@derberg

• Let me try that.
• Thank you for assistance.
• Will update about it.