3 ms·
As we are on HN, I'm going to assume that you are comfortable using Github and can follow instructions. Write it on Github and publish on your domain. Github h
by Brajeshwar 4y ago
As we are on HN, I'm going to assume that you are comfortable using Github and can follow instructions.
Write it on Github and publish on your domain. Github has an option for you to fire up a web-editor (VSCode) right there in the browser with the keyboard `.` (<- that is a period). So, you can write right then and there (I do it quite often these days).
When publishing, choose a Jekyll theme of your choice from Github Pages[1]. Your focus now are just enough plain text (Markdown).
If you want to bring it to your desktop/device, just checkout the repo and write. These days, my choice is to just write in Obsidian and don't even try to run Jekyll.
What do you get out of this? The simplicity of focusing on your writing with almost Plain Text while Github takes care of your theme, hosting, SSL, and custom domain[2] for FREE. I have been on the Internet long enough to know that the best intentioned services will go away one day and so you need to be able to own your content and use tools to publish them the way you want.
Of course, you will need to book a domain and own it. I like Cloudflare[3] that takes care of pretty much everything you want to do with a domain for free. If you so wish, you can even let Cloudflare do the page building[4] and hosting while you keep Github for the source.
Plug: I build a super simple Jekyll theme[5] just so I can do this. I wrote an article about it on my website[6].
1. https://pages.github.com https://pages.github.com
2. https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site https://docs.github.com/en/pages/configuring-a-custom-domain...
3. https://www.cloudflare.com https://www.cloudflare.com
4. https://pages.cloudflare.com https://pages.cloudflare.com
5. https://oinam.github.io/oinam-jekyll/ https://oinam.github.io/oinam-jekyll/
6. https://brajeshwar.com/2021/brajeshwar.com-2021/ https://brajeshwar.com/2021/brajeshwar.com-2021/
- jez 4y agoTo underscore this comment: by simply enabling GitHub pages on a GitHub repo, it will automatically render Markdown to HTML as soon as you push the repo. If you want, you can layer on Jekyll and a custom theme down the road—but if you know how to write Markdown in a GitHub repo, you can have a blog live in 2 minutes, and then get started on those articles you mention are already in your head.
- rg111 4y agoI highly recommend against Jekyll themes, as updating them is a total pain.
- Brajeshwar 4y agoI'm honestly surprised by this statement. Why not just use the gem or the remote theme and never even deal with anything that constitutes the theme, except, maybe, the `_config.yml`. I do that quite often when I need to fire up a site. I know, I'm kinda from the old-school world and Jekyll was magic when it came out. I think I got comfortable.