Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

extend current case study view with simplified adopters information #2135

Closed
derberg opened this issue Sep 11, 2023 · 3 comments · Fixed by #2232
Closed

extend current case study view with simplified adopters information #2135

derberg opened this issue Sep 11, 2023 · 3 comments · Fixed by #2232

Comments

@derberg
Copy link
Member

derberg commented Sep 11, 2023

Getting official case study is hard and takes months.

We need a "in-the-middle" solution that will still enable us to publicly capture different use cases from companies using AsyncAPI.

We need like a waiting room before actually case study is created.

I quickly mocked something nice and simple 👇🏼

Screenshot 2023-09-11 at 16 13 27

Links used in the mock


What do you think?

@Mayaleeeee
Copy link
Member

Getting official case study is hard and takes months.

We need a "in-the-middle" solution that will still enable us to publicly capture different use cases from companies using AsyncAPI.

We need like a waiting room before actually case study is created.

I quickly mocked something nice and simple 👇🏼

Screenshot 2023-09-11 at 16 13 27

Links used in the mock


What do you think?

This looks great, @derberg! ✈️ I love the arrangement too. However, it might be helpful to include a link within the '... a pull request' text that directs users to GitHub, making it easier for them to submit the PR.

@derberg
Copy link
Member Author

derberg commented Sep 12, 2023

@Mayaleeeee thanks

text that directs users to GitHub, making it easier for them to submit the PR

yup, definitely, a fixed link that will open the source file directly, I agree 💯

@derberg
Copy link
Member Author

derberg commented Sep 14, 2023

Also from technical point of view, data for the table should not be hardcoded in html, but stored in a new file called adopters.yml in yaml format, and then we need a script in scripts that handles yaml to json conversion using convertToJson util

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants