A Publishing Rhythm You Can Keep
Choose a pace you can sustain, build a buffer of finished posts, and compare two plans over twelve weeks with a program to see how a buffer keeps a blog going through busy weeks.
In this lesson you will
- Choose a pace you can keep
- Build a buffer of finished posts
- Compare two plans over twelve weeks
- Make a publishing calendar
About 22 minutes
Three weeks of silence
Priya starts strongly: a post every Tuesday and Friday. Then her sister visits, a deadline lands at work and a cold flattens her for a week. When she returns, the habit has broken, and she feels guilty about it, which makes writing harder. Nearly every blog hits busy weeks. The question is how to carry on publishing when life gets in the way. The answer is not more willpower. It is a buffer, a small stock of finished posts, and a simple rhythm you can keep.
Pick a pace you can keep
- Choose less than you think. One post a week for a year beats three a week for a month.
- Pick fixed days. Readers and search engines both learn a pattern. Fixed days also make planning easy.
- Count the real cost. Include writing, editing, images and publishing, which often takes twice as long as the writing itself.
- Allow for gaps. A plan that breaks after one bad week is a poor plan.
A model of two plans
The program below compares two ways of working over twelve weeks, using a made-up pattern of busy weeks: weeks 3, 6, 7 and 10 have no writing time. Plan A writes each post in the week it goes live, two a week. In a busy week nothing is written, so nothing is published. Plan B builds a buffer. It begins with three finished posts. In a good week it writes two posts, and one extra when the stock is below six. Each week it publishes two posts from the stock if it has them. The model is a simplification, and it shows the principle clearly.
from datetime import date, timedelta
# MADE-UP: weeks in which life got in the way (no writing time)
busy = {3, 6, 7, 10}
weeks = 12
# plan A: write each post in the week it goes live
live_a = sum(1 for w in range(1, weeks + 1) if w not in busy) * 2
# plan B: write 3 posts ahead in good weeks, publish 2 a week from the stock
stock, live_b = 3, 0
for w in range(1, weeks + 1):
if w not in busy:
stock += 2 + (1 if stock < 6 else 0)
if stock >= 2:
stock -= 2; live_b += 2
print("plan A, posts live in 12 weeks:", live_a)
print("plan B, posts live in 12 weeks:", live_b)
print("plan A weeks with nothing:", len(busy))
print("posts a week to reach 50 in a year:", round(50 / 52, 2))
# first eight publishing days: Tuesday and Friday from 3 November 2026
d = date(2026, 11, 3)
days = []
while len(days) < 8:
if d.weekday() in (1, 4):
days.append(d)
d += timedelta(days=1)
for day in days:
print(day.strftime("%a"), day.day, day.strftime("%b"))
n, start = 50, days[0]
weeks_needed = -(-n // 2)
print("weeks to 50 posts at 2 a week:", weeks_needed)
plan A, posts live in 12 weeks: 16
plan B, posts live in 12 weeks: 24
plan A weeks with nothing: 4
posts a week to reach 50 in a year: 0.96
Tue 3 Nov
Fri 6 Nov
Tue 10 Nov
Fri 13 Nov
Tue 17 Nov
Fri 20 Nov
Tue 24 Nov
Fri 27 Nov
weeks to 50 posts at 2 a week: 25
Plan A gets 16 posts live, and has 4 weeks with nothing. Plan B gets 24 posts live in the same twelve weeks, with the same four busy weeks, because it writes a little more in good weeks and spends the stock in bad ones. The numbers are not the point. The point is the shape: a buffer smooths out the bad weeks, so readers see a steady blog even when the writer’s life is not steady. Batching also helps, since writing several posts in one sitting saves the time of getting started each time.
A calendar to follow
The last lines list the first eight publishing days for posts on Tuesdays and Fridays starting on Tuesday 3 November 2026. At two posts a week, a blog reaches 50 posts in 25 weeks, about half a year. That is a useful picture: a blog that keeps going for half a year has a real body of work, and most blogs never get that far. If twice a week is too much, once a week would take twice as long, and that is fine.
- Choose publishing days and a number of posts you can keep in a bad week.
- Write a list of post ideas, so you never face a blank page.
- Batch: write or edit several posts in one sitting, when you have energy.
- Build a buffer of at least two or three finished posts.
- Review each month, and change the pace if it is too fast or too slow.
Writing every post the night before it goes live. One bad evening breaks the chain. Finish posts ahead, and schedule them if your tool allows it.
It is fine to take a planned break. Tell your readers, or schedule posts in advance. A short pause that is announced is better than a silent disappearance.
Practice for this lesson
Check what you learned
Five quick questions. Pick an answer and you will see straight away whether it is right and why.
What does a buffer of finished posts do?
- Slows you down
- Adds filler
- Loses readers
- Keeps you publishing in busy weeks
It smooths out weeks with no writing time.
How many posts did Plan B get live in the sample?
- 16
- 24
- 8
- 12
The buffer let it publish two a week in most weeks.
Why pick fixed publishing days?
- They are required
- They avoid editing
- They hide posts
- They make a pattern readers learn and planning easy
A steady rhythm builds a habit.
How many weeks to reach 50 posts at two a week?
- 25
- 10
- 50
- 12
Fifty divided by two is 25 weeks.
What is batching?
- Deleting old posts
- Posting daily
- Writing several posts in one sitting
- Buying posts
It saves the time of getting started each time.
Summary
- Choose less than you think and keep to fixed days.
- A buffer of finished posts smooths out busy weeks.
- Batch the work when you have energy.
- Planned breaks are better than silent ones.
Questions
How often should I publish?
As often as you can keep up for months. Once a week is a good start. Consistency matters more than frequency.
Is the two-plan model realistic?
It is a simplified model with made-up busy weeks, built to show the idea of a buffer. Your own weeks will differ.
Should I schedule posts?
If your tool allows scheduling, it is a good way to use a buffer. Check how your tool handles scheduled posts and time zones.
