updated some profile URLs (#8552)

contents/blog/meetings.mdx

@@ -38,9 +38,9 @@ Let me share with you how PostHog does meetings. We’re constantly improving ou
 
 Meeting-free days allow more deep work to get done. At PostHog, we've mandated Tuesdays and Thursdays as meeting-free days, which has had a significant impact on our team’s productivity. Mondays are reserved for company updates and Wednesdays for team updates. Every 2nd Friday, we do a retrospective planning session with life stories in between. We also use meetings for [SuperDays](https://posthog.com/handbook/people/hiring-process/), one-to-one coffee breaks (one every two weeks), or optional group socials (once per week).
 
-> "Meeting-free Tuesdays & Thursdays have increased the number of high-value tasks I get done than I did previously. If I were starting another company, I'd do exactly what we're doing here." — [Charles Cook](/community/profiles/254), Head of Business Ops @ PostHog
+> "Meeting-free Tuesdays & Thursdays have increased the number of high-value tasks I get done than I did previously. If I were starting another company, I'd do exactly what we're doing here." — [Charles Cook](/charles), Head of Business Ops @ PostHog
 
-Our meeting-free days create a natural cadence for the week, with everyone knowing they will alternate between ‘light’ and ‘heavy’ days with plenty of time in between to get good work done. In practice, while Monday, Wednesday, and Friday are meeting days, only a few people will use up that time for important work, such as [James](/community/profiles/71) or [Yakko](/community/profiles/56); or Eltje, our People Ops & Talent Manager, speaking to candidates.
+Our meeting-free days create a natural cadence for the week, with everyone knowing they will alternate between ‘light’ and ‘heavy’ days with plenty of time in between to get good work done. In practice, while Monday, Wednesday, and Friday are meeting days, only a few people will use up that time for important work, such as [James](/james) or Yakko; or Eltje, our People Ops & Talent Manager, speaking to candidates.
 
 > "I think PostHog’s meeting policy is a good setup and that we have the right balance with an extra day towards meetings." — Kunal Pathak, Growth Engineer @ PostHog
 
@@ -80,7 +80,7 @@ It's essential to strike the right balance between moments of team communication
 
 Building a positive and productive meeting culture must be modeled from the top. While many companies have different policies around meetings, things on the ground might be different. For example, a company could declare Tuesdays as meeting-free days and still have a manager set up a meeting during that protected time because their calendars are full. This erodes trust in the system and fosters resentment.
 
-Part of our magic here at PostHog is that we practice what we preach. James and [Tim](/community/profiles/108), PostHog’s co-founders, publicly model a low internal meeting culture. This sets the tone for the rest of the company and leads to high trust in management. It also assures everyone that they’ll always have plenty of non-meeting time to get work done.
+Part of our magic here at PostHog is that we practice what we preach. [James](/james) and [Tim](/tim), PostHog’s co-founders, publicly model a low internal meeting culture. This sets the tone for the rest of the company and leads to high trust in management. It also assures everyone that they’ll always have plenty of non-meeting time to get work done.
 
 ## The best meeting policy for your startup
 

contents/blog/seed-grow-scale-devrel.mdx

@@ -54,7 +54,7 @@ Anyone who knows me and is reading this may be surprised I've not mentioned [AAA
 
 ### At PostHog...
 
-PostHog has seen significant growth over the past year resulting in a [Series B raise](https://posthog.com/blog/15-million-series-b). Following this, [James](/community/profiles/71) and [Tim](/community/profiles/108), our co-founders, decided it was the right time to introduce dedicated DevRel roles (I'm particularly pleased about this because it means I now get to work here!). Before this, all potential DevRel activities were spread across other team members. But, because PostHog is a developer-centric company, operates with [small teams](/handbook/company/small-teams), and embraces [stepping on toes](/handbook/company/values#step-on-toes), people need to continue to do what's required to ship. There are, however, some gaps and opportunities where DevRel can make improvements or begin new activities.
+PostHog has seen significant growth over the past year resulting in a [Series B raise](https://posthog.com/blog/15-million-series-b). Following this, [James](/james) and [Tim](/tim), our co-founders, decided it was the right time to introduce dedicated DevRel roles (I'm particularly pleased about this because it means I now get to work here!). Before this, all potential DevRel activities were spread across other team members. But, because PostHog is a developer-centric company, operates with [small teams](/handbook/company/small-teams), and embraces [stepping on toes](/handbook/company/values#step-on-toes), people need to continue to do what's required to ship. There are, however, some gaps and opportunities where DevRel can make improvements or begin new activities.
 
 In the near term, our AAARRRP goals are Activation, Retention, Referral, and Product. Instead of narrowing in on specific activities, we've broadly mapped the priorities as:
 

contents/blog/slack-closure.md

@@ -38,7 +38,7 @@ We've also integrated the forum into other parts of the site. You can, for examp
 
 Profiles are also a big part of the forum; a place where you can add info, track discussions you're involved in, and display achievements earned through the community. In fact, we're giving everyone who joins the PostHog community from the public Slack a unique achievement to say thanks for the support!
 
-You can even open your profile to function as an Ask Me Anything (AMA) - something [James](https://posthog.com/community/profiles/71), [Cory](https://posthog.com/community/profiles/2), and [myself](https://posthog.com/community/profiles/59) have already done.
+You can even open your profile to function as an Ask Me Anything (AMA) - something [James](/james), [Cory](/community/profiles/30200), and [myself](https://posthog.com/community/profiles/29070) have already done.
 
 > **Ready to join the community?** [Create an account today](/questions) and, if you've previously signed up to the public Slack group, you'll get a unique achievement to display on your community profile!
 

contents/founders/recommended-reading.md

@@ -48,7 +48,7 @@ Lottie claims she doesn’t read very much, but when pressed for recommendations
 
 ![Secrets of Sand Hill Road](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/tracks/sand-hill-road.jpg)
 ## [Secrets of Sand Hill Road by Scott Kupor](https://www.goodreads.com/book/show/42348376-secrets-of-sand-hill-road)
-**Recommended by [James Hawkins, CEO & Co-founder](/community/profiles/71)**
+**Recommended by [James Hawkins, CEO & Co-founder](/james)**
 
 James reads a lot and could likely recommend enough books to fill an article all on his own but, when we asked for recommendations for first-time founders, this was one of the first books that came to mind. It focuses on explaining how startups operate from a VC’s perspective.
 
@@ -61,7 +61,7 @@ James reads a lot and could likely recommend enough books to fill an article all
 ![messy middle](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/tracks/messy-middle.jpg)
 
 ## [The Messy Middle by Scott Belsky](https://www.goodreads.com/book/show/40179007-the-messy-middle)
-**Recommended by [Charles Cook, Operations & Marketing](/community/profiles/254)**
+**Recommended by [Charles Cook, Operations & Marketing](/charles)**
 
 If there’s one person whose book recommendations are really worth listening to, then it’s Charles. Not only is he the leader of both our Operations and Marketing teams — he’s _also_ the founder of our internal book club.
 
@@ -72,7 +72,7 @@ If there’s one person whose book recommendations are really worth listening to
 
 ![high output management](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/tracks/high-growth.jpg)
 ## [High Output Management by Andrew Grove](https://www.goodreads.com/book/show/324750.High_Output_Management)
-**Recommended by [Grace McKenzie, Finance & Operations Lead](/community/profiles/718)**
+**Recommended by Grace McKenzie, Finance & Operations Lead**
 
 Andrew Grove was Intel’s third employee, third CEO, and the man who led the company to the world’s largest producer of semiconductors. He also somehow found time to write this book about organizational theory which is beloved by our chief organizer, Grace.
 
@@ -83,7 +83,7 @@ Andrew Grove was Intel’s third employee, third CEO, and the man who led the co
 
 ![no rules rules](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/tracks/no-rules-rules.jpg)
 ## [No Rules Rules by Reed Hastings](https://www.goodreads.com/book/show/49099937-no-rules-rules) 
-**Recommended by [James Hawkins, CEO & Co-founder](/community/profiles/71)**
+**Recommended by [James Hawkins, CEO & Co-founder](/james)**
 
 When it came to envisioning the sort of culture he wanted to build at PostHog, no was more influential for James as this exploration of Netflix’s company culture. PostHog doesn’t copy Netflix’s approach completely, but we definitely share some of the underlying philosophies. 
 

contents/founders/startup-ops-toolkit.md

@@ -27,7 +27,7 @@ I won't offer multiple options here – it's not that kind of guide. Just know t
 
 So, read on if you want to learn how to put together contracts, pay people on time, manage your money and comply with laws you are only just finding out exist.
 
-> [Charles Cook](/community/profiles/254) is VP Marketing & Ops at PostHog, leading operations, marketing, people, finance, and legal. All the fun stuff, basically. As PostHog's first non-product hire, he used these tools to do the work of 5ish people for a long time. 
+> [Charles Cook](/charles) is VP Marketing & Ops at PostHog, leading operations, marketing, people, finance, and legal. All the fun stuff, basically. As PostHog's first non-product hire, he used these tools to do the work of 5ish people for a long time. 
 
 ## 1. Hiring people
 

contents/handbook/people/hiring-process/engineering-hiring.md

@@ -33,7 +33,7 @@ This is the usual first round interview with the People & Ops team.
 The [technical interview](/handbook/people/hiring-process#interview-2) round is split into two parts:
 
 - The first part is an hour-long technical interview with one of our engineers. This might be architecture design or diving more into past technical experiences in more of a workshop style. No whiteboarding or brainteasers. 
-- If they pass this stage, we will then schedule a follow up 30-minute interview with [Tim](/community/profiles/108) about your previous experiences and what motivates you. 
+- If they pass this stage, we will then schedule a follow up 30-minute interview with [Tim](/tim) about your previous experiences and what motivates you. 
 
 #### Engineering SuperDay
 

contents/handbook/people/hiring-process/operations-hiring.md

@@ -31,7 +31,7 @@ This is our usual first round interview with a member of the People & Ops team.
 
 #### Technical Interview 
 
-The [technical interview](/handbook/people/hiring-process#interview-2) usually lasts between 45-60 minutes and you will probably meet a member of our [People and Culture team](/teams/people) as well as [Charles](/community/profiles/254). For this round, you can expect questions about your background, together with scenario-based questions. 
+The [technical interview](/handbook/people/hiring-process#interview-2) usually lasts between 45-60 minutes and you will probably meet a member of our [People and Culture team](/teams/people) as well as [Charles](/charles). For this round, you can expect questions about your background, together with scenario-based questions. 
 
 #### Operations SuperDay
 

contents/newsletter/b2b-startup-marketing-strategy.md

@@ -24,12 +24,12 @@ We’re product-led. We have [product-market fit](/founders/product-market-fit-g
 
 How nooby? Well, here’s our team and their marketing “credentials”:
 
-- [Charles](/community/profiles/254) – leads marketing and (weirdly) ops and finance. No prior marketing experience.
-- [Andy](/community/profiles/62) – worked in online publishing for 15+ years. No prior marketing experience.
-- [Ian](/community/profiles/269) – software engineering background. No prior marketing experience.
-- [Lior](/community/profiles/684) – spent five years in engineering at Meta before PostHog. No prior marketing experience.
-- [Lottie](/community/profiles/227) – our awesome graphic designer. PostHog is her first proper job.
-- [Joe](/community/profiles/59) – former journalist and, to be fair, has actual marketing experience at previous startups. Way too much experience, probably.
+- [Charles](/charles) – leads marketing and (weirdly) ops and finance. No prior marketing experience.
+- [Andy](/andy) – worked in online publishing for 15+ years. No prior marketing experience.
+- [Ian](/ian) – software engineering background. No prior marketing experience.
+- [Lior](/lior) – spent five years in engineering at Meta before PostHog. No prior marketing experience.
+- [Lottie](/lottie) – our awesome graphic designer. PostHog is her first proper job.
+- [Joe](/joe) – former journalist and, to be fair, has actual marketing experience at previous startups. Way too much experience, probably.
 
 So, yeah. Here’s what we’ve learned about marketing for startups, specifically for a B2B startup for developers. Let us know where we’re wrong!
 

contents/newsletter/hiring-at-posthog-lessons.md

@@ -36,7 +36,7 @@ PostHog’s co-founders, Tim and James, wrote [our public handbook](/handbook/)
 
 ## 2. Your early users could be your best hires
 
-In the early days, PostHog’s CEO, [James Hawkins](/community/profiles/71), would check out people who starred the repo and sometimes get in touch to gather feedback. One such call resulted in our third hire, [James Greenhill](/community/profiles/90).
+In the early days, PostHog’s CEO, [James Hawkins](/james), would check out people who starred the repo and sometimes get in touch to gather feedback. One such call resulted in our third hire, [James Greenhill](/jams).
 
 On the call, James G explained Uber (where he worked) had built a bunch of internal tools like PostHog for data control reasons. He found the project interesting and wanted to work on it. He ended up doing a few days of paid work and the rest is history.
 

vercel.json

@@ -910,7 +910,6 @@
         { "source": "/docs/cdp/gitlab-release-tracker", "destination": "/docs/cdp" },
         { "source": "/handbook/growth/marketing/Customer-personas", "destination": "/handbook/growth/marketing" },
         { "source": "/docs/cdp/bitbucket-release-tracker", "destination": "/docs/cdp" },
-        { "source": "/james", "destination": "/community/profiles/71" },
         { "source": "/handbook/company/strategy", "destination": "/handbook/strategy/overview" },
         { "source": "/guides", "destination": "/tutorials" },
         {
@@ -930,11 +929,21 @@
         { "source": "/tutorials/revenue", "destination": "/tutorials" },
         { "source": "/tutorials/how-to-segment-users", "destination": "/tutorials/power-users" },
         { "source": "/docs/cdp/shopify", "destination": "/docs/cdp" },
+
+        { "source": "/james", "destination": "/community/profiles/27732" },
         { "source": "/tim", "destination": "/community/profiles/27730" },
         { "source": "/marius", "destination": "/community/profiles/30202" },
         { "source": "/raquel", "destination": "/community/profiles/28693" },
         { "source": "/jamesg", "destination": "/community/profiles/30174" },
         { "source": "/jams", "destination": "/community/profiles/30174" },
+        { "source": "/charles", "destination": "/community/profiles/28625" },
+        { "source": "/andy", "destination": "/community/profiles/30208" },
+        { "source": "/ian", "destination": "/community/profiles/29296" },
+        { "source": "/lior", "destination": "/community/profiles/28754" },
+        { "source": "/lottie", "destination": "/community/profiles/27881" },
+        { "source": "/joe", "destination": "/community/profiles/29070" },
+        { "source": "/cory", "destination": "/community/profiles/30200" },
+
         { "source": "/docs/surveys/manual", "destination": "/docs/surveys" },
         { "source": "/docs/surveys/setup", "destination": "/docs/surveys/installation" },
         { "source": "/docs/surveys/new", "destination": "/docs/surveys/creating-surveys" },