Closed derberg closed 1 year ago
Hey @derberg Can I work on this.
@reachaadrika please 🙏
Hey @derberg I see no progress on this issue for 3 weeks Mind if I take it up?
@Ciggzy1312 please go ahead
@derberg Instead of yaml can't we use markdown in case studies similar to blogs.
Hey, I picked YAML instead of MD to get data in a structured way that is very easy to read in the front end so we can build different UIs out of one data set. now we just list all items from the YAML file in a given case study. Idea is that long term when we have many case studies, we can have a UI where we for example render only highlight on how different companies do schema versioning, or for example what are their use cases for AsyncAPI. So extracting info is much easier and user friendly, rather than you know, clicking through every case study one by one
@derberg I have further reduced the repeated codein the above PR. Do give me some suggestions if it can be improved further.
Reason/Context
Case study example: https://www.asyncapi.com/casestudies/adeogroup Code responsible for rendering: https://github.com/asyncapi/website/blob/master/pages/casestudies/%5Bid%5D.js Structure it operates on: https://github.com/asyncapi/website/blob/master/config/casestudies/adeo.yml
Some structures are arrays like: https://github.com/asyncapi/website/blob/master/config/casestudies/adeo.yml#L10 In this example you see that in case study we can have an array of contact points. But in code it is hardcoded to read only the first contact:
Description
Yeah just refactor the code to support rendering or all elements of the array wherever it is available.
company.contact
technical.languages
technical.frameworks
technical.protocols
asyncapi.versions
If there is some repetition, feel free to extract some code to reusable components