Look back through a month of reader questions. If several people asked how to price their work, that could be a theme. “What should I charge for revisions?” is an article within it. The distinction helps you choose what to publish next without writing the same piece twice.
A practical example
“Pricing freelance work” could sustain a dozen articles. “Our June pricing webinar” probably needs one announcement. The difference is what happens in July: readers will still need to quote a rush job, charge for revisions, and decide whether to offer a discount.
Give each theme an edge
Imagine an editor sorting three reader questions. “What should I charge for a second revision?” belongs under pricing. “Who approves the final version?” belongs under managing client projects. “How do I open an invoice template?” may need a support answer rather than a new editorial theme. The word “client” appears across the library; the reader’s decision is what separates the shelves.
Try writing a one-sentence boundary for each candidate: “Pricing covers how much to quote and what that amount includes; collecting an overdue invoice belongs elsewhere.” If two themes keep claiming the same questions, narrow their boundaries or combine them. You do not need a fixed number of themes.
Start with what readers actually ask
Gather questions from emails, comments, support requests, sales calls, search queries you can see in your own site data, and the forums or groups where your audience already talks. Write each question in the reader’s words. “How do I know if my idea is worth doing?” is more useful than a keyword phrase because it shows the decision behind the search.
Look for patterns rather than one memorable message. If several people ask about pricing, time management, or hiring a first contractor, those are candidates for a theme. A single unusual request may still deserve an answer, but it does not establish a long-term topic area.
Use themes to organize the library
Themes help you arrange articles so readers can move from a general introduction to a more specific next step. Link related posts to each other, and make sure each theme has an entry point that explains the subject plainly. A reader should not need to know your internal labels to find the right page.
Review the themes after a few months. If readers keep asking about a subject outside your current set, consider whether a new theme is needed or whether an existing one should be narrowed. Themes should change slowly, because frequent changes can make the library feel scattered.
Leave a little space outside the themes. A one-off announcement can be useful without becoming a category. Reconsider the categories when real questions repeatedly fall between them, not every time someone suggests a headline.
Start with what readers actually ask
Gather questions from emails, comments, support requests, sales calls, search queries you can see in your own site data, and the forums or groups where your audience already talks. Write each question in the reader’s words. “How do I know if my idea is worth doing?” is more useful than a keyword phrase because it shows the decision behind the search.
Look for patterns rather than one memorable message. If several people ask about pricing, time management, or hiring a first contractor, those are candidates for a theme. A single unusual request may still deserve an answer, but it does not establish a long-term topic area.
Separate durable themes from temporary campaigns
A durable theme addresses a problem that will still matter after the current season, tool release, or news cycle has passed. Starting a small business, communicating with customers, and planning a realistic schedule are examples of recurring needs. A campaign may be tied to a deadline, a product launch, a holiday, or a platform change that could alter the advice within a few months.
Test each candidate with a simple question: Would a reader from next year still need this answer? If the answer depends on a date, a specific app interface, or a promotional window, mark it as a campaign. Campaign posts can be useful, but they should not be the foundation of your editorial plan.
Choose three themes
Three themes are usually enough to guide a steady editorial plan without forcing every article into an unrelated category. Pick themes that match what you can explain well, what your audience asks about most often, and what you can update responsibly. Write a short definition for each one, including the reader it serves and the kinds of questions it covers.
Avoid choosing a theme so broad that it has no boundary. “Marketing” includes too many unrelated decisions. “Choosing a simple marketing calendar for a solo owner” is narrower and easier to test. A useful theme makes it clear what belongs and what does not.
Test future ideas against the themes
When a new idea appears, place it against the three themes. Does it answer a question inside one of them? Would a reader who came from an earlier article reasonably want this next? If the idea belongs to none of the themes, consider whether it deserves a separate area, a one-time article, or no article at all. Keeping a short list of rejected ideas can save time when the same thought returns.
Also check for overlap with existing articles. Two articles can share a theme if they answer different questions, such as one on choosing a theme and another on finding article topics from customer questions. If they answer the same question for the same reader, update the existing article rather than creating a second version.







