Skip to content

Blog: Questions people ask me about developer marketing - #19495

Open
joethreepwood wants to merge 3 commits into
masterfrom
posthog/developer-marketing-questions
Open

Blog: Questions people ask me about developer marketing#19495
joethreepwood wants to merge 3 commits into
masterfrom
posthog/developer-marketing-questions

Conversation

@joethreepwood

Copy link
Copy Markdown
Contributor

Changes

Adds a new blog post by Joe Martin: "Questions people ask me about developer marketing" — answers to the questions he gets asked most often, covering launch tactics, channel choice, billboards, merch, pre-marketing, community, first marketing hires, and more.

  • New post at contents/blog/developer-marketing-questions.md (category: Inside PostHog; tags: Marketing, Growth)
  • Featured image plus two in-post photos, committed under contents/images/blog/developer-marketing-questions/ and served via the Cloudinary auto-fetch mapping (they resolve once merged to master)
  • Embeds the merch page Wistia video and the DeskHog YouTube demo video, each with captions

Why

Joe keeps getting asked the same developer marketing questions on quick calls, so this post writes down the answers in one shareable place.

Checklist

  • I've read the docs and/or content style guides.
  • Words are spelled using American English
  • Use relative URLs for internal links
  • I've checked the pages added or changed in the Vercel preview build
  • If I moved a page, I added a redirect in vercel.json

Created with PostHog Desktop

New blog post by Joe Martin answering common developer marketing questions, with featured image, billboard photo, water bottle photo, and embedded merch and DeskHog videos.

Generated-By: PostHog Desktop
Task-Id: b12fadf3-619d-4ce5-86dd-2b7447b65c5b
@github-actions github-actions Bot added blog content PR only touches files under contents/ labels Aug 14, 2026
@joethreepwood joethreepwood self-assigned this Aug 14, 2026
@joethreepwood
joethreepwood marked this pull request as ready for review August 14, 2026 14:24
@joethreepwood
joethreepwood requested a review from a team as a code owner August 14, 2026 14:24
@github-actions

github-actions Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Aug 14, 2026 04:20PM

@github-actions

github-actions Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Vale prose linter → found 4 errors, 18 warnings, 2 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/blog/developer-marketing-questions.md — 4 errors, 18 warnings, 2 suggestions
Line Severity Message Rule
24:37 warning Use the Oxford comma before 'and' or 'or' in a list of three or more items. PostHogBase.OxfordComma
28:4 warning '"I built something and told people about it. What should I do now?"' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
32:535 warning 'pre' is a possible misspelling. PostHogBase.Spelling
36:4 warning '"What channels should I use?" / "What works?"' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
38:35 suggestion Avoid hedging. Be opinionated instead of saying 'It depends'. PostHogEditorial.Hedging
40:41 suggestion Avoid hedging. Be opinionated instead of saying 'It depends'. PostHogEditorial.Hedging
51:4 warning '"OK, but what about those billboards?"' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
57:4 warning '"You do great merch. How do you justify that and what suppliers do you use?"' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
60:21 warning 'outsized' is a possible misspelling. PostHogBase.Spelling
66:83 warning 'Micromerch' is a possible misspelling. PostHogBase.Spelling
66:172 warning Use American English. Use 'color' instead of 'Colour'. PostHogBase.AmericanEnglish
66:238 warning Use American English. Use 'modeling' instead of 'modelling'. PostHogBase.AmericanEnglish
68:4 warning '"New users don't know about old features. What should I do?"' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
70:153 warning Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. PostHogBase.ProductNames
89:4 warning '"How do you approach AEO?"' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
99:4 warning 'Automations' is a possible misspelling. PostHogBase.Spelling
100:4 warning 'Automations' is a possible misspelling. PostHogBase.Spelling
101:4 warning 'Automations' is a possible misspelling. PostHogBase.Spelling
112:196 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
124:28 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
142:376 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
157:4 warning '"What am I missing?" / "What advice do you have?"' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
159:237 error 'Rules' is repeated! Vale.Repetition
167:4 warning '"Shouldn't this have been a Reddit AMA or something?"' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase

@github-actions

github-actions Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Bundle report

Total JS (gzip)

7.55 MiB (no change)

Eager graph (modules shipped in each entrypoint's initial chunks)

Entrypoint Eager size Budget Modules
app 16.90 MiB (no change) report-only 2018
Largest modules in the app closure
Module Size
./src/data/mcp-tools.json 990.3 KiB
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css 746.7 KiB
./src/components/Stickers/Stickers.tsx 696.4 KiB
./node_modules/.pnpm/@radix-ui+react-icons@1.3.2_react@18.3.1/node_modules/@radix-ui/react-icons/dist/react-icons.esm.js 481.4 KiB
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules 395.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.cjs.js 364.8 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js 354.8 KiB
./src/hooks/useCustomers.tsx + 54 modules 354.5 KiB
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules 351.4 KiB
./src/components/ProductComparisonTable/index.tsx + 126 modules 301.4 KiB
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js 281.9 KiB
./src/components/SearchUI/index.tsx + 87 modules 273.0 KiB
./node_modules/.pnpm/@posthog+brand@0.8.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/magnifying-glass.mjs 254.7 KiB
./node_modules/.pnpm/framer-motion@10.18.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/framer-motion/dist/es/render/dom/motion.mjs + 109 modules 253.9 KiB
./node_modules/.pnpm/d3@7.9.0/node_modules/d3/src/index.js + 208 modules 247.4 KiB

Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes for the modules actually shipped in the entrypoint's initial chunks (post-tree-shake).

Swap repo-path Cloudinary URLs for the actual uploaded assets and remove the committed image files — the contents/images path mapping was a one-time 2024 migration, so images referenced that way never resolve.

Generated-By: PostHog Desktop
Task-Id: b12fadf3-619d-4ce5-86dd-2b7447b65c5b
Comment thread contents/blog/developer-marketing-questions.md
@jina-yoon
jina-yoon requested a review from ivanagas August 14, 2026 20:44
@jina-yoon

Copy link
Copy Markdown
Contributor

believe @ivanagas will be the main reviewer on this one! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blog content PR only touches files under contents/

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants