Assorted methods:
- Project Per Post:
If you like short quickly-completed projects (I do) then every week you might just create five projects. You know that you will publish five posts per week, so to be sustainable you write five posts per week, even if you're one or two or ten weeks ahead. So you could just create five projects every week, and your weekly review checklist could remind you to do that. If you tend to do a bunch of posts in one week and none in another week, the flurry of projects, or the lack of a flurry, still gives you visibility.
This is week 28, so the projects could look like:
Project: Blog Post 28.1
Next Action: Choose topic
Next Action: (What are the actions? If they vary per post, then the project-per-post model might be particularly suitable.)
Project: Blog Post 28.2
Next Action: Choose topic
...and so on.
- Blog Post Project Chart
If you're going to have five "post projects" every week, and especialy if the actions for each post tend to be the same, you could skip using the project structure and instead make a chart or a spreadsheet or a list:
Post Number - Topic - Status - Next Action
28.1 - Squash bugs - Researching - find insect netting link
28.2 - Perennial scallions - Writing - Final polish
28.3 - Soluble complete organic fert - Researching - Is there such a thing?
The blog posts themselves could then be project support material where you put any actions beyond the "next action"--plus you could keep a list somewhere where you keep ideas for posts that are so far future that you're not working on them yet. If you stay well ahead, then you could just spruce up the list once a week, looking at the blog posts in work so far, finding new Next Actions for the ones that are complete, and so on.
This could interact with your main action lists in two ways:
-- A regular trigger to check for actions to do.
-- A regular, but less frequent, trigger to confirm that you're not falling behind. Or this could be part of your weekly review.
- One Post at a Time
The above assume that you're working on several ideas a a time. What if you're working on just one at a time, and all you need to know is how soon you'll be in trouble if it isn't done? In that case, you could have a single project:
Current Blog Post
Next Action: Write first draft
And, elsewhere, a trigger to remind you to see if you're ahead or behind. Whenever you do figure that out, you could rename that single project with its "on or before" completion date:
Current Blog Post (7/13)
Next Action: Write first draft
Edited to add: OR, the date on that project could be the date that you're going to run out of posts. So the above tells you that you're covered until 7/13, yay! And then when you finish that one and put it in the posting queue, you get to change the date to 7/14.