technicalwriting.dev valid

technicalwriting.dev

A technical writing blog by Kayce Basques.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T23:00:18.157Z. Cached copy · Source on technicalwriting.dev

# technicalwriting.dev

> A technical writing blog by Kayce Basques.

## Blog

- [changelog](https://technicalwriting.dev/blog/2026/10/changelog/index.md): TODO
- [The wild west of polyglot docs sites](https://technicalwriting.dev/blog/2026/10/polyglot/index.md): A polyglot docs site attempts to combine the outputs from multiple docs generators into a cohesive whole. There isn’t really a great way to do this, yet.
- [Vector arithmetic on docs embeddings](https://technicalwriting.dev/blog/2025/10/arithmetic/index.md): What happens if we embed the full text of a guide on Supabase, then subtract the embedding for “supabase”, and then add the embedding for “angular”?
- [Understanding task types in the Gemini Embedding API](https://technicalwriting.dev/blog/2025/05/tasks/index.md): Should I care about the taskType parameter of the models.embedContent method?
- [Export Google Analytics data to Sheets via Apps Script](https://technicalwriting.dev/blog/2025/04/sheets/index.md): A tutorial that shows you how to export Google Analytics data to Google Sheets.
- [Automating code deletion with Gemini (and a little Python)](https://technicalwriting.dev/blog/2025/04/gn/index.md): Removing code from over 200 GN build files with Python and the Gemini API.
- [Sphinx + Bazel: the good, the bad, and the ugly](https://technicalwriting.dev/blog/2025/03/context/index.md): Strengths and weaknesses of orchestrating Sphinx projects with Bazel.
- [Orchestrate Sphinx projects with Bazel](https://technicalwriting.dev/blog/2025/03/tutorial/index.md): An end-to-end tutorial on managing a Sphinx project with Bazel.
- [Focus on decisions, not tasks](https://technicalwriting.dev/blog/2024/10/decisions/index.md): Documentation needs to help people make decisions, not just accomplish tasks.
- [Embeddings are underrated](https://technicalwriting.dev/blog/2024/10/embeddings/index.md): The ML technology that might end up having the biggest impact on technical writing.
- [Exploring the intertwingularity of a docs site](https://technicalwriting.dev/blog/2024/10/intertwingularity/index.md): Building a web crawler to quantify interconnected knowledge.
- [Deeplink to specific PDF pages](https://technicalwriting.dev/blog/2024/08/pdf/index.md): Append #page=X to your URL, where X is the page to link to.
- [Life of a Sphinx build](https://technicalwriting.dev/blog/drafts/life/index.md): TODO

Machine-readable: GET /v1/resolve?q=technicalwriting.dev · GET /v1/domain/technicalwriting.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for technicalwriting.dev:
1. POST https://agentwebmap.com/v1/sites/technicalwriting.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://technicalwriting.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/technicalwriting.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/technicalwriting.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.