Launch & Discovery Guides
Practical guides on launching products, getting discovered, and reaching the right audience - written for founders and developers.
Index
58 topics, A to Z

README Examples From 30 Popular CLI Repos: How Many Words Come Before the First Command
We pulled the README of the 30 most-starred GitHub repositories tagged cli and measured what sits above the first command a visitor can paste: prose, badges and pictures.
CodeTrendy Editorial Team
More Articles
41 total
Technical SEO Before Go-Live: 12 Inspections a New SaaS Landing Page Must Pass
An inspection card for the night before a new SaaS landing page opens: twelve crawl and index inspections, each with the result that passes and, where a terminal can prove it, the one-line command.

Developer Tool Pricing: Usage, Seat or Flat Fee, Chosen in Five Junctions
Five yes or no questions that route a developer tool to usage-based, per-seat or flat pricing, then the free tier shapes that fit each one, with real pricing pages as examples.

Free Tier Abuse: A Hypothetical Postmortem of One Weekend of Fake Signups, and the Quotas That Would Have Held
A made-up but realistic incident report: a small API loses its free tier to scripted signups over one weekend. The timeline, the five faults behind it, and the limits, keys and checks that close each one.

Ollama Pre-Commit Hook: Field Notes on Wiring a Local Model Into git commit
A bench log of putting a local Ollama model in front of every commit: where the hook sits, how to get JSON back, the 4096-token default, cold starts, and why the hook must let the commit through when the model is down.

Git Internals Quiz: 8 Questions on Objects, Refs and the Reflog, Answered With Real Output
Eight questions on what Git really stores: blobs, trees, commits, tags, HEAD, packed refs and the reflog. Answer each one, then open the answer to check it against real terminal output.

Your Product Updates Page Is a Landing Page You Already Wrote. Stop Hiding It.
An opinion: a changelog that lives on one endless page behind a "load more" button throws away the best writing a small team does. Give every notable change its own dated URL and the page starts earning visits.

Self-Hosted Web Analytics for a Small SaaS: Plausible, Umami, PostHog and Matomo Racked Side by Side
Four open source analytics tools you can run on your own server, compared row by row: server size, database, license, cookies, tracker weight and what the self-hosted build leaves out.

Build Log: Generating llms-full.txt, Markdown Page Copies and a Link Header From One Docs Folder
Five commits that turn a folder of Markdown docs into llms.txt, llms-full.txt and a .md copy of every page, with a check that fails the build and the v2 Link header that points agents to the Markdown.

Show HN Teardown: Five Launches Taken Apart by Title, First Comment and Demo Link
Five developer tool launches that passed 1,100 points on Show HN, each laid out on the bench in three parts: the title line, the first words from the maker, and the link a reader could try.

Idempotency-Key: Retry a Timed-Out POST Without Charging the Customer Twice
A POST times out and the client cannot know if it worked. A small server I ran today shows the double charge, then the Idempotency-Key header that prevents it, with the status codes the IETF draft and Stripe use.

How to Write a README: Five Ingredients, Measured Out Like a Recipe
GitHub lists five things a README usually answers. Here they are as a recipe: what goes in, in what order, how much of each, and what to leave in the wiki.

Exit Codes 0 to 255: What 1, 2, 126, 127, 130 and 137 Mean, and Which One Your CLI Should Return
Every process hands back one number when it ends. Here is what each common exit code means, a command that reproduces it, why 137 turns up in containers, and which codes to use in your own tool.

Good First Issues: Rewriting One Vague Ticket So a Stranger Can Finish It
A newcomer opens your Issues tab and sees "improve error handling". Here is the same ticket rewritten, the six things it needed, and where GitHub shows the label.

security.txt, SECURITY.md and Private Reporting: Three Doors for the Person Who Finds Your Bug
Set up the three places a researcher looks before reporting a flaw in your tool: /.well-known/security.txt, a SECURITY.md file and GitHub private vulnerability reporting, with a fire drill to test them.

actions.lock vs SHA Pins: Replaying the tj-actions Tag Hijack Against Every Workflow Defense
GitHub Actions lockfiles went GA on 28 October 2026. We replay the 2025 tj-actions and reviewdog tag hijack move by move to see what a tag, a SHA pin, the pinning policy, immutable releases and actions.lock would each have done.

Dependabot vs Renovate: Seven Rounds on Setup, PR Noise, Security and Automerge
Which dependency update bot should you run? Dependabot and Renovate compared round by round from their current docs, with starter configs and a pick for each kind of repo.

API Deprecation: The Sunset Header, Notice Periods and a Calendar for Retiring a Version
Retiring an API takes two dates. How the Deprecation and Sunset headers carry them, how much notice GitHub, Microsoft, Shopify and Anthropic give, and a 12-month calendar.

Show HN by the Numbers: What 46,138 Posts Scored in 12 Months
We pulled every Show HN post from October 2025 to September 2026. The median score was 2, one post in 60 reached 100, and timing mattered less than the title and the crowd.

Publish an MCP Server to the Official Registry: Names, Ownership Proof and server.json
What the official MCP Registry checks before it lists a server, which namespace to choose, the ownership marker for each package type, and what 53,479 listed servers show about getting found.

API Key Format: Prefixes, Checksums and Hashed Storage That Catch Leaks Early
How to design the keys your API hands out: a prefix scanners can match, a random part nobody can guess, a checksum, a hash in the database, and a plan for the day one leaks.

GitHub Topics and the About Box: The Three Fields Repository Search Reads
A plain GitHub repository search looks at the name, the description and the topics, and at the README only when someone adds in:readme. Yet about half of the repositories with 100 or more stars have no topics at all. What each field of the About box does, GitHub's limits for topics and the social preview image, and the commands that set them.

Is That Package Name Really Free? How Registries Decide Who Gets a Name
A 404 from the registry only says no package has that exact name. npm, PyPI and crates.io also compare a normalized form and block reserved names, npm and PyPI refuse names that look too similar, and a taken name changes hands only in narrow cases. The rules side by side, the lookup commands, and the order to check a name in.

Webhook Signature Verification: How Stripe, GitHub, Slack and Shopify Sign Events, and How to Check One
A webhook URL is public, so the signature header is the dependable proof that a request came from the provider. What each major provider signs, a Node.js verifier with a constant-time compare, the time limits that matter, and how to rotate a secret without losing events.

npm Trusted Publishing: Ship Releases From CI Without an NPM_TOKEN Before January 2027
npm targets January 2027 to stop access tokens from publishing new versions directly. Trusted publishing replaces the NPM_TOKEN secret with a short-lived OIDC identity from GitHub Actions, GitLab or CircleCI. How it works, how to set it up, and what to do when CI cannot use it.

API Rate Limit Headers: What to Send With a 429, and How Clients Should Wait
A 429 Too Many Requests tells a client to slow down; Retry-After and the rate limit headers tell it for how long. What each header means, how GitHub, OpenAI, Anthropic and Discord write them, and a retry loop that honours Retry-After and backs off with jitter.

Diátaxis: How to Structure Developer Documentation in Four Kinds of Pages
The Diátaxis framework sorts every docs page with two questions about the reader: doing or understanding, learning or working. What goes in tutorials, how-to guides, reference and explanation, and how to fix the docs you already have.

Changelogs People Read: Keep a Changelog, SemVer and Release Notes in Practice
What goes in a CHANGELOG.md, how to pick the next MAJOR.MINOR.PATCH number, why npm treats 0.x versions differently, and which tools can draft release notes for you.

MIT, Apache 2.0 or AGPL? Picking an Open Source License Before You Ship
What MIT, Apache 2.0, MPL, GPL, AGPL and source-available licenses ask of the people who use your code, which one each package ecosystem defaults to, and why Elastic, HashiCorp and Redis changed theirs.

llms.txt for Developer Tools: What It Does, Who Reads It, How to Write One
An llms.txt file gives AI agents a short map of your docs. What goes in it, which tools actually read it, what it will not do for search, and how to write one for your developer tool.

Are GitHub Stars Worth Chasing? What the Research Says
Most developers check the star count before they adopt a tool, but most stars are not usage. What a star measures, what bought stars do to a repository, and which signals show real adoption.

How to get cited by AI search: what the evidence says
An evidence-first guide for founders of small product sites: what the vendors document, what one much-quoted research paper really tested, which tactics are unproven, and a weekly method for checking whether AI answers cite you.

AI crawlers, robots.txt and llms.txt: a startup guide
A technical reference for founders who run their own site: every major AI crawler sorted by what it does with your pages, with the vendor documentation behind each row.

Schema markup for SaaS pages: what Google still shows
A type-by-type reference for founders and developers adding JSON-LD to a software product site, checked against Google Search Central documentation in October 2026.

How developers discover and adopt new tools
A field guide for anyone marketing a developer tool to people who distrust marketing. It follows one path: discover, evaluate in 5 minutes, first success, tell a colleague.

How to launch an AI tool in a crowded category
A working method for founders shipping "another" AI writing, notes or chatbot tool. You leave with a rewritten one-line claim and a plan for the evidence behind it.

The Complete Guide to Product Visibility in 2026
Everything you need to know about building product visibility in 2026 - from strategy to outreach to tracking results. This guide covers every major channel for getting your product discovered, with actionable steps.

Why Every Startup Needs a Product Discovery Listing
A product discovery listing is one way for startups to get in front of early adopters, build credibility, and give your product a public profile people can find from the moment you launch.

Top 10 Ways to Increase Your Product Visibility
Product visibility is how easily the right people can discover what you built. Here are 10 practical ways to get your product in front of a relevant audience and increase qualified discovery.

How to Get Your Product Listed on Discovery Platforms in 2026
A practical, step-by-step guide to getting your product listed on curated discovery platforms in 2026 - what to prepare, which platforms to target, and how to maximize your chances of approval.

What a Curated Product Listing Is and Why It Matters
Learn what a curated product listing actually is, how a discovery platform puts your tool in front of the right audience, and why a credible public profile is one of the most useful early moves you can make.