This is the most under-used asset most writers have. Four years of posts is a book's worth of thinking already done, already tested on readers, already edited once. The reason so few of these collections are any good is that people ship the archive rather than making a book out of it.
Choose one argument, then cut to it
A blog is allowed to be about everything you were interested in that month. A book is not. So the first decision is what the book is *about*, and it has to be narrower than what the blog is about.
- List every post with its title, date and word count. A spreadsheet is fine and the length matters later.
- Write the book's argument in one sentence — the thing a reader will be able to say they got.
- Mark each post: core, supporting, or out. Be harsh. A post you are fond of that does not serve the sentence is out.
- Expect to keep about a third. If you are keeping most of it, the argument is too broad and the book will read as a feed.
Order for a reader, not for the calendar
Chronological order is the one arrangement guaranteed to be wrong, because it is the order *you* learned things in. A reader needs the order that builds.
- Foundations first. The post you wrote in year three explaining the basics goes near the front, whatever its date.
- Group into parts. Three to five parts of three to six chapters each is a shape people can hold.
- Put the strongest piece early but not first. Chapter two or three, once the reader is committed and still deciding whether this was worth it.
- Merge the repeats. Every archive has four posts circling the same idea. That is one strong chapter, not four thin ones.
- Split the sprawlers. A 4,000-word post that covered two things is two chapters.
The rewrite pass, which is not optional
Posts are written to be read alone, on a screen, on a particular day, by someone who follows you. Every one of those assumptions has to come out.
| In the post | In the book |
|---|---|
| "Last week I wrote about…" | "In chapter three we saw…" — or cut it |
| "As I write this in early 2023…" | Either date it explicitly or remove the anchor |
| "Click here to read more" | The point itself, or a citation |
| Twelve inline links | Two or three that earn a footnote |
| "In my last newsletter…" | Gone |
| An embedded tweet or video | A description, or a quote with attribution |
| "Subscribe for more" | Once, at the back, where it belongs |
Links deserve their own thought. A post can be a hub of twenty references; a book on paper cannot follow any of them. Keep the ones a reader would genuinely want to chase, render them as text they can type or as a short list at the end of the chapter, and delete the rest — including, especially, links to your own other posts, which in a book become links to chapters.
Then read the whole thing end to end in one sitting. Repetition is invisible when posts are months apart and glaring when they are pages apart: the same anecdote twice, the same definition three times, the same joke.
Add the connective material
This is what separates a book from a PDF of posts, and it is usually less than 20 percent new writing.
- An introduction that states the argument and says who the book is for.
- A page or two opening each part, saying what it covers and why it comes here.
- Transitions between chapters — a sentence at the end of one pointing at the next. Posts have no reason to lead anywhere; chapters do.
- A conclusion that does something more than stop.
- Anything the archive never covered because it was too obvious to post about and is now a hole in the argument.
Getting the text out
Most platforms will give you your content in a form you can work with, and Markdown is the one to ask for since it is what most blogs are stored as underneath.
| Platform | Route |
|---|---|
| Ghost, Hugo, Jekyll, Astro | The posts are already Markdown files |
| WordPress | Tools → Export gives XML; convert, or use a Markdown export plugin |
| Substack | Settings → Export, which produces HTML per post |
| Medium | Settings → Download your information |
| Notion-based | Markdown & CSV export — the cleanup is its own job |
| Anything else | pandoc post.html -t markdown -o post.md, one at a time |
# HTML exports to Markdown, then one manuscript in your chosen order
for f in posts/*.html; do pandoc "$f" -t markdown -o "${f%.html}.md"; done
cat 01-*.md 02-*.md 03-*.md > manuscript.mdWhatever the source, budget for tidying: exported HTML carries wrapper markup, image paths point at your CDN, and code blocks often lose their language. It is an hour of work, and it happens once.
Produce it as a book, not as a download
The last mistake is doing all of the above and then exporting a document. A collection is judged on whether it feels like an object — and that is typography, page structure and a cover doing the work.
- Chapters open on a fresh page, so a part has a rhythm. In bukpress that is a line of three dashes.
- One typeface for the text, one for headings, set once and applied everywhere — the drift between posts written over four years should not be visible.
- Page numbers, and margins wide enough to hold the book, which is most of what typography is.
- A cover that works at thumbnail size — the sizes are here.
- Both formats. A PDF for the download and an EPUB for anyone who reads on a device, from the same file.
What you do with it afterwards is a separate decision: sell it, list it, or give it away as a lead magnet — a book made of your best work is a considerably better one than a checklist. The archive was already there. The book is the third of it you chose and the shape you put it in.