docs: fix invalid links in markdown files (#756)

Co-authored-by: Akshat Nema <[email protected]> Co-authored-by: Alejandra Quetzalli <[email protected]> Co-authored-by: Maciej Urbańczyk <[email protected]>
asyncapi · Nov 26, 2022 · e6b1897 · e6b1897
1 parent 9931574
commit e6b1897
Show file tree

Hide file tree

Showing 50 changed files with 286 additions and 243 deletions.
diff --git a/README.md b/README.md
@@ -1,16 +1,20 @@
-[![AsyncAPI Banner and Logo](/public/img/logos/github-repobanner-website.png)](https://www.asyncapi.com)
+[![AsyncAPI Banner and Logo](./public/img/logos/github-repobanner-website.png)](https://www.asyncapi.com)
 
 ---
+
 <!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->
+
 [![All Contributors](https://img.shields.io/badge/all_contributors-34-orange.svg?style=flat-square)](#contributors-)
+
 <!-- ALL-CONTRIBUTORS-BADGE:END -->
+
 [![Netlify Status](https://api.netlify.com/api/v1/badges/b2137407-b765-46c4-95b5-a72d9b1592ab/deploy-status)](https://app.netlify.com/sites/asyncapi-website/deploys)
 
 ## Overview
 
 This repository contains the sources of AsyncAPI website:
 
-- It's powered by [Next.js](https://nextjs.org/), 
+- It's powered by [Next.js](https://nextjs.org/),
 - It uses [Tailwind](https://tailwindcss.com/) CSS framework,
 - It's build and deployed with [Netlify](https://www.netlify.com/).
 
@@ -44,14 +48,16 @@ You can access the live development server at [localhost:3000](http://localhost:
 #### Compose a new blog post
 
 To bootstrap a new post, run this command:
+
 ```bash
 npm run write:blog
 ```
 
 Follow the interactive prompt to generate a post with pre-filled front matter.
 
 ### Spin up Gitpod codespace
-In order to prepare and spin up a Gitpod dev environment for our project, we configured our workspace through a [.gitpod.yml](/.gitpod.yml) file.
+
+In order to prepare and spin up a Gitpod dev environment for our project, we configured our workspace through a [.gitpod.yml](./.gitpod.yml) file.
 
 To spin up a Gitpod codespace, go to http://gitpod.io/#https://github.com/asyncapi/website.
 

diff --git a/mlc_config.json b/mlc_config.json
@@ -0,0 +1,14 @@
+{
+  "aliveStatusCodes":[200,429,999,403],
+  "ignorePatterns": [
+    {
+      "pattern": "^(https://www.postman.com/company/careers/|#|http://localhost|http://www.fmvilas.com|https://github.com/issues?)"
+    }
+  ],
+  "replacementPatterns": [
+    {
+      "pattern": "^/",
+      "replacement": "https://www.asyncapi.com/"
+    }
+  ]
+}
diff --git a/pages/about/index.md b/pages/about/index.md
@@ -26,7 +26,7 @@ In doing so, we achieve:
 - Making the project as democratic as possible.
 - Relying on an asynchronous decision-making process that empowers the people who "work," not the companies who "pay." 
 
-In other words, it [gives equal power to individual and corporate contributors](/blog/governance-motivation).
+In other words, it [gives equal power to individual and corporate contributors](https://www.asyncapi.com/blog/governance-motivation).
 
 ## Maintainers 
 
@@ -44,8 +44,8 @@ We apologize in advance if we failed to recognize your work. Feel free to contac
 
 ## AsyncAPI, in numbers
 Interested to know more about our growth? Feel free to check our annual summary report: 
-- [Summary report 2020](/blog/2020-summary)
-- [Summary report 2021](/blog/2021-summary)
+- [Summary report 2020](https://www.asyncapi.com/blog/2020-summary)
+- [Summary report 2021](https://www.asyncapi.com/blog/2021-summary)
 
 ## Companies support
 
@@ -64,7 +64,7 @@ The total number of companies and projects using AsyncAPI as well as their ident
 - [**Salesforce**](https://login.salesforce.com/?locale=es): Business consultancy company. It provides (CRM) services and more. It manages from small businesses to FORTUNE 500 companies, and it has more than 150,000 customers.
 - [**IBM**](https://www.ibm.com): Company that manufactures and markets hardware and software. It has operations in over 170 countries and provides hosting and consulting services in many areas.
 - [**SAP**](https://www.sap.com/index.html): Company dedicated to the design of computer products for business management. Develops business software to manage operations and business-to-customer relationships. It’s a large company with 100,330 employees.
-- [**IQVIA**](https://www.iqvia.com/"): Company providing services for the combined health information technology and clinical research industries. It employs more than 58.000 people in over 100 countries.
+- [**IQVIA**](https://www.iqvia.com/): Company providing services for the combined health information technology and clinical research industries. It employs more than 58.000 people in over 100 countries.
 
 ## Values of AsyncAPI
 
@@ -90,8 +90,8 @@ All the information about the project's economy, the amount of the donations, th
 [**[email protected]**](mailto:[email protected]).
 - [**Twitter**](https://twitter.com/asyncapispec?lang=es): It's used for disseminating all news and information regarding the project, resolving user queries, and sharing the latest updates within AsyncAPI.
 - [**Slack workspace**](https://www.asyncapi.com/slack-invite): The main place of encounter for the whole community of AsyncAPI.
-- [**Newsletter**](https://www.asyncapi.com/subscribe/): To learn about the status of the project, news, actualizations, recorded events, and meetings.
-- [**Blog**](/blog): It’s used to disseminate information related to the project. It's also open to collaborations.
+- [**Newsletter**](https://www.asyncapi.com/newsletter): To learn about the status of the project, news, actualizations, recorded events, and meetings.
+- [**Blog**](https://www.asyncapi.com/blog): It’s used to disseminate information related to the project. It's also open to collaborations.
 - [**LinkedIn**](https://es.linkedin.com/company/asyncapi): It's used to publish news related to the project or its environment. It’s also used as a source of information.
 - [**YouTube Channel**](https://www.youtube.com/playlist?list=PLbi1gRlP7pijUwZJErzyYf_Rc-PWu4lXS"): Where you can find conferences, AsyncAPI Open Meetings, and much more.
 - [**GitHub**](https://github.com/asyncapi): Issues (bugs, feature requests, etc.) and pull requests (PRs) for fixes or new features already discussed, as per the contributing guidelines.

diff --git a/pages/blog/2021-summary.md b/pages/blog/2021-summary.md
@@ -17,7 +17,7 @@ This article is a continuation of a tradition where once a year, we summarize al
 
 It is good to see how we are doing, how are we growing :rocket:
 
-If you are interested in previous years, look at [this 2020 summary article](2020-summary).
+If you are interested in previous years, look at [this 2020 summary article](https://www.asyncapi.com/blog/2020-summary).
 
 ## Slack
 
@@ -529,7 +529,7 @@ The increase in numbers is insanely huge. People automatically say that it is be
 Let me challenge you:
 - Corporations always use mirrored versions in npm. When you work on a project in a corporate network, you will always hit internal proxy. Not included in downloads.
 - Most build systems cache packages that are downloaded already to improve performance. Not included in downloads.
-When you work with npm locally, you also have a local cache that is used if you want to install something that you already installed. Not included in downloads.
+ When you work with npm locally, you also have a local cache that is used if you want to install something that you already installed. Not included in downloads.
 
 An interesting observation is that Generator uses Parser and Parser uses the package with AsyncAPI specs. So you can read from this data that packages with specs are primarily used in the AsyncAPI Parser. You can also see that Parser is a backbone for many more projects than just the AsyncAPI Generator.
 
@@ -663,6 +663,7 @@ We grow. Numbers just confirm our observation. We grow not only because people l
 If you want to look at more data, some of it is available [in this spreadsheet](https://docs.google.com/spreadsheets/d/1KxEkX9BqtJ4WIkh-NMftq5pDTcBStV_pHqa6P6-7bfM/edit?usp=sharing) and for others you just need to contact me directly. 
 
 In 2022, we need to establish a stronger bond with the community. We have many folks that give back a lot of time into the project, and it is time to give back. The main goals we have:
+
 - Meet in person for AsyncAPI Conference
 - Setup Ambassador program to give back to most active community members
 - Get involved in more events like Google Summer of Code

diff --git a/pages/blog/2022Q1-summary.md b/pages/blog/2022Q1-summary.md
@@ -56,7 +56,7 @@ We need to have a special task force that will focus on the subject. Please join
 Because of the community's growth and the growing number of topic-specific meetings, we had to spend some time improving things and automating as much as possible. After some initial discussions, such as [this discussion about Google-services](https://github.com/asyncapi/community/discussions/236), some initial requirements were defined, called [Meeting as a Service](https://github.com/asyncapi/community/issues/245).
 
 - A week ago, we stopped using our `asyncapi-users` Google Group. We removed it, and all the members were migrated as subscribers to the AsyncAPI Newsletter. This newsletter is the new place where we'll send email notifications every Monday morning with a list of upcoming meetings.
-- We switched to the new Google Calendar instance managed by the official AsyncAPI Google account. You should remove/unsubscribe from the old calendar and [subscribe to the new calendar](https://calendar.google.com/calendar/u/3?cid=Y19xOXRzZWlnbG9tZHNqNm5qdWh2YnB0czExY0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t),
+- We switched to the new Google Calendar instance managed by the official AsyncAPI Google account. You should remove/unsubscribe from the old calendar and [subscribe to the new calendar](https://calendar.google.com/calendar/u/0/[email protected]),
 - [Our Technical Steering Committee (TSC)](https://github.com/asyncapi/community/discussions/295) approved to sponsor 8 Zoom licenses to host official AsyncAPI meetings. So far, only 3 licenses have been assigned. We have lots of room for more meetings and hosts, if there is a need.
 
 Huge thanks to [Krishna Kumar](https://github.com/Krishks369) and [Shreyansh Jain](https://github.com/sudoshreyansh), who helped research the implementation. :heart:

diff --git a/pages/blog/april-2021-at-asyncapi.md b/pages/blog/april-2021-at-asyncapi.md
@@ -32,7 +32,7 @@ I'm super happy to share that we removed the last roadblock for the next AsyncAP
 
 I hope you noticed a pattern. We do not want to do releases during the summer holidays and stay away from December :smiley:.
 
-In June 2021, we will release 2.1.0 version of the specification. It is going to be the first release under [open governance model](https://github.com/asyncapi/.github/blob/master/CHARTER.md), under Linux Foundation and new [contribution guide](https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md). So many new things, a lot to organize around. It means we probably won't accept too many changes as logistics will consume a lot of time. We welcome any help. Join our [Slack](https://www.asyncapi.com/slack-invite/) for more details. 
+In June 2021, we will release 2.1.0 version of the specification. It is going to be the first release under [open governance model](https://github.com/asyncapi/community/blob/master/CHARTER.md), under Linux Foundation and new [contribution guide](https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md). So many new things, a lot to organize around. It means we probably won't accept too many changes as logistics will consume a lot of time. We welcome any help. Join our [Slack](https://www.asyncapi.com/slack-invite/) for more details. 
 
 ## AsyncAPI use case at eBay
 
@@ -86,7 +86,7 @@ Since we were getting more and more questions about using WebSocket with AsyncAP
 * Blog post on [Creating AsyncAPI for WebSocket API - Step by Step](https://www.asyncapi.com/blog/websocket-part2)
 * And soon I'll release the last blog post on [From API-First to Code Generation - A WebSocket Use Case](https://github.com/asyncapi/website/pull/237) 
 
-In addition, you can have a look at [official WebSocket example](https://github.com/asyncapi/spec/blob/master/examples/2.0.0/websocket-gemini.yml).
+In addition, you can have a look at [official WebSocket example](https://github.com/asyncapi/spec/blob/master/examples/websocket-gemini.yml).
 
 There is also a [live stream](https://www.youtube.com/watch?v=8tFBcf31e_c) I did about this topic. I will also present at [EDASummit](https://edasummit.com/) on 19th of May and most probably at [APIOps Helsinki](https://www.meetup.com/Apiops-Helsinki/) someday around mid-June. Stay tuned.
 

diff --git a/pages/blog/async-api-spec-3.0-release.md b/pages/blog/async-api-spec-3.0-release.md
@@ -46,11 +46,11 @@ AsyncAPI is a community-driven project and we welcome all kinds of contributions
 
 To better understand AsyncAPI and how the Spec 3.0 release will play out, we recommend watching our [past meeting recordings](https://www.youtube.com/watch?v=CLNgLB4-UnA&list=PLbi1gRlP7pihClJY-kXuTRRJ8n1awb0VV). To know how you can contribute, we recommend checking out our [contributing guidelines](https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md). If you wish to keep track of all the work that is happening on the Spec 3.0 release, we recommend checking out our [GitHub issue](https://github.com/asyncapi/spec/issues/691).
 
-Before landing in your contributions, make sure you follow our [Code of Conduct](https://github.com/asyncapi/.github/blob/master/CODE_OF_CONDUCT.md) and the pull request you raised is [described properly](https://github.com/asyncapi/.github/blob/master/CONTRIBUTING.md#conventional-commits). To know how we collaborate using Git & GitHub, follow the [Git workflow](https://github.com/asyncapi/.github/blob/master/git-workflow.md) that we have developed for contributors.
+Before landing in your contributions, make sure you follow our [Code of Conduct](https://github.com/asyncapi/.github/blob/master/CODE_OF_CONDUCT.md) and the pull request you raised is [described properly](https://github.com/asyncapi/.github/blob/master/CONTRIBUTING.md#conventional-commits). To know how we collaborate using Git & GitHub, follow the [Git workflow](https://github.com/asyncapi/community/blob/master/git-workflow.md) that we have developed for contributors.
 
 ## When will the release happen?
 
-We are yet to arrive at a date but the community is working towards releasing this by the end of 2022. Currently, we meet every two weeks to discuss the upcoming Spec 3.0 release and share updates and you are welcome to join it! We are going to have our next meeting on [UTC 16:00 on March 16, 2022](https://github.com/asyncapi/community/issues/270). You can access the [AsyncAPI Calendar](https://calendar.google.com/calendar/u/0/embed?src=tbrbfq4de5bcngt8okvev4lstk@group.calendar.google.com) and explore our upcoming meetings.
+We are yet to arrive at a date but the community is working towards releasing this by the end of 2022. Currently, we meet every two weeks to discuss the upcoming Spec 3.0 release and share updates and you are welcome to join it! We are going to have our next meeting on [UTC 16:00 on March 16, 2022](https://github.com/asyncapi/community/issues/270). You can access the [AsyncAPI Calendar](https://calendar.google.com/calendar/u/0/embed?src=c_q9tseiglomdsj6njuhvbpts11c@group.calendar.google.com) and explore our upcoming meetings.
 
 The release will happen gradually, where the new specification and tooling will live in coexistence until there is a collective consensus that everything is ready. This gives everyone an easy way to test out the new changes and provide feedback before the release. Finally, after rigorous testing, we will make an official announcement about our release!
 

diff --git a/pages/blog/async_standards_compare.md b/pages/blog/async_standards_compare.md
@@ -11,7 +11,7 @@ tags:
 authors:
    - name: Jesse Menning
      photo: /img/avatars/jmenning.webp
-     link: https://linkedin.com/in/jmenning
+     link: https://www.linkedin.com/in/jmenning
      byline: CTO Architect at Solace
 ---
 
@@ -93,4 +93,4 @@ Once completed, OpenTelemetry helps to answer the classic event-driven question
 
 It’s a great time for event-driven architecture. Challenges that used to be overcome in different ways in every implementation are now being addressed by standard, open-source solutions. While OpenTelemetry, AsyncAPI and CloudEvents do have overlapping capabilities, they are distinct enough to all warrant a place in your DevOps processes.
 
-If you have more questions or want to share your experience with these standards, you can let us know in the [AsyncAPI Slack](https://asyncapi.com/slack-inviteyou) or the [Solace Community Forum](http://solace.community/). 
+If you have more questions or want to share your experience with these standards, you can let us know in the [AsyncAPI Slack](https://www.asyncapi.com/slack-invite) or the [Solace Community Forum](http://solace.community/).