Skip to Content

Planning a Personal Website with Hugo

So I’ve been going through my various online representations, trying to figure out what each one is for, and what I’m missing. Part of that has been moving my “blog,” such as it was, off of my main homepage and moving it to a dedicated platform for broadcasting writing. Now, I’m using WriteFreely at posts.emsenn.net to share some of my longer but more informal writing - this text is probably going to go there.

This leaves emsenn.net free to be mine, rather than belonging to my writing. You might think this would leave me without much content to put there, and in way, that’s true, but there’s also still a lot of information that one can provide about oneself to be a filled-out digital representation.

A note - I’m going to be using terms like agent, representation, avatar, user, person, and so on as I write about this stuff, and I’ll be doing so without what I hope is my usual precision. I’m not sure how I want to train myself to think about these things yet, so I’m not sure what terms I want to use for which concepts. I apologize if the current indecision makes this writing less intelligible or more verbose.

So, emsenn.net is free to be my “personal website.” Now… to think about what that means. It’d need to have information about me, as a person. I often find myself wanting to link to info about how to donate to me. I maintain a list of things I recommend folk read. I also maintain a list of my recent activities, my plans, and I’d like to start keeping a list of things I’m looking for help with.

There’s also things that are a part of the IndieWeb that I’d like to add, and other things like a /now/ page, which would have my most recent activities.

I put some thought into this the other night and I think the way I’d like to implement this is as a static HTML website - there’s nothing I do so rapidly that people need a second-by-second update of it.

Hugo is my static site generator of choice - it’s powerful enough to do everything I’ve wanted to do with it, without relying on your final site having Javascript (or being very particular about avoiding it.)

I want to do things properly this time though - and by properly, I mean in such a way that what I’m making can be useful for other people who’d like to make a site like mine, but with their own information.

As I understand it, this means organizing the components as Hugo themes. Hugo uses what it calls layouts to determine how to render a document, and follows a lookup order to determine which layout to use.

So, I think I’ll start by making a new project, hugo-personal-website-theme, that’ll be a Hugo theme, and used by the emsenn-website project, that’ll be a Hugo website.

That’s about all I can write on the topic until I take the first steps toward implementation.

Editorial and License Information

My name is emsenn and I wrote this essay for the benefit of the commons. To the extent possible under law, I have waived all copyright and related or neighboring rights to it. If you're viewing it on a remote server, you're encouraged to download your own copy. Essays like this are made possible with financial support from readers like you. Thank you. To read more of my work and to learn more about me, visit https://emsenn.net