64 lines
3.9 KiB
HTML
64 lines
3.9 KiB
HTML
<!-- Hi to anyone who decided to inspect the source code for my site today! -->
|
||
<!DOCTYPE html>
|
||
<html lang='en'>
|
||
<head>
|
||
<title>gome — update</title>
|
||
<meta charset='utf-8'/>
|
||
<meta name='theme-color' content='#efe5d7'>
|
||
<meta name='viewport' content='width=device-width, initial-scale=1.0, shrink-to-fit=no'/>
|
||
<link rel='icon' type='image/x-icon' href='../favicon.ico'>
|
||
<link rel='preconnect' href='https://fonts.googleapis.com'>
|
||
<link rel='preconnect' href='https://fonts.gstatic.com' crossorigin>
|
||
<link href='https://fonts.googleapis.com/css2?family=Lora:ital@0;1&display=swap' rel='stylesheet'>
|
||
<link rel='stylesheet' type='text/css' href='../css/style.css'/>
|
||
</head>
|
||
<body>
|
||
<header id='header'>
|
||
<nav>
|
||
<a href='..'>back to gomepage</a>—<a href='.'>journal</a>
|
||
</nav>
|
||
</header>
|
||
<main>
|
||
<article>
|
||
<h1 id='title'>How I update my site</h1>
|
||
<time datetime='Thu, 23 Feb 2023 21:00:00 CST'>23 Feb 2023, 9:00 PM</time>
|
||
<p>
|
||
Most people who blog use some sort of tool that stands between them and the HTML your computer fetches from the server.
|
||
Even if it’s not a fully-fledged content management system, they will at least use a static site generator to save a lot of repetition.
|
||
That’s not the case here on gomesite.
|
||
</p><p>
|
||
Every HTML file you view here has been hand-edited by me.
|
||
That’s right: organic, cage-free, free-range HTML.
|
||
I usually write my posts on my main machine, adding them to the journal index, the RSS feed, and the front page.
|
||
Once the changes are ready, I push them to the <a href='https://tildegit.org/gome/gomesite'>git repository for gomesite</a> kindly hosted by <a href='https://tildegit.org/'>tildegit</a>.
|
||
Then, I SSH into the Ctrl-C server and pull the updates into the copy of the repo in my <code>public_html</code> folder.
|
||
</p>
|
||
<figure>
|
||
<img src='img/upload_screenshot.webp' width='563' height='369' />
|
||
<figcaption>My POV updating the site every day</figcaption>
|
||
</figure>
|
||
<p>
|
||
Why do I do things this way?
|
||
Isn’t this the <a href='https://en.wikipedia.org/wiki/Don%27t_repeat_yourself'>wettest</a> way to write a website?
|
||
Well, sure, there’s a lot of boilerplate with the journal now, but when I started building gomepage, the site was so simple there was really nothing that needed generation.
|
||
</p><p>
|
||
When I started the writing challenge, I considered setting up a static site generation solution for the journal, since I foresaw the repetition in doing it manually.
|
||
But when I think about how long it <i>actually</i> takes to set up an SSG, I was not at all sure it would be worth it, even after 100 repetitions.
|
||
In the spirit of <a href='https://xkcd.com/1205/'>xkcd</a>, if I were to save myself five minutes 100 times with an SSG, then it would only be worth it if I spent less than 8 hours and 20 minutes on it.
|
||
</p><p>
|
||
Time optimization aside, I just don’t really <i>want</i> to automate my site.
|
||
The only SSG I’ve ever used is <a href='https://jekyllrb.com/'>Jekyll</a> and while I liked it enough, what I don’t like is the Ruby dependency, because literally nothing else I use is in the Ruby ecosystem.
|
||
Learning a new system doesn’t sound like much fun right now, either.
|
||
Even with how error-prone the process is, the repetition is actually kind of nice.
|
||
It keeps me mindful of how my whole site fits together, which I appreciate.
|
||
</p><p>
|
||
Do you have a site or page you update regularly?
|
||
What do you use to update it?
|
||
Do you have something you actually like doing repetitively, rather than automating it?
|
||
Let me know your thoughts at my Ctrl-C email: <code>gome<span style='user-select: none;'> ​</span>@<span style='user-select: none;'> ​</span>ctrl-c.club</code>.
|
||
</p>
|
||
</article>
|
||
</main>
|
||
</body>
|
||
</html>
|