![]() Now we’re talking! It’s a really simple standard too. … an mention that works across websites so that you don’t feel immovable from Twitter or Fb There’s a whole suite of technologies involved, but the piece of the puzzle that I’m interested in right now is the WebMention, described as In the time I’ve been mostly not blogging, some of the folks who kept at it have been cooking up a collection of tools, technologies and standards under the IndieWeb banner. There was a sense of connectedness that’s missing from a collection of articles. The old site had comments, and pingback links to other blogs. 2īut the thing I miss about the old, slow, hard to maintain version of this site, is the sense of connection. Again, fiddly to set up, and arguably only of philosophical benefit, but worth it, I think. ![]() The markdown files never exist anywhere that anyone can edit them. Yes, Emacs is an editor, but if you do 「 emacs all‑ ‑‑batch ‑l ox-hugo ‑‑eval=’(org-hugo-export-wim-to-md t)’ ‑‑kill 」 it will happily execute any lisp code you care to ask it to. Then one day I read an article about using Github Actions to build an ox-hugo based site by installing emacs and ox-hugo on the VM that does the build step and generating the markdown files during the build by running Emacs ![]() I didn’t worry about this for ages, but it niggled at me. It’s certainly not the sort of file that should live in the repository. It’s not a file that should be left around to be edited willy nilly because it could get out of sync with its source file. ![]() The generated file is an artefact of the build process and simply repeats the info in the org file, which should be our single source of truth. That’s the sort of thing that makes me itch, because there were two files for any given article: the org file in which I write all my articles article.md the generated file that hugo uses to build the site. md files from an org source, which are then used to generate the site, and I had things set up to autogenerate the html whenever I commited to the main branch of the blog repo, and the git server hook based system I was using only worked if those exported files were in repo. As I say, a tad fiddly at first, but once it’s in place, it just works.Įxcept… ox-hugo works by generating. I’d go so far as to say it’s a point of pride. So I use ox-hugo, there’s a bit of configuration needed to make it work the way I like, but I prefer to change software to accommodate me rather than change me to accommodate software org files, so I could just lean on that, but the way Hugo treats org files seems slightly out of whack with what I think of as the Org way and I’d end up having to stick with the subset of org syntax that Hugo know. For instance, markdown is all well and good, but I’ve been doing most of my writing in Org Mode 1 so I really want to stay in Org mode to write these blog posts. All that remains is to upload those files to the appropriate directory on your server and all is well.īut never underestimate the ability of a long time Emacs user to complicate things.īut never underestimate the ability of a long time Emacs user to complicate things. Simple markdown formatted files go in at one end and a slim, fast and easy to serve website comes out the other end. The beauty of using a static site generator to build your website is supposed to be that it’s all delightfully simple. Keep it Simple, But Where's The Fun In That? Post Neighbors: Previous post | Next post Keep it Simple, But Where's The Fun In That? Folk singer, photographer, carer and occasional programmer. The personal website of Piers Cawley ( they/ him)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |