4 ms·
I appreciate the author sharing technical details about how they build their blog. I do. However I'd like ask the HN community here to share some examples of r
by blenderob 2y ago
I appreciate the author sharing technical details about how they build their blog. I do.
However I'd like ask the HN community here to share some examples of really simple blogs? Those that do not take building Rube Goldberg machines to publish the blogs. Perhaps those where the posts are just simple HTMLs. I'll take slapping a header and footer with some scripting or SSIs. But that's about it. Do you know any such simple examples of blogs? I think such blogs are under-appreciated and should be highlighted more often on HN.
- rpgbr 2y agoMine?[1] Pure HTML/CSS handwritten, no JS, powered by Jekyll. [1] https://notes.ghed.in https://notes.ghed.in
- medstrom 2y agoAs someone with knowledge of JS, my favored static site generator is SvelteKit. I feel like for me, Jekyll and such things no longer offer a simplification.
- ReleaseCandidat 2y ago> However I'd like ask the HN community here to share some examples of really simple blogs? My static site generator is quite simple (650 lines of JS including the http server, almost half of which are the header and footer templates), it uses markdown-it (and some plugins) to convert Markdown to HTML, Katex to convert Latex to HTML and Highlight.js for syntax highlighting. The generated pages are static, only JS is to change light/dark mode and open all "hints" when printing. And right now I'm adding RSS/Atom support. https://codeberg.org/Release-Candidate/pages/src/branch/source/markdown2html.js https://codeberg.org/Release-Candidate/pages/src/branch/sour... https://codeberg.org/Release-Candidate/pages/src/branch/source/package.json https://codeberg.org/Release-Candidate/pages/src/branch/sour...
- neogodless 2y agoIt's not a very good blog but it is simple HTML + vanilla JS. https://retorch.com/blog/ https://retorch.com/blog/
- nicbou 2y agoMine is halfway there. It uses a static site generator that I built for another website which I run for a living. It’s also used as a reference implementation for that static site generator. The problem is that a simple setup becomes too simple for certain purposes. If you edit content for a living, you gain more from useful features than you lose from complexity. In my case, every feature I added was to make my work easier: constants, linters, image compression etc. I suspect that the author here also faces the same issue. https://nicolasbouliane.com/projects/ursus https://nicolasbouliane.com/projects/ursus
- spc476 2y agoMy blog [1] is mostly dynamic (only static pages are the main index.html page and the various feed files) and uses a simple template based system, and each entry is a separate file. The engine [2] also supports adding new entries via POST and PUT. I've been using the same engine for over 24 years now. [1] https://boston.conman.org/ https://boston.conman.org/ [2] https://github.com/spc476/mod_blog https://github.com/spc476/mod_blog
- thomas_moon 2y agoI just started my own with literally no code. 1. Obsidian to compose markdown 2. Git extension to commit and push changes to github 3. Github Pages 4. Cloudflare for image hosting Literally write markdown, push 3 buttons, its live within 2 min. My first post was actually about figuring it all out. Sorry if its poorly written. https://tmunayyer.com/Projects/making-this-blog.html https://tmunayyer.com/Projects/making-this-blog.html
- thomas_moon 2y agoGoing to reply to my own post with a disclaimer: Go with HTML instead. As soon as you even try to position photos, you need HTML and CSS haha. Mine was a bit too simple but I was optimizing for absolute lowest friction possible to writing & publishing.