diff --git a/markdown/blog/2024-august-summary.md b/markdown/blog/2024-august-summary.md
index 477210de06a1..368cef32c319 100644
--- a/markdown/blog/2024-august-summary.md
+++ b/markdown/blog/2024-august-summary.md
@@ -11,7 +11,6 @@ authors:
link: https://www.linkedin.com/in/v-thulisile-sibanda/
byline: AsyncAPI Community Manager
excerpt: 'August Community Update'
-featured: true
---
The summer holidays are almost over, but the community hasn't slowed down. We've been receiving great news, and I'm thrilled to share that our list of sponsors is growing.
diff --git a/markdown/blog/2024-september-summary-and-london.md b/markdown/blog/2024-september-summary-and-london.md
new file mode 100644
index 000000000000..cbac4f5563ed
--- /dev/null
+++ b/markdown/blog/2024-september-summary-and-london.md
@@ -0,0 +1,200 @@
+---
+title: "September Community Update And AsyncAPI Conference London 2024"
+date: 2024-10-02T06:00:00+01:00
+type: Communication
+tags:
+ - Project Status
+cover: /img/posts/2024-blog-banner/blog-banner-september.webp
+authors:
+ - name: Thulisile Sibanda
+ photo: /img/avatars/thulieblack.webp
+ link: https://www.linkedin.com/in/v-thulisile-sibanda/
+ byline: AsyncAPI Community Manager
+excerpt: 'September Community Update and London Conference Highlights'
+featured: true
+---
+
+In September, we had our second in-person AsyncAPI conference after Helsinki; read all about it in the [AsyncAPI Helsinki Conference update](https://www.asyncapi.com/blog/helsinki-and-community).
+
+This time, I had the privilege of being present in person. First and foremost, I would like to thank [Gravitee.io](https://www.gravitee.io/) and to [Georgie Burrows](https://www.linkedin.com/in/georgieburrows/) for sponsoring the AsyncAPI Conference. Their sponsorship enabled me to cover the visa expenses and travel costs. I also want to express my gratitude to [Lukasz Gornicki](https://www.linkedin.com/in/lukasz-gornicki-a621914) for his support and assistance throughout the process. It wasn't easy, but in the end, it was an incredible achievement for all of us, especially for me.
+
+## AsyncAPI Conference London Edition 2024
+This year's London Edition was made possible by the amazing folks at [APIdays](https://www.apidays.global/), and we were part of the 2-day APIdays London Conference. The AsyncAPI track took place on the first day, and we had an incredible lineup of speakers and talks that attracted an entire room of attendees.
+
+
+
+Lorna started things off with a session on Better AsyncAPI Governance and how to devise sensible standards that support usability, security, and reliability.
+
+
+
+Artur followed with a demonstration on harmonizing NATS, CloudEvents, and AsyncAPI to build scalable, robust, and maintainable systems.
+
+
+
+Eduardo then shared a success story on how using AsyncAPI helps build API management platforms that enable event-driven architectures across domains by decoupling producers and consumers without compromising data contracts between parties.
+
+
+
+Later, Swen spoke on lessons we can learn from synchronous API design and architecture.
+
+
+
+During the break, the `API Specs and Standards Booth` was busy with people interested in what the AsyncAPI Initiative is all about and the work we do.
+
+
+
+Dale gave a session on how much information you need to know to design a solution around Kafka topics and illustrated the critical additional information a provider of an asynchronous API needs to provide.
+
+
+
+Laurent shared how to use Microcks ready to work with Testcontainers to provide solutions for mocking and testing APIs without extensive coding.
+
+
+
+Will then demonstrated how Architecture as Code and AsyncAPI work together to create deployable environments for production and the deployment of WebSocket-based APIs in a financial organization.
+
+
+
+Sho ended the day by taking us on a journey on how to build a cross-exchange trading bot and how AsyncAPI has the proper tooling to tackle pain points such as document inconsistency and missing language support.
+
+
+
+All the talks were incredible, and even the questions asked during the sessions were very insightful. Some of the slide presentations and recordings will soon be available under the [Resources Hub at the AsyncAPI Conference website](https://conference.asyncapi.com/).
+
+### API Specs And Standards Booth
+We teamed up with the OpenAPI Initiative team at the booth and had many insightful conversations.
+The first day was bustling with activity, and it was interesting to see how many people were not familiar with AsyncAPI and the community.
+They were very intrigued by how a bunch of folks with diverse expertise and skills from different continents and companies came together to represent AsyncAPI despite having never met. Our maintainers and ambassadors did a fantastic job educating and answering questions about the community, specification, and tooling.
+
+
+Day 2 at the conference was calmer and less busy than the first day, but we had the opportunity to visit other booths and get some contacts for the future.
+
+
+
+I would like to thank the experts for taking their time at the conference and volunteering at the `API Specs and Standards Booth`.
+
+
+
+## AsyncAPI Conf in Paris
+As you can tell, London was a success, and now there's an opportunity to be part of another fantastic AsyncAPI conference in Paris. [The Call for Proposals for Paris](https://conference.asyncapi.com/venue/Paris) will soon close on the 12th of October, and we encourage anyone to apply.
+
+## AsyncAPI Bounty Program
+This month, we celebrate a significant milestone: the first anniversary of the official launch of the AsyncAPI Bounty Program. Our goal has been and continues to recognize and reward the efforts of our maintainers and contributors and to challenge the notion that contributing to Open Source is always free. You can learn about the history of the AsyncAPI Program from [the redistribution of Open Collective funds discussion](https://github.com/orgs/asyncapi/discussions/541#discussioncomment-5462792).
+
+As a community, we have greatly benefited from the program. For example, we have used the AsyncAPI Cheat Sheet at conferences, saved costs on Digital Ocean, and implemented an automated TSC voting process. For more details, [please read the AsyncAPI Bounty Program Summary](https://www.asyncapi.com/blog/asyncapi-bounty-program-2024).
+
+Kudos to [Viacheslav Turovskyi](https://github.com/aeworxet) (Ash) for his outstanding work in leading and managing the initiative smoothly.
+
+## AsyncAPI Mantainership Program
+The Maintainership Program is progressing well; we have received some excellent project ideas. Once the project ranking is complete, we will announce the call for applications soon.
+
+Keep an eye on the `#09_mentorships` Slack channel for the exact dates. For details on the submitted projects, [please take a look at the Mentor/Maintainership discussion](https://github.com/orgs/asyncapi/discussions/1361).
+
+## AsyncAPI Ambassador
+We are excited to welcome [Lorna Mitchell](https://www.linkedin.com/in/lornajane), VP of Developer Experience at Redocly, to the [AsyncAPI Ambassador Program](https://www.asyncapi.com/community/ambassadors/lornajane).
+
+
+
+## Coming in October
+- **AsyncAPI Community Updates Newsletter** - The October Edition issue will arrive in your inbox on the 9th. [Ensure you subscribe to the AsyncAPI Newsletter](https://www.asyncapi.com/newsletter); you don't want to miss out.
+- **AsyncAPI Online Conference** - [The Online Conference will take place on the 30th of October](https://conference.asyncapi.com/venue/Online). Be sure to check the website for the Agenda and Speakers.
diff --git a/markdown/docs/tools/cli/usage.md b/markdown/docs/tools/cli/usage.md
index 3a1ddf960222..95669e0efd6c 100644
--- a/markdown/docs/tools/cli/usage.md
+++ b/markdown/docs/tools/cli/usage.md
@@ -27,7 +27,7 @@ $ npm install -g @asyncapi/cli
$ asyncapi COMMAND
running command...
$ asyncapi (--version)
-@asyncapi/cli/2.4.1 linux-x64 node-v18.20.4
+@asyncapi/cli/2.5.0 linux-x64 node-v18.20.4
$ asyncapi --help [COMMAND]
USAGE
$ asyncapi COMMAND
@@ -99,7 +99,7 @@ EXAMPLES
$ asyncapi bundle ./asyncapi.yaml -o final-asyncapi.yaml --base ../public-api/main.yaml --baseDir ./social-media/comments-service
```
-_See code: [src/commands/bundle.ts](https://github.com/asyncapi/cli/blob/v2.4.1/src/commands/bundle.ts)_
+_See code: [src/commands/bundle.ts](https://github.com/asyncapi/cli/blob/v2.5.0/src/commands/bundle.ts)_
## `asyncapi config`
@@ -113,7 +113,7 @@ DESCRIPTION
CLI config settings
```
-_See code: [src/commands/config/index.ts](https://github.com/asyncapi/cli/blob/v2.4.1/src/commands/config/index.ts)_
+_See code: [src/commands/config/index.ts](https://github.com/asyncapi/cli/blob/v2.5.0/src/commands/config/index.ts)_
## `asyncapi config analytics`
@@ -133,7 +133,7 @@ DESCRIPTION
Enable or disable analytics for metrics collection
```
-_See code: [src/commands/config/analytics.ts](https://github.com/asyncapi/cli/blob/v2.4.1/src/commands/config/analytics.ts)_
+_See code: [src/commands/config/analytics.ts](https://github.com/asyncapi/cli/blob/v2.5.0/src/commands/config/analytics.ts)_
## `asyncapi config context`
@@ -147,7 +147,7 @@ DESCRIPTION
Manage short aliases for full paths to AsyncAPI documents
```
-_See code: [src/commands/config/context/index.ts](https://github.com/asyncapi/cli/blob/v2.4.1/src/commands/config/context/index.ts)_
+_See code: [src/commands/config/context/index.ts](https://github.com/asyncapi/cli/blob/v2.5.0/src/commands/config/context/index.ts)_
## `asyncapi config context add CONTEXT-NAME SPEC-FILE-PATH`
@@ -169,7 +169,7 @@ DESCRIPTION
Add a context to the store
```
-_See code: [src/commands/config/context/add.ts](https://github.com/asyncapi/cli/blob/v2.4.1/src/commands/config/context/add.ts)_
+_See code: [src/commands/config/context/add.ts](https://github.com/asyncapi/cli/blob/v2.5.0/src/commands/config/context/add.ts)_
## `asyncapi config context current`
@@ -186,7 +186,7 @@ DESCRIPTION
Shows the current context that is being used
```
-_See code: [src/commands/config/context/current.ts](https://github.com/asyncapi/cli/blob/v2.4.1/src/commands/config/context/current.ts)_
+_See code: [src/commands/config/context/current.ts](https://github.com/asyncapi/cli/blob/v2.5.0/src/commands/config/context/current.ts)_
## `asyncapi config context edit CONTEXT-NAME NEW-SPEC-FILE-PATH`
@@ -207,7 +207,7 @@ DESCRIPTION
Edit a context in the store
```
-_See code: [src/commands/config/context/edit.ts](https://github.com/asyncapi/cli/blob/v2.4.1/src/commands/config/context/edit.ts)_
+_See code: [src/commands/config/context/edit.ts](https://github.com/asyncapi/cli/blob/v2.5.0/src/commands/config/context/edit.ts)_
## `asyncapi config context init [CONTEXT-FILE-PATH]`
@@ -230,7 +230,7 @@ DESCRIPTION
Initialize context
```
-_See code: [src/commands/config/context/init.ts](https://github.com/asyncapi/cli/blob/v2.4.1/src/commands/config/context/init.ts)_
+_See code: [src/commands/config/context/init.ts](https://github.com/asyncapi/cli/blob/v2.5.0/src/commands/config/context/init.ts)_
## `asyncapi config context list`
@@ -247,7 +247,7 @@ DESCRIPTION
List all the stored contexts in the store
```
-_See code: [src/commands/config/context/list.ts](https://github.com/asyncapi/cli/blob/v2.4.1/src/commands/config/context/list.ts)_
+_See code: [src/commands/config/context/list.ts](https://github.com/asyncapi/cli/blob/v2.5.0/src/commands/config/context/list.ts)_
## `asyncapi config context remove CONTEXT-NAME`
@@ -267,7 +267,7 @@ DESCRIPTION
Delete a context from the store
```
-_See code: [src/commands/config/context/remove.ts](https://github.com/asyncapi/cli/blob/v2.4.1/src/commands/config/context/remove.ts)_
+_See code: [src/commands/config/context/remove.ts](https://github.com/asyncapi/cli/blob/v2.5.0/src/commands/config/context/remove.ts)_
## `asyncapi config context use CONTEXT-NAME`
@@ -287,7 +287,7 @@ DESCRIPTION
Set a context as current
```
-_See code: [src/commands/config/context/use.ts](https://github.com/asyncapi/cli/blob/v2.4.1/src/commands/config/context/use.ts)_
+_See code: [src/commands/config/context/use.ts](https://github.com/asyncapi/cli/blob/v2.5.0/src/commands/config/context/use.ts)_
## `asyncapi config versions`
@@ -304,22 +304,23 @@ DESCRIPTION
Show versions of AsyncAPI tools used
```
-_See code: [src/commands/config/versions.ts](https://github.com/asyncapi/cli/blob/v2.4.1/src/commands/config/versions.ts)_
+_See code: [src/commands/config/versions.ts](https://github.com/asyncapi/cli/blob/v2.5.0/src/commands/config/versions.ts)_
## `asyncapi convert [SPEC-FILE]`
-Convert asyncapi documents older to newer versions or OpenAPI documents to AsyncAPI
+Convert asyncapi documents older to newer versions or OpenAPI/postman-collection documents to AsyncAPI
```
USAGE
- $ asyncapi convert [SPEC-FILE] -f openapi|asyncapi [-h] [-o ] [-t ] [-p client|server]
+ $ asyncapi convert [SPEC-FILE] -f openapi|asyncapi|postman-collection [-h] [-o ] [-t ] [-p
+ client|server]
ARGUMENTS
SPEC-FILE spec path, url, or context-name
FLAGS
-f, --format=