August 24th, 2024

Making a blog for the next 10 years

The author plans to maintain their blog for a decade, using Markdown for readability, Mataroa for hosting, and Go for publishing tools, while addressing third-party module reliability concerns.

Read original articleLink Icon
Making a blog for the next 10 years

The author reflects on their commitment to maintaining a blog over the next decade, emphasizing the importance of using GitHub as a mirror and implementing automation for upkeep. The blog's content is written in Markdown, which ensures readability even without specific formatting tools. The author utilizes a hosting platform called Mataroa, which allows for easy export to other platforms, reducing the risk of platform lock-in. They have also secured a proper domain, kokada.dev, to facilitate potential future migrations. The author employs various tools, including shell scripts and Makefiles, to streamline the publishing process, while ensuring compatibility across different systems. The blog's publishing tools are primarily written in Go, a language known for its backward compatibility, which the author believes will ensure long-term viability. However, they express concerns about the reliability of third-party Go modules, opting to use the "go mod vendor" feature to include copies of necessary modules within their repository. The author acknowledges potential issues such as broken links and the need for permalinks, considering future solutions to maintain the blog's integrity.

- The author is committed to maintaining their blog for the next ten years.

- Markdown is used for content creation, ensuring long-term readability.

- The hosting platform Mataroa allows for easy content export and reduces platform lock-in risks.

- The author uses Go for publishing tools, valuing its backward compatibility.

- Concerns about third-party module reliability led to the use of "go mod vendor" for local copies.

Link Icon 2 comments
By @manuelmoreale - 3 months
I’m not entirely sure how and why this should be hard. I have a blog that runs on a file based CMS. It doesn’t need constant updates and will run just fine on its current set up for as long as the VPS is up. There are sites I made at the beginning of my freelance career that are still out there, still doing fine and are more than 10 years old.

The only reason why a site is not going to last is if you build it on a convoluted tower of tools that depend on other tools that depend on 3rd party services and so on.

Want your site to last? Pick a stack that’s as simple as possible. Want to make it last “forever”? Build it with just html + css.

By @SenHeng - 3 months
Note to author: some links to capivaras.dev in https://kokada.dev/blog/quick-bits-why-you-should-automate-e... points to capivavas.dev.