I Blog with Raw HTML
41–50 of 137 posts
Re: I Blog with Raw HTML
#42Re: I Blog with Raw HTML
#43Re: I Blog with Raw HTML
#44> the blog you’re reading now is written in raw HTML, with md-block for markdown, and highlight.js for syntax highlighting. That doesn't sound like raw HTML to me. I write my own blog in raw HTML with a text editor (BBEdit), no JavaScript, and no server-side script either. For good measure, I also write my RSS feed in raw XML with a text editor.
For what it's worth, I don't think there's anything wrong with that. My blog is written in markdown. HTML is a deeply unpleasant thing to write blogs with.
Re: I Blog with Raw HTML
#45> the longest lived one is based on hugo Upgrading hugo is not straightforward due to the backward incompatibility changes. Too much changes to care for a static generator.
Re: I Blog with Raw HTML
#46Regarding the topic, I resonate with the concern about personal blog having to follow the convention of certain technology. Wouldn't say I enjoy reading it (or any site) without some minimal styling though.
Re: I Blog with Raw HTML
#47Blogging in raw html means you fire up emacs, tramp to the blogs index.html find the last closing p tag and underneath put the post headline and timestamp and an opening p tag on the next line and you are off to the races. Of course opening the index in tramp, putting the heading, timestamp and p tag goes into a function or paused kbd-macro so it fits into Mx blogthis
You do it just like that. But with vi.
Re: I Blog with Raw HTML
#48Re: I Blog with Raw HTML
#49I'm blogging with Raw HTML since the beginning of this year. The biggest missing piece is probably RSS support which makes me sad. I can write a script to generate that from the list of article but I'm not sure if there's better way.
It's a GitHub Action that regularly scrapes your page and checks for new entries, turning it into an RSS feed. Set up a redirect yourblog.com/feed -> you.github.io/feeds/feed.xml, then you're golden.
Re: I Blog with Raw HTML
#50> However, even a static site generator will deprecate some features one day No? You don't need to upgrade to the version that deprecates. Besides, what features are you using with such a simple blog the are at risk?
I used wintersmith.io. At some point it was abandoned and eventually the node version needed was old and other stuff associated with it. It became a hassle.
Ahhh...