Have you ever worked with a CMS or CCMS that required lots of repetitive clicking through the UI to get things done? If the tool has a REST API, you can trade those clicks for natural language prompts by building an MCP (Model Context Protocol) server that's a simple API wrapper and use it with an AI agent skill. Here's how I did it using Claude to handle the coding.

I once sat by two engineering leaders who were phenomenal at handling requests for new software features. Often team members would come to them and insist on something like, We really need to add a new feature that lets users do X. Our users are clamoring for it. We might lose customers over this! The leaders would respond, What problem are you trying to solve? The conversation immediately shifted to a discussion about root causes, user goals, business value, and real evidence. More often than not, it quickly became clear that the proposed solution was not the right thing to spend time on.

If you're launching a docs-as-code platform (or retooling one) and want to use an open-source static-site generator, choosing one can be overwhelming. There are a lot out there, and it's tempting to look at which one has the most stars in GitHub and go from there. I've been there, and I've learned a few things the hard way! Here are some things to think about that might help with your decision.