-
-
Notifications
You must be signed in to change notification settings - Fork 638
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
chore(blog): adding 3 New Articles as Blog Posts #1805
Conversation
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-1805--asyncapi-website.netlify.app/ |
|
||
- First write the OpenAPI definition, collaborating between API providers and API consumers. | ||
- Then use OpenAPI Generator, either the maven plugin or a CLI, to generate some DTOs and interfaces from your OpenAPI definition. | ||
- Implementing the generated interfaces you can create a service for the API. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Implementing the generated interfaces you can create a service for the API. | |
- You can create a service for the API by implementing the generated interfaces. |
@alequetzalli please help with the final editorial review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ivangsa @thulieblack, we already have published versions of the blog, why there is a need to republish it via the AsyncAPI website? We can add the required articles/blogs in newsroom section as well.
Hey @akshatnema, we are reposting them onto the blog, but if newsroom is the way to go, then it should be fine 👌🏿 |
I got the suggestion to repost it to the blog similar to this PR https://github.com/asyncapi/website/blob/master/pages/blog/openapi-vs-asyncapi-burning-questions.md?plain=1#L6 |
I think Lukasz once mentioned how we could repost and use canonical something something, @derberg |
We have multiple ways to do that, it's important that in which way we are getting more exposure to our content. So, probably @derberg will give proper insights on it. But to the fact that, Articles which are not part of AsyncAPI blog should be present inside Article section of Newsroom page, else we don't have any other usage for that component. |
@akshatnema the newsroom is fine for articles from authors that do not wish to repost but if author wants to repost, and we already support |
Hey, At least 1 approving review is required to merge this pull request. |
Yeah I think since everything has been cleared up, we can merge this cc @derberg |
maybe the publish date for articles should be updated to more recent? like schedule it for next week so we do not release them this week when July update comes up? |
makes sense. will schedule for next week then |
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
Thanks @thulieblack for making our life easier!! <3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's get this merged!!
/rtm |
Description
Adding three new articles about AsyncAPI spec from zenwave... Their medium versions are:
Related issue(s)