Sustainable Online Publishing

Sustainable Online Publishing

Every few months someone asks why I bother with a website when I could just post on Facebook. Fair question. Signing up takes five minutes. The audience is already there. You don’t have to think about hosting or deploys or why your build failed at 11pm.

I still wanted my work on the web without begging an algorithm for reach. Social makes starting easy. The catch is you don’t own the platform. Rules change. Reach throttles. Accounts get restricted when enough people complain. I learned that the hard way when I lost old PHP hosting and a chunk of my work with it - not a social ban, but the same lesson: rented land is rented land.

Publishing only on platforms you don’t control isn’t sustainable if your voice matters past this quarter.


Social is a lobby, not a library

Facebook, X, YouTube - I still use them. They’re fine for getting a link in front of people. They’re a terrible place to keep the only copy of something you care about.

Terms of service shift. Monetization rules change overnight. Content disappears behind logins or dies when the app pivots. Your best thread from 2019 isn’t on your resume - it’s on their servers, and you can’t export it cleanly if they decide you can’t.

I don’t treat social as my archive. I treat it as the thing I point at my archive.


Sustainable publishing = a domain and files you control

Domain - cheap annual rent on a name people can remember (jorap.com). Buy something you won’t cringe at in five years.

Hosting - where the files actually live. Classic hosting bills monthly. Static hosting can be free if you’re willing to learn a little Git and Markdown:

PieceRole
Hugo (or similar)Markdown → static HTML for the main site
GitHubVersion control + backup
Cloudflare PagesBuild and serve on push - free tier

No database, no admin panel, no PHP cron jobs to babysit.


What I don’t mean by “sustainable”

I’m not saying quit social. I’m not saying build everything custom to prove you’re serious. And free hosting doesn’t mean zero work - you trade a monthly bill for Git pushes and Markdown files.

What I mean is simpler: the real copy lives somewhere you control. Social is the megaphone. Not the vault.


If you’re starting from zero

  1. Buy a domain you won’t hate in five years
  2. Pick a static generator you can live with (Hugo worked for me; write down the version number the day you install it)
  3. Put content in Git from day one - that’s your backup whether you think you need it yet or not
  4. Connect Cloudflare Pages (or Netlify, etc.) to auto-deploy on push
  5. Share links on social - don’t write only in the social text box

You don’t need the full stack on day one. Domain + Git + static hosting is enough.


Bottom line

Social media is a great lobby. It’s a bad foundation.

Sustainable online publishing is your domain, your files, your deploy - with social optional when you want people to notice.

The stack can be free. The habit of owning your work is the part that compounds.

comments powered by Disqus
Top Reasons to Create and Maintain Your Own Website

Top Reasons to Create and Maintain Your Own Website

Every time I tell someone I run my own website, they ask why I don't just post on Facebook. After years of watching platforms die and rules change, here's why I keep my own corner of the internet.

How I Built JoRap Notes: My Journey from Expensive Hosting (and Better!)

How I Built JoRap Notes: My Journey from Expensive Hosting (and Better!)

I lost my old PHP hosting (and a chunk of my work with it). A weekend of fumbling later, I landed on Hugo + GitHub + Cloudflare Pages - faster, and honestly better than what I was paying for.

HugoPlate: The Theme Quietly Powering This Site

HugoPlate: The Theme Quietly Powering This Site

After losing half a Saturday to theme-shopping, I picked HugoPlate - and a year and change later, I'm still on it. Here's what comes in the box, what I changed, and where it still bites.

Static Site or CMS? How I Pick the Stack

Static Site or CMS? How I Pick the Stack

The stack debate is usually the wrong fight. Who publishes, what changes live, and whether you need logins pick static vs WordPress (or a git CMS in between) better than any framework ranking.

Why I Focused on Open Source Technologies

Why I Focused on Open Source Technologies

Open source wasn't a purity test for me. It was cheaper hosting, inspectable code, portable files, and communities big enough to find work in. Here's how that shaped my stack.

Consistent AI Output for WordPress Builds

Consistent AI Output for WordPress Builds

Month one with AI on WordPress builds I was thrilled. Month three I finally got consistent output - helpers, reference examples, and a short rules doc that stop every feature from drifting.

Garden notes that share topics with this post.

Digital Garden

My garden is where notes grow in public - linked, imperfect, alive on Hugo and Git.

Drafting in Public

Drafting in public keeps the garden honest with rough posts and feedback instead of private hoarding.

The Garage Concept

The vault is the garage for scraps and experiments - the blog is the showroom, kept separate.

Note Relationships

My graph shows extends, contradicts, implements, alternative - not just two notes mentioning the same word.

Commonplace Book

Before linked notes, quotes and ideas lived in one book worth reopening.

Success is Stewardship

Success is borrowed - accountable for how gifts are used, not entitled to keep them forever.

Random Note

One garden note picked at random — shuffle for a new pairing with this post.

AI prompt

Loading…