I stopped spending 40m formatting posts by using layout skeletons

I spent weeks writing technical posts that completely tanked on mobile.

I was spending 2 hours drafting in obsidian, testing the snippets, and checking the architecture

On my desktop monitor, the drafts looked clean

Then I opened one of the live posts on my iphone, it was unreadable.

A 4-sentence paragraph had stretched into 14 lines of unbroken text.

Readers on linkedin saw zero whitespace and scrolled away in 2 seconds

The code was solid, but nobody reads a solid wall of text on a 6-inch glass screen.

I only fixed the retention when I stopped guessing line breaks and started using a layout grid.

Today, I run a 3-tool workflow that separates the writing from the mobile formatting:

Raw capture in obsidian: I dump my terminal outputs, error logs, and architecture notes into local markdown without worrying about line breaks
Fluff removal in claude: I run the draft through claude with a strict prompt to cut passive voice, strip filler words, and keep sentences under 15 words
Layout extraction: I grab the structural skeleton from posts in blotato and that held high engagement on linkedin. It strips away the author's words and leaves the whitespace grid: a 1-line tension opener, a 2-line problem frame, 3 short mechanism bullets, and a diagnostic closer

I drop my cleaned notes straight into that empty grid and schedule the post

The structure makes the post scannable in 45 seconds on an iphone, while the substance stays 100% technical.

My drafting time dropped from 2 hours of manual reformatting down to 15 minutes of review.

When you post technical work online, do you write freestyle into a blank box, or do you draft inside a fixed layout grid?

0 comments

I stopped spending 40m formatting posts by using layout skeletons