Move images to Cloudinary (#8024)

* featured images

* thumbnails

* remove hosthog

* images

* logos

* imports

* remove versions

* relative imports

* icons

* fix undefined vars

* fix import script

* kill images

* fix static images

* fix og creation

* remove quality option

* add absolutepath back

* wait for images

* date fixes

* remove scripts

* reduce network requests

* only generate OG images in prod

* simplify

* update docs

* add new images

contents/apps/notification-bar/index.mdx

@@ -1,10 +1,14 @@
 ---
 title: Notification Bar
-featuredImage:
+featuredImage: null
 documentation: /docs/apps/notification-bar
-thumbnail: ../thumbnails/notification-bar.png
+thumbnail: >-
+  https://res.cloudinary.com/dmukukwp6/image/upload/posthog.com/contents/apps/thumbnails/notification-bar.png
 description: Alert users to important news by adding a banner to your website
-filters: { type: ['other'], maintainer: official }
+filters:
+  type:
+    - other
+  maintainer: official
 ---
 
 <Section

contents/apps/pineapple-mode/index.mdx

@@ -1,12 +1,13 @@
 ---
 title: Pineapple Mode
-featuredImage: 
+featuredImage: null
 documentation: /docs/apps/pineapple-mode
-thumbnail: ../thumbnails/pineapple-mode.png
-filters: {
-    type: ["other"],
-    maintainer: official
-}
+thumbnail: >-
+  https://res.cloudinary.com/dmukukwp6/image/upload/posthog.com/contents/apps/thumbnails/pineapple-mode.png
+filters:
+  type:
+    - other
+  maintainer: official
 ---
 
 <Section

contents/blog/100-times-more-events.md

@@ -1,16 +1,17 @@
 ---
 date: 2021-05-17
-title: "Why we're giving away 100 times more cloud usage, free"
+title: 'Why we''re giving away 100 times more cloud usage, free'
 rootPage: /blog
 sidebar: Blog
 showTitle: true
 hideAnchor: true
-featuredImage: ../images/blog/100x/100x.png
+featuredImage: >-
+  https://res.cloudinary.com/dmukukwp6/image/upload/posthog.com/contents/images/blog/100x/100x.png
 featuredImageType: full
 author:
   - james-hawkins
 category: PostHog news
-tags: 
+tags:
   - Product updates
 ---
 

contents/blog/15-million-series-b.md

@@ -5,7 +5,8 @@ rootPage: /blog
 sidebar: Blog
 showTitle: true
 hideAnchor: true
-featuredImage: ../images/blog/series-b/series-b-baby.png
+featuredImage: >-
+  https://res.cloudinary.com/dmukukwp6/image/upload/posthog.com/contents/images/blog/series-b/series-b-baby.png
 author:
   - joe-martin
 category: PostHog news

contents/blog/2022-review.md

@@ -1,13 +1,15 @@
 ---
 date: 2023-01-11
-title: "CEO diary: The things I learned in 2022"
+title: 'CEO diary: The things I learned in 2022'
 rootPage: /blog
 sidebar: Blog
 showTitle: true
 hideAnchor: true
 category: CEO diaries
-author: ["james-hawkins"]
-featuredImage: ../images/blog/posthog-ceo-diary-blog.png
+author:
+  - james-hawkins
+featuredImage: >-
+  https://res.cloudinary.com/dmukukwp6/image/upload/posthog.com/contents/images/blog/posthog-ceo-diary-blog.png
 featuredImageType: full
 ---
 
@@ -17,7 +19,7 @@ It's always helpful to look back on the year just gone, and 2022 was an exceptio
 
 ### We grew very fast _and_ are much more durable
 
-![Our 2022 revenue growth over time, which increases by 6 times](../images/revenue-end-2022.jpg)
+![Our 2022 revenue growth over time, which increases by 6 times](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/revenue-end-2022.jpg)
 
 - Revenue grew nearly 6x without any outbound sales team.
 

contents/blog/Introduction-to-self-service-analytics.md

@@ -7,7 +7,8 @@ showTitle: true
 hideAnchor: true
 author:
   - joe-martin
-featuredImage: ../images/blog/blog-generic-4.png
+featuredImage: >-
+  https://res.cloudinary.com/dmukukwp6/image/upload/posthog.com/contents/images/blog/blog-generic-4.png
 featuredImageType: full
 category: Product growth
 tags:

contents/blog/a-non-coders-thoughts-on-everybody-codes-culture-part-two.md

@@ -5,7 +5,8 @@ rootPage: /blog
 sidebar: Blog
 showTitle: true
 hideAnchor: true
-featuredImage: ../images/blog/migrating-hog.png
+featuredImage: >-
+  https://res.cloudinary.com/dmukukwp6/image/upload/posthog.com/contents/images/blog/migrating-hog.png
 featuredImageType: full
 category: Inside PostHog
 ---
@@ -27,7 +28,7 @@ If I’d stuck to realistic limits, that would be the end of it. I can’t  buil
 
 It turns out that I can. Late last year I made [a ShuffleHog prototype on Twitter](https://twitter.com/thehogbot), coded in [Tracery](https://www.tracery.io/). That lasted until [Marius added the ability to make front-end apps in PostHog](https://github.com/PostHog/posthog/issues/9654#issuecomment-1133222836) last week. 24 hours later, ShuffleHog now lives inside PostHog as a beta feature that can suggest random query ideas.
 
-![ShuffleHog - AKA PostHog's Best Feature](../images/blog/non-coders-thoughts/shufflehog_app.png)
+![ShuffleHog - AKA PostHog's Best Feature](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/blog/non-coders-thoughts/shufflehog_app.png)
 
 ShuffleHog still isn’t quite ready for other users to try yet, but who knows? Maybe I’ll keep following this dream. 
 
@@ -41,7 +42,7 @@ Breaking things is a great way to learn about how to fix them. PostHog recently
 ### Take it offline
 Something I’ve loved about becoming more confident with code is that I’ve been able to follow this passion outside of work. This creates a feedback loop where I get even more excited about what I’m learning and what I’m able to do, so I bring that energy back into work…where I _also_ learn and do more. It’s very satisfying. 
 
-![Joe's Open Source Arcade](../images/blog/non-coders-thoughts/arcade_open_source.png)
+![Joe's Open Source Arcade](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/blog/non-coders-thoughts/arcade_open_source.png)
 
 The experience I’ve had with GitHub, for example, ended up being the catalyst for me to build my own arcade emulation machine at home because I now had the skills to fork and tweak certain repos. Likewise, spending time in the world of open-source software led to me playing around with a _lot_ of Raspberry Pi sensors at home.
 

contents/blog/a-non-coders-thoughts-on-everybody-codes-culture.md

@@ -7,7 +7,8 @@ rootPage: /blog
 sidebar: Blog
 showTitle: true
 hideAnchor: true
-featuredImage: ../images/blog/non-coders-thoughts/non-coders-thoughts.jpg
+featuredImage: >-
+  https://res.cloudinary.com/dmukukwp6/image/upload/posthog.com/contents/images/blog/non-coders-thoughts/non-coders-thoughts.jpg
 featuredImageType: full
 category: Inside PostHog
 ---

contents/blog/after-the-hn-launch.md

@@ -29,13 +29,13 @@ We write down everything we learn internally on the same doc we started with in
 
 The second thing we try to do well is to set up informal communication with the customer – we often us Slack or WhatsApp groups. They let people feel safer just sending a couple of sentences because they lose the formality of email. And, they can just be quite good fun.
 
-![](../images/02/Screenshot-2020-02-25-at-21.52.15.png)
+![](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/02/Screenshot-2020-02-25-at-21.52.15.png)
 
 Throughout YC, we’ve split our roles pretty clearly. As my former boss used to say “don’t be like 5 year olds playing football”.
 
 Even when there were just two of us, Tim and I quickly saw how important it was to write tickets for features and issues. This meant that Tim could code uninterrupted, with notifications disabled. I would do everything else. We tend to work with our headphones on almost all day to help stay focused. Occasionally we take them off, and one day we may treat ourselves to a new lightbulb for the office (updated - we never did):
 
-![](../images/02/working.jpeg)
+![](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/02/working.jpeg)
 
 Since Aaron joined, he has focused on getting feedback from users, Tim has kept working on the product, and I’ve focused on product, marketing and anything else. Aaron and I share the QA for features and we try to get them done immediately, so it doesn’t cause Tim to have to multitask.
 

contents/blog/analytics-tips-for-customer-success-teams.md

@@ -7,7 +7,8 @@ showTitle: true
 hideAnchor: true
 author:
   - joe-martin
-featuredImage: ../images/blog/green-blog-image.jpg
+featuredImage: >-
+  https://res.cloudinary.com/dmukukwp6/image/upload/posthog.com/contents/images/blog/green-blog-image.jpg
 featuredImageType: full
 category: Using PostHog
 tags:
@@ -19,7 +20,7 @@ While PostHog is obviously useful for product managers, engineers and analysts,
 You can find out more about [how our customer success team works](/handbook/people/team-structure/customer-success) in the PostHog docs, but in the meantime here are five tips to help _your_ CS team get started with PostHog…
 
 ## 1. Use funnels to find out where customers get stuck
-![Top to bottom funnels in PostHog](../images/blog/activation-checklist-images/top-down-funnel.png)
+![Top to bottom funnels in PostHog](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/blog/activation-checklist-images/top-down-funnel.png)
 
 Using a combination of [autocapture](/docs/data/autocapture) and [custom or calculated events](/tutorials/event-tracking-guide#using-custom-events-to-track-advanced-behaviors), PostHog makes it possible to track every part of your product experience. This makes it trivial to track where users are getting stuck by using [funnel insights](/manual/funnels) to visualize the user journey.
 
@@ -28,7 +29,7 @@ At PostHog, for example, new users have to go through several common steps to be
 > 💡**PostHog Tip:** Want to delve deeper into the root causes behind a drop off? Use [breakdowns](/manual/funnels#identify-possible-causes-of-failure-and-success) to explore what groups of users have in common. 
 
 ## 2. Use trends to find out which features are popular
-![graph of an insight broken down by a property](../images/blog/activation-checklist-images/posthog-trend-insight.png)
+![graph of an insight broken down by a property](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/blog/activation-checklist-images/posthog-trend-insight.png)
 
 If you, like PostHog, charge based on usage then you’ll want to keep a close eye on your usage metrics. This will both help you spot trends in declining usage so that you can react early, and also proactively reach out to customers with increasing usage too. 
 
@@ -37,7 +38,7 @@ The simplest way to monitor usage is via a [trends insight](/manual/trends). Jus
 > 💡**PostHog Tip:** If you’ve only got a small number of users, your results may get swayed by internal users or test accounts. [Here’s how to filter them out](/tutorials/filter-internal-users).
 
 ## 3. Use lifecycle charts to find users about to churn
-![lifecycle chart in posthog](../images/blog/activation-checklist-images/lifecycle-chart-posthog.png)
+![lifecycle chart in posthog](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/blog/activation-checklist-images/lifecycle-chart-posthog.png)
 
 Regardless of whether or not your overall usage is growing, it’s a good idea to monitor your overall retention and identify which customers are falling dormant and are at risk of churning. The [lifecycle insight](/manual/lifecycle) exists exactly for this purpose.
 
@@ -46,14 +47,14 @@ Lifecycle insights categorize users based on whether they have completed any eve
 > 💡**PostHog Tip:** Curious about the difference between returning and resurrecting users? Check [the lifecycle docs](/manual/lifecycle#interpreting-your-lifecycle) for a full explanation. 
 
 ## 4. Install apps to integrate PostHog with your stack
-![apps for cs teams](../images/blog/activation-checklist-images/apps-for-cs-teams.png)
+![apps for cs teams](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/blog/activation-checklist-images/apps-for-cs-teams.png)
 
 We like to think PostHog works brilliantly on its own, but to get the most out of the platform you may want to connect it with other software in your stack. We have a library of over 50 apps to help you do this, so you can connect PostHog with tools such as [Hubspot](/apps/hubspot-connector) or [Salesforce](/apps/salesforce-connector). 
 
 Best of all, because PostHog is entirely open source, you can build your own apps to enhance your data even further — all you need is a little Javascript or Typescript knowledge and you’re good to go!
 
 ## 5. Build and share a customer success dashboard
-![subscriptions in posthog](../images/blog/activation-checklist-images/subscribe-in-posthog.png)
+![subscriptions in posthog](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/blog/activation-checklist-images/subscribe-in-posthog.png)
 
 Once you’ve built the insights you need, an essential step is adding them all to a PostHog dashboard so that you don’t need to check them one-by-one. Once you’ve pinned all your insights to a dashboard, you can easily check everything in one place and export it as an image if you need to include it in reports. 
 

contents/blog/analytics-tips-for-marketing-teams.md

@@ -7,7 +7,8 @@ showTitle: true
 hideAnchor: true
 author:
   - joe-martin
-featuredImage: ../images/blog/posthog-marketing/marketing-hog.jpg
+featuredImage: >-
+  https://res.cloudinary.com/dmukukwp6/image/upload/posthog.com/contents/images/blog/posthog-marketing/marketing-hog.jpg
 featuredImageType: full
 category: Using PostHog
 tags:
@@ -19,7 +20,7 @@ One of the great things about PostHog is that it democratizes your product strat
 Internally, [our marketing team](/handbook/people/team-structure/marketing) uses PostHog for [all their reporting](/blog/posthog-marketing), as well as for running ad-hoc analysis and testing new ideas. Here are some of the tips and tricks we recommend based on their experience...
 
 ## 1. Set up an AARRR pirate funnel
-![AARRR pirate metrics](../images/blog/using-posthog/aarrr.png)
+![AARRR pirate metrics](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/blog/using-posthog/aarrr.png)
 
 AARRR funnels are a framework for understanding how users engage with your product at different stages of their journey — Acquisition, Activation, Retention, Revenue, and Referral. It’s especially useful for marketers, growth teams and product marketers because it enables you to see where your biggest drop-offs are at a glance. 
 
@@ -28,7 +29,7 @@ The AARRR framework needs to be adapted slightly for each product — acquisitio
 > 💡**PostHog Tip:** Want to know more? Check our [complete guide to AARRR pirate funnels](/blog/aarrr-pirate-funnel)!
 
 ## 2. Track campaigns with trend insights
-![how to track utms in posthog](../images/blog/activation-checklist-images/utm-tracking-in-posthog.png)
+![how to track utms in posthog](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/blog/activation-checklist-images/utm-tracking-in-posthog.png)
 
 UTMs are an indispensable tool in the modern marketing arsenal, enabling you to track clicks by adding a customizable parameter after a URL. The URL `posthog.com/?utm_campaign=opensource` could be used in social media posts to track visits to the PostHog website via an open source campaign, for example. But how do you track these campaigns in PostHog?
 
@@ -37,7 +38,7 @@ The simplest way is to use a [trends insight](/manual/trends) in PostHog that fi
 > 💡**PostHog Tip:** Trends aren’t the only way to visualize UTM performance. You can also use [the funnels insight](/manual/funnels) to explore how users move between two events - such as viewing a landing page, and signing up. 
 
 ## 3. Watch how users sign-up with session recordings
-![session recordings in posthog](../images/blog/activation-checklist-images/session-recording-posthog.png)
+![session recordings in posthog](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/blog/activation-checklist-images/session-recording-posthog.png)
 
 You may think your sign-up flow is easy to navigate, but what really matters is what your users think. If only there was some way to watch how they use your site, so you can identify where they’re experiencing friction? Enter: [session recordings](/manual/recordings).
 
@@ -46,7 +47,7 @@ Session recordings are like a DVR of people using your product and enable you to
 > 💡**PostHog Tip:** Watching lots of recordings can be time consuming. We recommend filtering recordings to focus on key events, such as new sign-ups, to make it easier to find valuable insights. 
 
 ## 4. Understand how users explore your site with paths
-![session recordings in posthog](../images/blog/activation-checklist-images/paths-in-posthog.png)
+![session recordings in posthog](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/blog/activation-checklist-images/paths-in-posthog.png)
 
 So, you know how to track performance of marketing campaigns and how to see how individual users engage with your content, but how can you get a view of the entire user journey? That’s where [path analysis](/manual/paths) comes in. 
 
@@ -55,7 +56,7 @@ Paths enable you to see the route every user takes between two points, as well a
 > 💡**PostHog Tip:** Path insights in PostHog don’t have to specify both the start and endpoint. If you’re curious how users get to a specific page, for example, you can just set an endpoint to see every path users took to reach that page. 
 
 ## 5. Use dashboards subscriptions to keep up to date
-![dashboard subscriptions in posthog](../images/blog/activation-checklist-images/subscribe-in-posthog.png)
+![dashboard subscriptions in posthog](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/blog/activation-checklist-images/subscribe-in-posthog.png)
 
 Maybe you want to share PostHog reports with the whole company, or maybe you’re just trying to cut down on time spent looking for credentials in 1Password. Either way, subscriptions are the solution.