I remember the exact afternoon I stopped believing that good writers just sit down and produce. I was watching someone I admired prepare a long post for a publishing platform, and before typing a word they opened a battered folder and spent twenty minutes flicking through it. Screenshots, half-sentences, a few printed pages with scribbles on them. That folder was their swipe file, and it explained why their work always arrived with a shape already in it.
If you publish content for a living, or for the love of it, a swipe file is the cheapest upgrade you can make. Here are eight things I would put in one, along with the small human reasons each earns a place. Keep your own copy modest, and write a note beside every item saying what you noticed.
1. Opening lines that made you keep reading
Start here, because openings are where most of us stall. Save the first paragraph of any post that pulled you in, then jot a few words about the mechanism. Maybe it named a problem you recognised. Maybe it put you in a concrete scene. Over a month you will see the same three or four moves repeating, and that is your toolkit.
One small trick: when you save an opening, also save the sentence that followed it. The second sentence is where many drafts lose the reader, and seeing how skilled writers handle the handover from hook to substance is worth more than the hook itself.
2. Headlines that promised something specific
Collect titles that told you precisely what you would get, and also the ones that irritated you with vagueness. The second group teaches just as much. Write beside each what the promise was, in a short phrase. When you draft a title, you can hold it up against that pile and ask whether yours makes a promise a stranger could understand in a second.
I also keep a short list of title shapes, such as the question, the numbered list, the plain statement and the gentle contradiction. Each shape suits a different kind of post, and having them written down stops me defaulting to whichever one I used last week.
3. Layouts that respected a tired reader
Some pages feel like a kindness. The headings are spaced so a skimmer can find their place, the lists are short, the paragraphs breathe. Save a few of those and note the layout choices: how often a subheading appears, how long the longest block of text runs. Most platforms have their own house look, and it is worth studying how writers on the rules that matter when posting on Medium bend one format to carry very different subjects.
4. Posts that taught one thing well
Every field has pieces that teach exactly one idea and then stop. Those are rarer than they should be. Save a handful and write down the single sentence each could be summarised in. Then test your own drafts the same way: if you cannot state your post in one sentence, the structure probably needs work before the wording does.
5. Closing sections that gave the reader somewhere to go
An ending is a hand-off. Strong ones name the next small step, point to a related piece or invite a reply in a way that sounds like a person speaking. Weak ones repeat the introduction or fade out. Keep three of each, labelled honestly, and glance at them when you reach your own final paragraph, which is when energy tends to run out.
There is a kind of ending I now actively collect: the one that stops a beat earlier than you expect. After years of writing conclusions that summarised everything twice, I started saving posts that simply finished once the point had landed. Reading them side by side was like hearing the difference between a door closing softly and one slamming. I try to give my readers the soft version now.
6. Visuals that carried part of the argument
A diagram, a table or a simple chart can do work that paragraphs cannot. Save the ones where the picture clearly did something the words would have done clumsily. Pay attention to restraint: the best ones usually have fewer labels than you expect. While you are at it, save an example of a visual that failed, such as a crowded chart with a tiny legend or a screenshot so wide that the text vanished on a phone. Those cautionary specimens remind you what to avoid when a deadline looms. If you work in note-taking or workspace tools, a page such as this walkthrough of posting practices on Notion is a decent case study in how a structured workspace page can double as a published piece.
7. Community posts that earned replies
Forum and developer-community posts are underrated models, because their authors face an audience that answers back. Save threads where a question was written so clearly that the replies came quickly and kindly. Note what the asker included: the context, the thing already tried, the exact outcome they wanted. For writers aiming at technical communities, a guide to publishing an article on DEV Community sits well beside such threads, and the pairing shows how a post and its surrounding conversation fit together.
8. Evidence that your own taste is changing
The last item is odd but valuable: keep a few examples you once loved and now find only fine. Annotate how your view shifted. Taste develops, and recording the shift reminds you that your preferences are not fixed rules. It also keeps the folder honest, because you are less likely to cling to a style simply because it once impressed you.
What a useful note actually looks like
People often ask what to write beside an item, and the honest answer is that it should be short and specific. “Great intro” is useless. “Starts with the reader’s mistake, not the fix” is something you can act on. “Nice layout” tells you nothing; “Only one idea per subheading, and every subheading is a full phrase” gives you a rule you can apply by Thursday.
A good test is to imagine reading the note in six months with no memory of the item. If the note alone would still tell you what to do differently, it is doing its job.
How I keep the folder from becoming a junk drawer
It took me a couple of embarrassing attempts to learn this. My first swipe file ballooned within a month and became a place where good intentions went to die. Now I follow a few plain habits.
- I never save without a note, even a clumsy one.
- I sort by job (openings, titles, layouts) rather than by where I found the thing.
- Once a quarter I delete anything whose note I no longer understand.
- I record the source, so I can credit it or return to it.
- I write patterns in my own words and close the folder before drafting.
That last habit is the one that matters most. The folder is a place to borrow ideas about structure and feel. It is never a place to lift sentences. The distinction keeps the practice fair to the people whose work taught you something, and it keeps your voice yours.
Looking sideways for fresh material
A final tip, for when your folder starts to feel samey: go and look at the websites in neighbouring worlds. I once spent an evening browsing a flying-and-space themed academy-style website with menu areas for courses, licences and a blog, purely to see how a site with a lot to say sorts it into rooms. I came away with a note about menu order that changed how I laid out a resource page for my own readers. The subject had nothing to do with my work. That is exactly why it helped.
Start with ten minutes
Skip the app and skip the grand plan. Open a folder, call it something plain, and put in three items today: an opening that worked, a title that promised well and a layout you liked. Write one line about each. In a week you will have the beginnings of a habit, and the next time a blank page stares back at you, you will have somewhere to turn that is full of solved problems and your own observations. That is a lovely thing to have on a Monday morning.