a) own website b) write on something like medium c) use in built article feature on LinkedIn
It's hosted on DreamHost. It's all custom, I glued it together with Markdown, CSS, and a little Python. I've been with them for years and I can still recommend them. I'm not sure the exact location matters though. Success comes not from the venue but bringing an audience.
Also the key to successful self-promotion is to spam your own stuff tirelessly until the heat death of the universe, so here we go:
But it seems that most HN'ers use a static site generator and push to Github Pages.
EDIT: might as well give the link: https://theandrewbailey.com/
My "blogs" are "one thought a day" (sometimes I post on this blog, sometimes I post on that blog) which also includes the list of movies I've watched (along with my brief thoughts), some TV shows (again with thoughts), books I've read (with mini-review), albums I've heard (with mini-review), art I've drawn, music I've made, problems I've solved, thought's I've thunk, and science papers I've digested.
And it goes all the way back to 1976, from childhood drawings and musings about programming problems at 12 years old only to discover someone had the same thought decades earlier, all the way through to "I was standing in the shower this morning and had this thought about artificial intelligence..."
I don't write to gain traction or popularity (tried it for a year, hated myself more than I usually do), and I am pretty sure if I did get any notoriety, I'd lose interest in publishing my writing on my blog pretty darn quick. I write because I want too. I want to gather my thoughts, and putting out something that someone else might read, even though nobody will read, means I have to actually pay attention to what I am saying about a subject.
In the off-chance your writing becomes noticed, you'll have it there.
Another key difference is discoverability of the blog/content. Something like LinkedIn leverages the platform so the post gets in front of people (however how that happens is outside your control). A self hosted website does not have any direct way to attract/retain the audience (you need a way to get inbound traffic, and then a way to get people to keep coming back). To me, this part seems like the more challenging bit relative to the tech stack and I'm curious what other perspectives folks have here.
I started out with Wordpress circa 2011 but I switched to Pelican/AWS once the plugins became available to use Jupyter notebooks in the blogs (I'm a geoscientist so I like to show numerical/computational stuff in the posts, although it's been a few years).
More recently I've implemented some cool plate tectonics visualizations in D3.js:
https://rocksandwater.net/blog/2020/11/tibet-blocks-js/ (tectonics of India-Asia collision)
https://rocksandwater.net/global-block-model/ (work-in-progress global tectonic plates/blocks)
For those who are primarily interested in blogging for writing purposes (i.e. primarily text based) then going with a wordpress/medium type centralized solution sounds great. For me, SSGs can better deal with the content that I make, and pushing to AWS is really not that hard.
Of course I'm not really interested in wide visibility either (pretty niche stuff here...).
Hosting on platforms like Medium is good for views (so I've heard) but I'd be concerned about relying on someone elses platform. What happens if the platform goes downhill and your stuck with them? What if they shut down? What if you're wrongfully banned?
Guess it just comes down to preference and what you find important.
If on the other hand, you want to make money off your writing, like Matt Taibbi, then Substack is the place for you. They give you most of the royalties. Ted Gioia explains it in his interview with Rick Beato.
Blog is built with Jekyll. Treating GH as a CMS means I have a diff built-in to my platform. I also have a GH action that can schedule merges for post PRs. No one really cares to look through the blog source code but I have GH premium so that the pages repo can be private -- coupled with the merge scheduler this means no one can see the post before it goes live on my blog.
Other than that I have a static site landing page hosted on Netlify, also a private repo. Both sites are under the same domain:
* https://pivic.blog: my new blog that runs on Mataroa. I write in English about anything here. SSG, extremely small load time.
* https://niklas.reviews: my book reviews in English. SSG, Jekyll/Netlify.
* https://niklas.rodeo: thoughts in Swedish (my mother tongue). SSG, Jekyll/Netlify.
I've also written on https://niklasblog.com for about 25 years; this is a WordPress blog that I might kill. I'll see about that.
I wrote my own static site generator[0] to suit my needs. It’s not especially fancy - just a series of JSON config files and then a notion of “posts” and “pages” that are in Markdown format.
The code gets pushed to sourcehut and uses a build stage to deploy the site.
None of this is especially novel - I wrote the static site generator mostly because I was frustrated with how complex some of the more flexible existing tooling is. Nothing wrong with those tools, just more complicated than I need.
It's definitely more complex than raw HTML purists would prefer. I'm using NextJS with static site generation to generate static HTML from my React code. I'm also using MDX to automatically compile my articles, which are written in Markdown but I can embed React components in them.
Source is available at the bottom of the page. All feedback welcome!
This year, I rewrote the whole thing in Next.js and now it's somewhat more presentable.
I don't mind because in my experience it improves readability (I'm non-native) but I guess it depends on which editor you get and in general how do you feel about it.
Moreover, Hackernoon is to share a story / something meaningful to others. It's not for a PR about you launching a new feature for your product. In these cases I still use medium.
2018 I think I had made my yearly objective to be back to hosting a more live site. I have some WIP persistence layers that I want to power it all. A desire to use webcomponents & ActivityPub- with my homesite as basically a well tailored feed reader that happens to point first at my content.
I have written a couple tbings on LinkedIn, because I more or less wanted some practice. But not a lot.
Mainly... I guess I ought confess.... I write here. In comments. To me, my writing is about, not quite an arena of ideas (it's no so zero sum) but participating in exploring & thinking & searching for Truth and Meaning, Justice and Liberty, Progress and Gain. Hashing things out, seeing a lot of different ways of viewing a thing, and finding a couple pivotal points or ideas to inject: that's really rewarding. I really enjoy the interlinked nature of the web, and having threaded conversations to engage in, that can branch out & talk to different ideas very much embodies similar values.
[1] https://slothblog.org/ [2] https://medium.com/@balle.johannes
I used to do very ~project-oriented blog stuff at tumblr, but I wanted to be able to consolidate things down to one site where I could have a ~main stream with all posts, while still being able to add new streams for big themes/topics/projects. (This works, though IIRC I haven't sorted out separate RSS feeds for each stream yet.)
My first post was a guide on how I did it with Hugo, Netlify and Wowchemy: https://nicolaslouge.com/post/how-to-create-static-website-h...
If you want to have your website, GitHub Pages + a static site generator works well.
Facebook/LinkedIn etc are the most closed gardens, and I wouldn't recommend them unless it's where your audience is and your posts are not intended to be evergreen.
Regardless of the above, I think what is crucial:
- Just write. Where is secondary and can be changed later, don't agonize over that. Just pick the first which is "good enough" and see if it fulfills your needs over the course of your blog posts.
- Make sure to have some backups anywhere. Every server can change its ToS, shut down, or make its usage (and data export) cumbersome.
Wordpress -> Static site generator -> Squarespace -> Static site generator
Over. And over again.
It's a constant battle between 1) wanting control over my data/customization 2) writing and publishing.
Never ending battle
I also used to "syndicate" my posts to Medium, which did help get a few eyeballs on my work, but I didn't like the direction Medium went so i gave it up. Ultimately I got sick of the grind that's required to build an audience.
I haven't posted anything for a couple years now, but I recently decided to rebuild my site to get rid of analytics and all that BS. I'm writing again but won't be posting anything until I have my custom CMS working. Then I'll probably be cross-posting to Substack, because I still crave validation like most people.
My fictional stuff is at https//writing.stonecharioteer.com
The blog is built using ablog + sphinx. I am not very happy about how it looks on mobile. I have to hide the archives and wordcloud because it appears above the article on mobile mode, which annoys me.
I want to use pure sphinx for the articles. Mainlynl because ablog isn't compatible with Furo, the best sphinx theme IMO.
I use Sphinx because it supports the RST format. This is superior to markdown because of the directives, and internsphinx is amazing.
For the first year or so I also published every new post on Medium and dev.to (with my site as the canonical URL on both) so that more than zero people would read my articles.
I was lucky enough to get a few of my code-heavy tutorial posts ranking well on Google for the niche I focus on and now that I have a couple hundred organic visitors to my own site each day, I've stopped bothering with Medium and dev.to.
This setup replaced my old Django on VPS setup. It's faster for more people, will never have scaling issues (not that Django did). Costs nothing. And I could switch to other services (even self host on a toaster) in a heartbeat. Static site generators are great for blogs.
No interest in a platform. I'd lose autonomy, my gut history, gain a lot of page weight... All for what? An online editor?
When done, I push to Github. Netlify's webhooks pick it up and auto-deploy by running my site generator (small stand-alone binary kept in the repo). They then host it with custom domain and TLS for free.
Whole process reduces to: edit the content, run local preview, commit, and push. Moments later it's live.
This led me to create my own tool [0] to make minimalist blogs with Markdown, no messy code or configuration needed. The end result is my site [1], which although barebones, I think looks decently good for now.
WordPress, Rocket.net (also where I work)
https://github.com/nathants/libaws/tree/master/examples/simp...
will probably switch to cloudflare+r2 soon since egress is cheaper.
r2 is fantastic. here is an mp4 screen recording uploaded adhoc yesterday. a friend was trying to setup tinysnitch and was wondering what prompts looked like when visiting netflix: https://r2.nathants.workers.dev/fcd5ca7a-3d25-4912-9404-2bc0...
site: https://nathants.com
although I (b.) also sometimes put stuff on dev.to.
https://fredlybrand.com/2021/10/28/better-writing-better-blo...
EDIT: https://socialism.tools/
or my blog on a shared tilde server, if i'm doing a project writeup rather than prose.
gemini://anachronauts.club/~voidstar/
(i'm a fan of the smolweb lately. text-only, content-first, no junkware.)
It's simple, fast, and I can move it easily if I want to.
I also publish a weekly newsletter (newsletter.dsebastien.net hosted on Revue).
In the future, I intend to migrate my newsletter and blog to Ghost (SaaS, not self-hosted for convenience), but to continue cross-posting when it makes sense.