> ## Documentation Index
> Fetch the complete documentation index at: https://portfolio.subinb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 📝 Posts

> Articles, insights, and perspectives on technical writing, AI, and developer documentation.

I write about the intersection of technical communication, AI tooling, and developer experience, drawing from real-world work at PayPal, Aquera, and Nokia.

## Latest

<Update label="Live rendering">
  <Card title="Rendering a GitHub README in Mintlify Without Copying It" icon="code-branch" href="/posts/live-github-readme-mintlify" cta="View post">
    How I added live GitHub README and `SKILL.md` rendering to this portfolio while keeping GitHub as the source of truth.
  </Card>
</Update>

<Update label="AI in docs">
  <Card title="When AI Reads Your Docs Before Developers Do" icon="sparkles" href="/posts/ai-in-docs" cta="View post">
    Exploring four dominant strategies: contextual menus, AI-enhanced search, MCP servers, and embedded assistants.
  </Card>
</Update>

<Update label="Agent scores">
  <Card title="Fern's Agent Scores vs Cloudflare's Is Your Site Agent-Ready" icon="robot" href="/posts/agent-scores" cta="View post">
    I compared Fern's agent scores against Cloudflare's Is Your Site Agent-Ready? and found a key gap most docs teams haven't addressed yet.
  </Card>
</Update>

## Topics

<CardGroup cols={2}>
  <Card title="Docs-as-Code" icon="code-branch">
    Version-controlled documentation using Git, CI/CD pipelines, and linting tools like Vale.
  </Card>

  <Card title="API Documentation" icon="plug">
    REST API references, OpenAPI specs, and onboarding guides that reduce developer time-to-first-call.
  </Card>

  <Card title="Agentic AI" icon="wand-magic-sparkles">
    Practical AI agents in documentation pipelines, from content generation to automated testing.
  </Card>

  <Card title="Developer Experience" icon="terminal">
    Writing that puts the developer first: clear onboarding, minimal friction, zero assumptions.
  </Card>
</CardGroup>

## 📬 Have a Topic in Mind?

If you'd like me to write about something specific, or want to discuss a collaboration, feel free to reach out.

I'm always happy to explore new writing projects, speaking opportunities, or content partnerships. [Email me](mailto:subin23k@gmail.com).