diff --git a/pages/blog/2022-summary.md b/pages/blog/2022-summary.md
new file mode 100644
index 000000000000..2cd597418448
--- /dev/null
+++ b/pages/blog/2022-summary.md
@@ -0,0 +1,252 @@
+---
+title: "State of AsyncAPI Initiative 2022 in Numbers"
+date: 2023-02-28T06:00:00+01:00
+type: Communication
+tags:
+ - Project Status
+cover: /img/posts/2022-summary/cover.webp
+authors:
+ - name: Lukasz Gornicki
+ photo: /img/avatars/lpgornicki.webp
+ link: https://twitter.com/derberq
+ byline: AsyncAPI Maintainer and Dev Comm Keeper
+excerpt: 'tl;dr We do not see any negative trends indicating that the interest in the project got stale and that the community is not growing anymore.'
+featured: true
+---
+
+It is a good practice to sometimes stop and turn back. Sometimes you need to see what you left behind, what successes made you go that far, and what things you missed and never had time to enjoy or explore. The more often you do it, the better your decisions may be in the future. It is essential to do it at least once a year in open source.
+
+Omg, I don't recall when I last wrote something so clever. At least, I think it sounds clever. :smiley:
+
+This article will take you on a journey to the past to see what happened in 2022 at AsyncAPI Initiative.
+
+If you are interested in previous project updates [check other `Project Status` posts](https://www.asyncapi.com/blog?tags=Project+Status).
+
+## Slack
+
+At the end of 2022, we had **3114** members in the AsyncAPI workspace. But what does that really mean? Don't get me wrong; I like when the numbers are high, especially if I see them in my bank account.
+
+The thing is that some accounts might belong to people that joined three years ago but don't even remember that they had an account in the AsyncAPI workspace. It would be good to check how this number relates to people's activity.
+
+Another important item to understand is how come we have **3114** members. Did all of them join in 2016? Have we had no new people join since then? That would be a disaster and a clear indication we are doing something wrong. :sweat_smile:
+
+### Workspace size
+
+Below you can see how many members have joined AsyncAPI Slack in past years. The numbers are pretty neat! People join AsyncAPI Slack because they know:
+- someone will answer their call for help
+- it is a welcoming place for first-time contributors
+- we participate in many mentorship programs
+- this is the best place to get closer together with the community
+
+
+
+My prediction is that it will be growing and growing cause existing members will tell others what place it is and why it is worth joining.
+
+### Weekly active members
+
+Below I'm showing the average and median activity throughout the years. I think the median is more accurate as it eliminates super-high weeks (like typical conference-related noise) and weeks when we have lots of holidays simultaneously, like Christmas break.
+
+
+
+Last year was the first time the median value was much lower than the average. It is higher than the previous year, but not something we got used to so far. We noticed a significant increase in Slack members, but I think we can say that this number doesn't correlate well with median activity.
+
+We should look into the data more deeply and understand what happened between April 23 and June 21 when numbers got much higher than usual. For example, what the heck happened on April 29 when we had 583 active members? Was AsyncAPI Mentorship the reason?
+
+Anyway, I definitely predict that data for 2023 will show an increase in activity as we plan to do a series of meetups around the world that will bring more and more people into Slack.
+
+### Channels popularity
+
+Below you can see all-time data that show the number of messages posted on each channel in Slack.
+
+The `General` channel is the oldest, and yeah, it is generally for general stuff... what a joker. Anyway, the most important is the discussion size in the `Tooling` channel. Specifications are boring, and people are interested more in how it works. On the other hand, tooling is most attractive to tech folks; coding and talking about it is more fun.
+
+
+
+Remember that AsyncAPI Initiative cares about both the specification and the tooling ecosystem.
+
+### New members' activity
+
+As I wrote in the intro, each community must be welcoming to new people and give them space inside so they feel comfortable interacting with others and feeling safe.
+
+Below you can see the top three members that joined the community in 2022 and were most active among other new-joiners. Their activity was clearly reflected in their contributions. In the end, all the people you can see below are now members of the [AsyncAPI Technical Steering Committee](https://www.asyncapi.com/community/tsc).
+
+
+
+## Social media
+
+Social media is not a silver bullet. I think social media should only be a news interface with the community, not a marketing tool.
+
+Below data will show you that these channels should not be treated as promotion channels that convert to new users. You will see that LinkedIn and Twitter brought together 2,082 users to the AsyncAPI website. Now, compare it to this single [Mozilla documentation article](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) that referred to our website 5,542 users.
+
+Social media is suitable for communication with the community. Promotion should target people in a location where they look for help. In other words, mentioning AsyncAPI on a WebSocket-related website performs much better than hundreds of social media posts. So we should also try to make sure AsyncAPI is mentioned in other locations. Why not mention AsyncAPI in official docs for Kafka, MQTT, and other protocols?
+
+### LinkedIn
+
+I'm so damn tired of LinkedIn. Seriously, a platform that drains so much data from others and earns money from job marketing cannot afford to give users access to historical data and see more than one-year-old stats. Like seriously...
+
+We had 2,139 followers at the end of 2022. Every year's data since account creation looks like below.
+
+
+
+We are not active on LinkedIn. We only republish whatever we publish on Twitter. No engagement is created. We treat it as a news feed, although LinkedIn != Twitter.
+
+Numbers went down a lot compared to last year, but when you look two years back, numbers are very similar. Why? In 2021, we spent $1,200 on LinkedIn marketing; thus, the number spike for one year.
+
+
+
+My statement doesn't change. LinkedIn is an important presence, and even without dedicated moderation, simple reposting brings people to the project. We should continue our work there.
+
+### Twitter
+
+Twitter? Seriously, the most unreliable tool ever. :smiley: But of course, I'm biased; I do not like it. So let's look at the data. Are people really leaving Twitter because of Elon Musk?
+
+Forget about the number of followers. We have over 3.5k followers, over 500 more than last year. For me, followers number are as reliable as GitHub stars on a repository. Not much...
+
+Let's see how Twitter's presence converts to visits to the AsyncAPI website.
+
+
+
+Exactly the same situation as with LinkedIn. Numbers drop between 2021 and 2022, but again because 2021 was a special year. We experimented that year with paid marketing on Twitter too. So the numbers we should compare are for the years 2020 and 2022. As we can see no change, and it is pretty stable. It looks like Twitter was not really abandoned, at least not for now :smiley: .
+
+My take on it. This is acceptable. I do not think we have to do more there. My observation is that tweets that perform there are not technical tweets that could bring more people to the project, but "thank you" tweets and "appreciation" tweets. And do not get me wrong, we should still create such tweets, no question about it. It proves it is a social media, not a "technical geeks knowledge exchange center." I do not think any additional investment in the platform makes sense.
+
+## Google Analytics
+
+We use Google Analytics on [AsyncAPI website](https://www.asyncapi.com/) to understand the most valuable content for you and learn how the interest is growing. The data we get doesn't 100% reflect reality because AsyncAPI is for technical people, and many technical people use plugins in browsers to block Google Analytics or browsers that block it natively.
+
+We also have numbers that confirm that. I checked the last seven days of data from Google Analytics and compared it with the raw traffic data we get from Netlify servers. The dates I checked were February 13-20:
+
+- Google Analytics noted over 24k page views.
+- Netlify noted over 26k page views.
+
+This means we are losing around 7% of the data if I calculated it right. :smiley:
+Unfortunately, with Netlify we do not have access to data older than seven days. We can dump this data for future analytics, but we need New Relic or some other service to sponsor the storage for us :smiley:
+
+### Confusing data
+
+The "quality" of the user visiting the website is much better. In 2022, we had no paid marketing nor any viral blog posts, and finally, data is more reliable and natural.
+
+
+
+There is a much larger increase in the amount of **Pageviews** and **Sessions** but no significant increase in **User visits**. My theory: In 2022, we didn't have a single super viral blog post like in previous years that would bring a few thousand people in just a few days (like September 9, 2021 - over 5k readers), people that are interested in an article, and not AsyncAPI in general.
+
+I think we can say that it is the first time we have had a regular increase in users and that this increase is valuable as these users generate a lot of sessions and navigate through the website a lot. In other words, the bigger difference between **User visits** and **Pageviews**, the better.
+
+It would make sense to retake the above table and check it against Google Analytics, but not base it on the total number of visits and sessions, but the median for each year. In theory, this way, we would remove the traffic that is hard to predict from the equation, as it is not up to us to decide if something will be viral.
+
+### The more docs we get, the more traffic increase we will see
+
+One of the top goals for the AsyncAPI website should be to increase the content and benefit from the SEO. This happened in 2022, thanks to participation in Google Season of Docs. We had six dedicated docs contributors. We gained new [`Concepts`](https://www.asyncapi.com/docs/concepts) and [`Generator`](https://www.asyncapi.com/docs/tools/generator) documentation in the website.
+
+In the case of Generator documentation, Florence and Pratik refactored all the documentation from the Generator repository and made sure it was published in an automated way on the website. It was published on the website on the 20th of December, almost the end of the year during Christmas break, a dead season for the website. Yet the new content managed to generate an additional 1,053 Pageviews to the website!
+
+Concepts were published to the website on different dates, some in September and some in early December. This new content generated more than 17,646 Pageviews in over three months.
+
+
+
+As you can see, more technical content, which was not even released at the beginning of the year, converted into many additional pageviews. In 2023, this content will perform even better. I know it for sure, as only in the case of Generator docs, in January 2023, Google Analytics noted 4,668 views! Well, you must admit that 48k **Pageviews** for 2023 would be huge!
+
+### Google Search Console
+
+I believe that numbers from GSC can show how many more people hear about AsyncAPI and gain interest in the topic. In other words, the assumption is that the more people google, the more people are aware of AsyncAPI. And yes, the below numbers of impressions indicate a number higher than a million. :wink:
+
+
+
+In 2022 we didn't perform any specific modifications on the website to improve SEO. So the only explanation for the increase in impressions and clicks is the increased volume of documentation I wrote about in the previous section. More useful content, better ranking in search.
+
+## GitHub
+
+Like on other channels, we notice growing traffic in [our GitHub organization](https://github.com/asyncapi).
+
+### Total contributions
+
+In the last three years, we increased from 301 contributors in Q1 2020 to 1,520 in Q4 2022.
+
+From 301 to 1,520 contributors for things like commits, pull requests authoring and review, or issues participation. In just three years!!!
+
+
+
+This huge difference also has a negative aspect. More contributions mean more maintenance work.
+
+### Negative aspect of growth
+
+Unfortunately, the number of maintainers does not grow as much as the number of contributors. This means that the difference between the number of submitted and resolved issues will get larger and larger.
+
+
+
+Three years ago, we dreamed about having thousands of contributions. We forgot to balance that number with the proper number of maintainers. Now we need to react and make sure we also get a large number of active maintainers.
+
+## npm
+
+Most of our tools are written in JavaScript/TypeScript; we host them on Node Package Manager (npm).
+
+### Top packages
+
+Our most essential packages are [the project that provides AsyncAPI JSON Schema files](https://www.npmjs.com/package/@asyncapi/specs), [the Generator](https://www.npmjs.com/package/@asyncapi/generator), [the React component](https://github.com/asyncapi/asyncapi-react) and [the Parser](https://www.npmjs.com/package/@asyncapi/parser). Below you can see how downloads of these packages increased.
+
+
+
+You do not believe in this data? Lemme repeat what I wrote last year:
+
+> The increase in numbers is insanely huge. People automatically say that it is because of build systems, local development, or that some single corporation started using it at scale. In other words, the increase could result from just one project that uses these tools as a dependency.
+ 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 the internal proxy. Not included in downloads.
+- Most build systems cache packages downloaded are ready 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.
+
+An interesting observation is that in 2021 AsyncAPI Parser was the only user of the AsyncAPI spec JSON schemas project (`@asyncapi/specs`), as the number of downloads was almost the same. In 2022, the AsyncAPI spec JSON schemas project was downloaded five million times, three times more than the parser. This means many more tools are dependent on the project.
+
+In 2021 we could see that the AsyncAPI Parser is not only a Generator dependency; today we see the AsyncAPI spec JSON schemas project is not only a Parser dependency. This means that the increase in traffic in different channels and the growing user base also reflect the number of tools built on top of AsyncAPI tools. One of the big users of `@asyncapi/specs` is now Spectral. Also, GitHub tells us that `@asyncapi/specs` is used in 1,329 public repositories
+
+## YouTube
+
+The [AsyncAPI YouTube channel](https://www.youtube.com/asyncapi) had a massive increase in traffic.
+
+### Watch time
+
+YouTube is just another channel where we can see the audience is growing. The conference and other regular live streams bring a lot of watchers. In 2023, numbers might drop because we do not want to do the online conference, but yeah, let's see.
+
+
+
+## Final words
+
+We grow. Numbers just confirm our observation.
+
+- If you plan to invest in AsyncAPI Initiative, don't worry. It is still an on-top project.
+- It was the right call if you already invested in AsyncAPI Initiative. The community is growing.
+
+We do not see any negative trends indicating that the interest in the project got stale and that the community is not growing anymore.
+
+I also recommend below conference recording to learn more about AsyncAPI Community.
+
+
+
+> Photo by Hannah Busing on Unsplash
diff --git a/pages/blog/2022Q1-summary.md b/pages/blog/2022Q1-summary.md
index 6eda7d22ea55..800fafb39ea3 100644
--- a/pages/blog/2022Q1-summary.md
+++ b/pages/blog/2022Q1-summary.md
@@ -11,7 +11,6 @@ authors:
link: https://twitter.com/derberq
byline: AsyncAPI Gardener
excerpt: 'New AsyncAPI brand. AsyncAPI 2.4 and work on the 3.0 spec release. Meetings organization change. 2022 conference organization. AND SO MUCH MORE!'
-featured: true
---
diff --git a/pages/blog/async-api-spec-3.0-release.md b/pages/blog/async-api-spec-3.0-release.md
index c347b654689c..302daf47aed0 100644
--- a/pages/blog/async-api-spec-3.0-release.md
+++ b/pages/blog/async-api-spec-3.0-release.md
@@ -12,7 +12,6 @@ authors:
photo: /img/avatars/harsh.webp
link: https://www.linkedin.com/in/harshcasper/
excerpt: 'Announcing the start of work on AsyncAPI Spec 3.0. Check out all the potential new features coming to AsyncAPI 3.0 and how you can get involved!'
-featured: false
---
AsyncAPI is a specification for describing your event-driven architecture. Our specification allows you to describe and document your message-driven APIs into a human-readable format. The AsyncAPI community is currently inching towards a 3.0 release that will bring together multiple features, enhancements, and breaking changes. We follow [release cadence](https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md#release-cadence) and we will continue to release the Spec to the community as we continue to build on it.
diff --git a/pages/blog/creating-consistency-announcing-asyncapi-spectral-together.md b/pages/blog/creating-consistency-announcing-asyncapi-spectral-together.md
index e0a09842c90a..b9fbbfeb53d7 100644
--- a/pages/blog/creating-consistency-announcing-asyncapi-spectral-together.md
+++ b/pages/blog/creating-consistency-announcing-asyncapi-spectral-together.md
@@ -12,7 +12,6 @@ authors:
byline: Senior Software Engineer at Stoplight
excerpt: |
The collaboration between Stoplight’s open-source linting tool, Spectral, and AsyncAPI will be a game-changer for creating more consistency in your API program. Check out what comes with the release of the AsyncAPI ruleset!
-featured: true
---
The collaboration between Stoplight’s open-source linting tool, Spectral, and AsyncAPI is going to be a game changer for creating more consistency in your API program. Check out what comes with the release of the AsyncAPI ruleset!
diff --git a/pages/blog/documenting-sqs-event-driven-apis-with-asyncapi.md b/pages/blog/documenting-sqs-event-driven-apis-with-asyncapi.md
index 2cce7f8872b8..16b20dd55cdb 100644
--- a/pages/blog/documenting-sqs-event-driven-apis-with-asyncapi.md
+++ b/pages/blog/documenting-sqs-event-driven-apis-with-asyncapi.md
@@ -10,7 +10,6 @@ authors:
link: https://www.linkedin.com/in/mauro-bosetti/?locale=en_US
byline: Argentinian software explorer.
excerpt: This post demonstrates how documenting event-driven architectures is possible, using SQS as a (real-world) example.
-featured: true
---
> Hey, do you remember what this field looks like in GET /operations?
diff --git a/pages/blog/event-driven-api-documentation-made-simple-clientside-rendering.md b/pages/blog/event-driven-api-documentation-made-simple-clientside-rendering.md
index 9806496f2552..0cd18cd85b44 100644
--- a/pages/blog/event-driven-api-documentation-made-simple-clientside-rendering.md
+++ b/pages/blog/event-driven-api-documentation-made-simple-clientside-rendering.md
@@ -1,7 +1,6 @@
---
title: Event driven API documentation made simple (Client-Side Rendering).
date: 2022-09-28T06:00:00+01:00
-featured: true
type: Engineering
tags: ['documentation','guide']
cover: /img/posts/event-driven-API-documentation-made-simple/documentation.webp
diff --git a/pages/blog/google-season-of-docs-2022.md b/pages/blog/google-season-of-docs-2022.md
index 6fba17872659..7e35562a821b 100644
--- a/pages/blog/google-season-of-docs-2022.md
+++ b/pages/blog/google-season-of-docs-2022.md
@@ -12,7 +12,6 @@ authors:
link: https://www.linkedin.com/in/alejandra-quetzalli/
byline: Our proposal? Update Docs Information Architecture
excerpt: Check out the Docs project proposal we're submitting to GSoD 2022! You won't want to miss out.
-featured: true
---
## ¡Hola, AsyncAPI community!
diff --git a/pages/blog/radical-transparency.md b/pages/blog/radical-transparency.md
index 4a7853c0da9a..594866ce0d5b 100644
--- a/pages/blog/radical-transparency.md
+++ b/pages/blog/radical-transparency.md
@@ -13,7 +13,6 @@ authors:
link: https://twitter.com/fmvilas
byline: Executive Director at AsyncAPI Initiative
excerpt: ''
-featured: true
---
There are multiple ways to manage an open-source project. At AsyncAPI, we chose the Open Governance model for many good reasons that Lukasz explained in his article [Finding a Good Open Governance Model for AsyncAPI](/blog/governance-motivation).
diff --git a/pages/blog/release-notes-2.4.0.md b/pages/blog/release-notes-2.4.0.md
index 8d32c38cec5e..f2b522728701 100644
--- a/pages/blog/release-notes-2.4.0.md
+++ b/pages/blog/release-notes-2.4.0.md
@@ -12,7 +12,6 @@ authors:
link: https://twitter.com/smoyac
byline: Pilot at AsyncAPI Airlines
excerpt: 'AsyncAPI 2.4 is now released. This brings really helpful additions, such as the new `messageId` field, Server Variables reusability, and security at Operation level'
-featured: true
---
The new version of the AsyncAPI specification - 2.4.0 - is now available.
diff --git a/pages/blog/release-notes-2.5.0.md b/pages/blog/release-notes-2.5.0.md
index 410b447a0ccb..a9b7eace8fa7 100644
--- a/pages/blog/release-notes-2.5.0.md
+++ b/pages/blog/release-notes-2.5.0.md
@@ -12,7 +12,6 @@ authors:
link: https://twitter.com/vladimirgorej
byline: Open Source Software Engineer, OSS contributor, author and content creator.
excerpt: "The release of AsyncAPI 2.5 brings helpful additions, such as extended Server Variables reusability and many clarifications."
-featured: true
---
The new version of the AsyncAPI specification - 2.5.0 - is now available.
diff --git a/pages/blog/status-update-week-14-2019.md b/pages/blog/status-update-week-14-2019.md
index e4d6adf89559..5888497e97c8 100644
--- a/pages/blog/status-update-week-14-2019.md
+++ b/pages/blog/status-update-week-14-2019.md
@@ -3,7 +3,7 @@ title: 'Status update (week 14, 2019)'
date: 2019-04-04T13:56:52+01:00
type: Communication
tags:
- - Status Update
+ - Project Status
cover: /img/posts/status-update-week-14-2019.webp
authors:
- name: Fran Méndez
diff --git a/pages/blog/status-update-week-15-2019.md b/pages/blog/status-update-week-15-2019.md
index 046a251121b2..73cf99ec17e5 100644
--- a/pages/blog/status-update-week-15-2019.md
+++ b/pages/blog/status-update-week-15-2019.md
@@ -3,7 +3,7 @@ title: "Status update (week 15, 2019)"
date: 2019-04-11T13:56:52+01:00
type: Communication
tags:
- - Status Update
+ - Project Status
cover: /img/posts/status-update-week-15-2019.webp
authors:
- name: Fran Méndez
diff --git a/pages/blog/status-update-week-17-2019.md b/pages/blog/status-update-week-17-2019.md
index 561f4596e9b2..bcf36fc47569 100644
--- a/pages/blog/status-update-week-17-2019.md
+++ b/pages/blog/status-update-week-17-2019.md
@@ -3,7 +3,7 @@ title: "Status update (week 17, 2019)"
date: 2019-04-25T13:56:52+01:00
type: Communication
tags:
- - Status Update
+ - Project Status
cover: /img/posts/status-update-week-17-2019.webp
authors:
- name: Fran Méndez
diff --git a/public/img/posts/2022-summary/cover.webp b/public/img/posts/2022-summary/cover.webp
new file mode 100644
index 000000000000..f53828c85435
Binary files /dev/null and b/public/img/posts/2022-summary/cover.webp differ
diff --git a/public/img/posts/2022-summary/ga-views.webp b/public/img/posts/2022-summary/ga-views.webp
new file mode 100644
index 000000000000..a0b327f2cdd8
Binary files /dev/null and b/public/img/posts/2022-summary/ga-views.webp differ
diff --git a/public/img/posts/2022-summary/github-contrib.webp b/public/img/posts/2022-summary/github-contrib.webp
new file mode 100644
index 000000000000..2d572ba789ea
Binary files /dev/null and b/public/img/posts/2022-summary/github-contrib.webp differ
diff --git a/public/img/posts/2022-summary/github-issues.webp b/public/img/posts/2022-summary/github-issues.webp
new file mode 100644
index 000000000000..fd67489207b1
Binary files /dev/null and b/public/img/posts/2022-summary/github-issues.webp differ
diff --git a/public/img/posts/2022-summary/google-concepts.webp b/public/img/posts/2022-summary/google-concepts.webp
new file mode 100644
index 000000000000..4520224ecf7d
Binary files /dev/null and b/public/img/posts/2022-summary/google-concepts.webp differ
diff --git a/public/img/posts/2022-summary/google-search.webp b/public/img/posts/2022-summary/google-search.webp
new file mode 100644
index 000000000000..57418bdc5f73
Binary files /dev/null and b/public/img/posts/2022-summary/google-search.webp differ
diff --git a/public/img/posts/2022-summary/linkedin-followers.webp b/public/img/posts/2022-summary/linkedin-followers.webp
new file mode 100644
index 000000000000..41194a33c6c6
Binary files /dev/null and b/public/img/posts/2022-summary/linkedin-followers.webp differ
diff --git a/public/img/posts/2022-summary/linkedin-referrals.webp b/public/img/posts/2022-summary/linkedin-referrals.webp
new file mode 100644
index 000000000000..c59e9fb3af1e
Binary files /dev/null and b/public/img/posts/2022-summary/linkedin-referrals.webp differ
diff --git a/public/img/posts/2022-summary/npm-stats.webp b/public/img/posts/2022-summary/npm-stats.webp
new file mode 100644
index 000000000000..3cfcafa6adce
Binary files /dev/null and b/public/img/posts/2022-summary/npm-stats.webp differ
diff --git a/public/img/posts/2022-summary/slack-channel-usage.webp b/public/img/posts/2022-summary/slack-channel-usage.webp
new file mode 100644
index 000000000000..14252fcef501
Binary files /dev/null and b/public/img/posts/2022-summary/slack-channel-usage.webp differ
diff --git a/public/img/posts/2022-summary/slack-most-active-new-2022.webp b/public/img/posts/2022-summary/slack-most-active-new-2022.webp
new file mode 100644
index 000000000000..6b69040a3326
Binary files /dev/null and b/public/img/posts/2022-summary/slack-most-active-new-2022.webp differ
diff --git a/public/img/posts/2022-summary/slack-people-joining.webp b/public/img/posts/2022-summary/slack-people-joining.webp
new file mode 100644
index 000000000000..a0189dbbdde7
Binary files /dev/null and b/public/img/posts/2022-summary/slack-people-joining.webp differ
diff --git a/public/img/posts/2022-summary/slack-spammers.webp b/public/img/posts/2022-summary/slack-spammers.webp
new file mode 100644
index 000000000000..d9d8d5b6a57f
Binary files /dev/null and b/public/img/posts/2022-summary/slack-spammers.webp differ
diff --git a/public/img/posts/2022-summary/slack-weekly.webp b/public/img/posts/2022-summary/slack-weekly.webp
new file mode 100644
index 000000000000..7a1207df2d62
Binary files /dev/null and b/public/img/posts/2022-summary/slack-weekly.webp differ
diff --git a/public/img/posts/2022-summary/twitter-referrals.webp b/public/img/posts/2022-summary/twitter-referrals.webp
new file mode 100644
index 000000000000..86e1d38811f7
Binary files /dev/null and b/public/img/posts/2022-summary/twitter-referrals.webp differ
diff --git a/public/img/posts/2022-summary/yt.webp b/public/img/posts/2022-summary/yt.webp
new file mode 100644
index 000000000000..998b2ef7597d
Binary files /dev/null and b/public/img/posts/2022-summary/yt.webp differ