Ben Gabler

Most README badges are quietly costing your visitors a page-speed tax. The standard shields.io badge is a third-party image request. Four badges = four DNS lookups + four render-blocking image fetches on a page you don't control the cache headers for. On a repo landing page that's usually fine. On your product's docs or homepage, it shows up in your Core Web Vitals. There's also a quota trap nobody mentions: GitHub's public API allows 60 unauthenticated requests per hour per IP. If you fetch the star count client-side on every page load, a traffic spike means your badge starts rendering blank exactly when the most people are looking at it. Three things I'd check on any badge you embed outside a README: ─ Is the count cached server-side, or re-fetched on every single load? ─ Does it degrade gracefully when the API is rate-limited or down? ─ Is it an image (works in markdown) or a script (works on web pages)? Those are different jobs — use the right one for the right surface. Star counts are real social proof. It's worth 5 minutes to embed them in a way that doesn't slow the page down. What's on your README right now — badges, or a clean slate? 👇 #OpenSource #GitHub #DeveloperTools #WebPerformance #IndieDev #DevRel #CoreWebVitals #SaaS

I've been automating our own GTM at Warmly with with Warmly + Claude Code Agent SDK and here's what you need to do: 1. Integrate all your systems. For us it's HubSpot (CRM activity stream), Slack (internal discussions on deals), Sybill (call recording), BuiltWith (technographics), Warmly, (signals, chat conversations, enrichment/web research). Outreach for sequencing. APIs or bust for vendors 2. Use Warmly's TAM Agent to find the short list of high intent ICP companies and perfect buying committee contacts (no interns, just buyers). 500 accounts, 1500 contacts. Pull into Claude Code. 3. Use Claude Code to build territory mapping for AEs and SDRs. 15 per AE, 100+ per SDR. Map email inboxes. Just prompt this and save as an .md file the territory mapping. Then map this to Hubspot via the integration 4. Use Claude Code to query my systems in step 1 and build the full timeline on each of the accounts. "Closed lost, who visited the website, when did we engage last, what pages are they looking for, what was discussed on last demo call" 4. Use Octave API to write the perfect email outreach with full context from Step 3. Send this automatically to Outreach with tags and using custom fields for subject and email body. 5. Automatically sync the contacts directly to LinkedIn Ads. Results: - Ads: 50% reduction in CPC, 3x improvement in CTR for the exact same ad creative after a week of running. - Emails: Will let you know next week. Aleksandar Lepidovski running it right now! Okay here's the problems you run into: 1. You are going to iterate a lot with prompting Claude Code and context degrades quickly when you use MCPs. Claude code does its best to auto-compact but I've noticed that once it gets to 85% context window the memory degradation is already severe. 2. It takes a long time to pull the full context on the accounts once you get a short list of accounts to do deep research on. And by the time the context pulls you realize you missed something or claude didn't pull it right... so you burn through tokens (good thing claude code tokens are cheap for now) 3. Agents are stateless, which means once you close the session it loses all the context, so you need a way to build memory into the system if you want to run this job again. You'll use .MD guideline files for now and you try your best to use claude.md files to stitch together where to look, but you have no idea if the AI is reading in the right context and guideline files before it runs the job. So you pray. 4. You have no idea how to encode this into your existing human and workflow systems and how to scale it. Human systems are more deterministic (gets the job done) but do not compound alongside foundational model improvements. 5. You realize that shit data in means shit outputs and that's a whole can of worms that has nothing to do with LLMs. You don't want to manage this system even though it's the foundation. You start looking for Agent Harnesses for GTM (check the comments)

95

24 Comments

I've been building CMS systems for 20 years. WordPress, Drupal, you name it, I've shipped more sites than I care to admit. One pattern has never changed: the teams that publish early and iterate consistently always win. So it's painful watching YC founders, brilliant people building incredible products, treat content as a "post-PMF problem." Here's what actually happens: 📉 Company A waits until after fundraising to think about content. Six months post-Demo Day, they have zero organic traffic and are burning cash on paid acquisition. 📈 Company B starts publishing in Week 1. By Demo Day, they have 50 indexed pages, ranking for long-tail keywords, with a steady stream of inbound leads. Six months later, that trickle is a river. The excuse used to be "we don't have time." But in 2026, AI has completely changed the equation. A 2-person startup can now run a content operation that rivals companies 10x their size: → AI agents that write, publish, and distribute content autonomously → Full-stack apps generated from a single text prompt → Automated workflows that cross-post to every platform We built Cosmic for exactly this. It's the AI-powered content platform that lets your tiny team operate like a 20-person marketing department, while you stay focused on building product. I wrote the full week-by-week playbook here: https://lnkd.in/gfFNCV84 If you're a YC founder (or any early-stage startup), I'd love to hear how you're thinking about content. What's working? What's not? #YCombinator #Startups #ContentMarketing #HeadlessCMS #AI

4

Hey all, DrupalCon North America is just around the corner! See you soon! Don't forget to sign up for the Nonprofit Summit when purchasing your DrupalCon ticket! ‼️ It’s FREE ‼️ The summit is a full-day event from 9 AM to 4 PM on Monday, March 23, featuring talks and informal breakout sessions hosted by nonprofit Drupal practitioners. The summit is a fantastic opportunity for community engagement. Key themes for the summit include: 🔶 AI (Artificial Intelligence): A fireside chat with Timothy Lehnen (CTO of the Drupal Association) and Josh Miller (Director of Web Development for the Urban Institute) will discuss how AI can serve non-profit missions, focusing on practical applications and ethical considerations rather than just hype. Breakout sessions will cover AI governance and agentic interfaces. 🔶 Resiliency: Maintaining website functionality and organizational stability amidst challenges like high turnover and resource constraints. 🔶 Digital Sovereignty: Tim Lennon will lead a discussion on digital ethics and sovereignty, which is a significant topic in the open-source community. Additional breakout sessions cover topics such as: 🔶 Drupal careers 🔶 Creating accessible, secure, and inclusive online spaces for sensitive topics 🔶 Building simple, small site features in Drupal on a budget See the full agenda: https://lnkd.in/gdNxwWUx Already bought your ticket? You can add the summit: https://lnkd.in/gczeuGwH And if you want to hear more about the summit, you can listen to these two episodes of TD Cafe! https://lnkd.in/gcrHXzjV https://lnkd.in/gey9NGAS

29

The Big Bite agency is now part of WP Engine: https://lnkd.in/e5pjbuV8. This could be a very interesting move for publishers using WordPress. If you're curious what Big Bite does, I wrote about them last year. For example, they helped "The Times" to standardize on WordPress: https://lnkd.in/ebnsX5YU

9

Optimizing the WooCommerce checkout process is key for conversions. AJAX loading can speed things up, but avoid slowing the checkout page with too many upsells. A well-placed, compatible pre-order plugin with a coupon can work wonders. CheckoutWC and CartFlows offer Shopify-like experiences, but be mindful of compatibility and customization. #WooCommerce #eCommerce #CheckoutOptimization #ConversionRate #OnlineBusiness

1