HowToClaudeAtoZ Public Roadmap

Every page on this site starts as a GitHub Issue. That means you can see exactly what is being worked on, what is planned, and what has already been published — and more importantly, you can vote on what gets written next. The most-upvoted issues move to the top of the writing queue. If there is a guide you need, this is the page to visit and the 👍 reaction is the mechanism that gets it written.

The roadmap updates automatically on every site deploy. When a page moves from planned to in progress, or from in progress to published, the status card changes. You do not need to check GitHub directly — this page reflects the current state of the site.

How Voting Works

The kanban board below shows all tracked pages across three columns: Planned, In Progress, and Published. Each card links directly to the GitHub Issue for that page.

To vote for a page you want written:

1. Click the card for the page you want.
2. This opens the GitHub Issue in a new tab.
3. Scroll to the bottom of the issue and click the 👍 reaction.
4. That is all. Your vote is counted.

You need a GitHub account to vote. If you do not have one, creating a free account takes two minutes and is worth it — the same account lets you contribute prompts to the Prompt Library, suggest new pages, and comment on issues to explain why a particular guide matters to you.

The votes are visible on each issue and are checked regularly when deciding which planned pages to move into the writing queue. A page with fifty 👍 reactions will be prioritised over one with two, everything else being equal. If you want a page written urgently, sharing the issue link with others who would find it useful is the most effective thing you can do.

What's Coming Next

The pages currently in the writing queue are the ones in the In Progress column above. These are actively being researched and drafted and will be published within the next few weeks.

The Planned column represents the full backlog. Every issue there has been scoped — we know what the page needs to cover, what questions it should answer, and roughly how long it will be. What determines the order in which they are written is primarily community votes, with secondary weight given to pages that fill obvious gaps in the existing content.

A few areas that are heavily requested and moving up the queue:

Claude for coding workflows. Several issues cover using Claude Code for real development tasks — reviewing pull requests, writing tests from existing code, explaining legacy codebases, and generating documentation from source. These have consistently high upvote counts and are moving into production.

Comparison pages. Pages that compare Claude to specific alternatives — GPT-4o, Gemini, Copilot — are among the most searched topics in the space. A set of rigorous, benchmark-backed comparison pages is planned and will be published as a batch.

Prompt engineering deep dives. The fundamentals guide already covers the basics. What the community is asking for is specificity: how to write prompts for particular industries, how to handle edge cases, how to build prompt libraries for teams. These are in the queue.

Claude API and developer content. The Claude Code and developer section of the site is the least complete pillar. Issues covering the API, MCP (Model Context Protocol), tool use, and building Claude-powered applications are planned and will be a focus over the coming months.

Suggest a Page

The roadmap only covers what has already been thought of. If you need a guide that is not on the list, open a new suggestion and it will be considered for the roadmap.

To suggest a page, open a new GitHub Issue with a title that describes the page you want and a brief note explaining what you are trying to accomplish and why existing guides do not cover it. The more specific you are about the use case — "I need to know how to use Claude to process PDF invoices and extract line items into a spreadsheet" rather than "guide about PDFs" — the easier it is to scope and write the right page.

Suggestions that come with clear use cases and detail consistently get added to the roadmap within a week of being filed. Suggestions that gather 👍 reactions from other community members are treated as high-priority additions.

Related Guides

• Getting Started with Claude — if you are new to Claude and want to know what it can actually do
• Prompt Library — community-contributed prompts you can use right now, ranked by upvotes
• Claude for Business Workflows — how teams are using Claude to automate repeatable tasks
• Advanced Claude Techniques — power-user features including Projects, memory, and multi-step reasoning