Articles are live on Stacklist

Think about something useful you wrote a few years ago. A guide your clients still ask about. A post that explains what you do better than your website does.

Now try to find it.

It's probably wherever you were posting that year. A blog you stopped updating. LinkedIn, somewhere down the feed. A newsletter platform you no longer pay for. The writing is still good. It just lives in a place you left, and moving it somewhere else means making it again.

We call that content jail.

Why we built Articles

Your Hub on Stacklist already held videos, PDFs, links, files and image galleries. Writing was the missing piece. You could save a link to your blog post as a Card, but the post itself stayed where it was.

Articles fix that. Your writing now lives natively on Stacklist, in the same Stacks as everything else you've made. For example, the setup guide you wrote can sit beside the walkthrough video and the spec sheet, and when a client asks how something works, you send one link instead of three. One place for all your content and the network where it gets found.

Kyle, our co-founder, wrote the longer argument for why that matters, and published it as an Article: One place for your content. This post covers the practical side.

How do I move an article I've already published?

Most people reading this have already written something worth keeping. Start there.

1. Open the + menu and choose Import an Article.
2. Paste the link to an article on Substack, Medium or anywhere else you've published.
3. Stacklist finds it and shows you a preview: the title, the author and what's in it.
4. Choose Import as Article. It opens in the editor as a draft, ready to check and publish.

The original stays where it is. What lands on Stacklist is yours to edit, add to and put in your Stacks. Imports work one article at a time. The full walkthrough is in our help center: Import an Article from a link.

Or write a new one with Stacky

The editor gives you what an article needs: a title and subtitle, headings, lists, quotes, images with captions, and link cards that point at your other Cards and Stacks. You don't need to know Markdown.

Stacky works inside the editor. Ask it to start a draft, help you think something through, or rework a passage you've selected. Stacky suggests; you decide what goes in.

Your work saves as you go. A draft is private until you publish it. Once it's published, your edits go live, because there is one article, not a pile of copies. More in Write an Article.

What does someone see when I share an Article?

They start reading. When you share an Article, the link opens straight into the reading view. There's no sign-up wall in front of the words. It's one calm column with a serif body and nothing floating over the text.

The ask comes after the reading, not before it. Every Article ends with the writer, a Follow button and the Stack it lives in. If someone liked what they read, that's when they find out who you are and what else you've put together.

Update it once, and it updates everywhere

An Article is a Card like any other, so it can sit in as many of your Stacks as it belongs in. On a public Stack it can be the lead piece, with a Read Article button.

Fix a typo, and every place that article appears shows the fix. Nobody has to hunt down the old version. See Publish, share and update an Article.

Built to be found

Article pages are in Stacklist's sitemap and carry full article information for search engines. Each one also has a public Markdown version that AI agents can read.

As the owner, you can see saves and comments, and which search bots and AI agents came by to read your content. That tells you who read it, not what they did with it afterward.

Your AI assistant can write here too

If you work with an assistant like Claude, you can connect it to Stacklist through the Stacklist MCP. It can then create, edit, publish and unpublish Articles for you.

This one, for what it's worth, was drafted that way, then edited and published by a person.

Start with the one you'd miss

Pick the article you'd be most annoyed to lose. Bring it over, check it, publish it, and put it in a Stack with the things that belong next to it.

Then the next time someone asks the question it answers, you'll know exactly where to send them.