known as @hacdias
A few months ago, I released an article where I showed most versions of my website before I started integrating IndieWeb into it. I think it is nice to have an overview of how your website evolved with time. So today I present to you all the major changes to my website after IndieWeb.
Since I created this website’s colophon (also known as meta page), I’ve wanted to also created a page that show cased how this website evolved over the years. I created this website when I was 14, in 2014. At first, it was just a bunch of HTML pages written by hand. Within the first year, the website moved from pure HTML to WordPress and then to Hugo.
In 2015, I posted an article with a very similar name to this one. At the time, I was saying goodbye to WordPress and welcoming Hugo. As with everything in life, there are cycles and things change. It’s time to turn a new page on this website’s life cycle.
Today I have been thinking about my website. Mainly about ditching Hugo and moving to a completely custom and dynamic website. There are a few reasons about why I would like more flexibility. However, I don’t know if it justifies the effort.
Hello 👋 Today’s newsletter is a bit different (and smaller) than most. I have been quite busy during the past week and this week as well. Starting tomorrow, I’m having three three hour exams this week that count 100% towards my final grade. I don’t even know if this should be allowed.
My website is growing, not in terms of views, because I’m not aware of that. Maybe I should add some non-intrusive analytics. Anyways, it’s growing in terms of functionality. However, since I’m using a static website generator, it makes it complicated to add some interactive functionalities.
Today’s the first day of a new month, so here’s a new “recently” post. Since I decided to start this series after mid-september, there’s not that many news since. However, I’m more than happy to write a few words about what’s been happening lately.
I decided to make a few updates on my website - again. However, this are a bit more than visuals and I’m mostly reinventing the way I manage IndieWeb posts, namely likes, reposts, notes and replies.
For quite a few time, I used Bear as my go-to Notes application for two reasons: it was simple to use and the syntax was quite similar to markdown. However, it is not markdown and it does not support some things that’d like to see on such software: diagrams, mathematics, wiki-like links, etc.
For quite some time, I have been getting more and more into the IndieWeb world and trying to own my own data. I have started publishing more to my website and using it as a place to store most of my public data, i.e., data I already published on other social media and platforms.
As Tom once said, it is now time to own my own reading log. Why? Despite all the reasons mentioned on Tom’s post, I also got bored of Goodreads and I ended up not using it as much as I should have.
After digressing a bit about building a Micropub endpoint for my website, I’ve been thinking about the next steps: if I should keep Hugo or move to some other system.
Recently, I have talked about restructuring the URLs of my website and adding IndieAuth so I could use my domain as my main online identity to login into services. Along those lines, I came across Micropub. In their own words:
This is going to be a quick post — I hope.
After updating the structure of the URLs on my website, I felt like the next step would be to implement IndieAuth because almost everything on the IndieWeb needs that.
I’m now working on making my website more IndieWeb friendly, which was triggered by my searches after writing my last post about owning our own data. It has been… harder than I though. But in a positive way!
