Writing
Notes on startup programs, developer documentation, and the work behind Sourcey.
What GitHub Shows About Your Email Address
What profiles, commits and signing keys reveal about your email address, how to check yours, and what GitHub's privacy settings actually protect.
Topics: github · git · email · privacy · developers
Who to Email About Startup Credits
Who to contact for startup credits, when to follow up, and which referrals, account details and replies AWS, Google, Microsoft and others actually need.
Topics: startup-credits · cloud · founders · email · sourcey
Where Agents Still Need a Person
An agent can find a service and still need a person to use it. What 104 Sourcey product and job profiles show about discovery, access and human setup.
Topics: agents · agent-readiness · api · sourcey
How We Check Startup Programmes
Who qualifies, what they receive and where they actually apply. How Sourcey checks startup programmes and preserves the details a short summary can lose.
Topics: startup-credits · research · eligibility · sourcey
Why We Care What the Docs Look Like
Good-looking documentation should come with the tool. A closer look at typography, API references and the design choices projects make with Sourcey.
Topics: documentation · design · api-docs · sourcey
Before You Apply for Startup Credits
Startup credits can leave you with a larger bill than you expected. Check eligibility, coverage, expiry and migration costs before choosing an offer.
Topics: startup-credits · cloud · founders · sourcey
Rust API Docs on Your Own Site
Bring Rustdoc API references and doctests into your own documentation site, beside your guides. Configure Sourcey’s Rust adapter and keep the build reproducible.
Topics: rust · rustdoc · doctests · documentation · sourcey
You Don't Own Your Docs
You have the Markdown. Can you rebuild the site, take the design and search with you, and keep the links people already use?
Topics: documentation · ownership · open-source · sourcey · llms-txt
Your Docs Have a Second Reader Now
The sentence an agent leaves out can be the one that changes the answer. Your docs need to carry their meaning beyond the page.
Topics: agents · llms-txt · documentation · mcp · sourcey
pkg.go.dev Isn't Your Docs Site
Build a Go documentation site from package comments and test examples, with guides, deliberate package selection, and a layout your project can make its own.
Topics: godoc · go · pkg.go.dev · documentation · llms-txt
Don't Replace Doxygen
Give C++ documentation a better-looking home without replacing Doxygen. Use its XML output, keep the comments, and check the symbols and links that matter.
Topics: doxygen · c++ · documentation · moxygen
Stop Renting Your OpenAPI Docs
Turn an OpenAPI spec into a good-looking docs site you can host yourself. What to keep, what to check, and where guides, examples, and URLs complicate a move.
Topics: openapi · swagger · api-docs · documentation · llms-txt
Documentation Is the Contract Surface
A request can match the schema and still do the wrong thing. The docs have to explain what those fields mean in use.
Topics: documentation · sourcey · agents · open-source · llms-txt
For the numbers behind the Catalog, see the State of Startup Credits and the State of Agent Readiness.