From 16e48ed8655528a81cbec84f0cbc1a211d663b37 Mon Sep 17 00:00:00 2001
From: Hannah Isopod <me@bathynomus.xyz>
Date: Sun, 9 Nov 2025 08:58:02 -0700
Subject: Probably final commit before the redesign Routine updates to various
 pages Accessibility fix in /guestbook Updated /uses im pretty sure
 Reorganized /blog/ a little under the hood

---
 blog/posts/blog_questions/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'blog/posts/blog_questions/index.md')

diff --git a/blog/posts/blog_questions/index.md b/blog/posts/blog_questions/index.md
index 4f6ac6b..af44d9f 100644
--- a/blog/posts/blog_questions/index.md
+++ b/blog/posts/blog_questions/index.md
@@ -17,7 +17,7 @@ The backend for my blog is built around its RSS feed, which is to say, the autho
 The posts themselves are stored as Markdown files with a smattering of HTML mixed in for the really custom stuff, and there's a second PHP file that renders them using a third-party PHP Markdown parser called [Parsedown](https://github.com/erusev/parsedown) (which, fun fact, is also responsible for the Markdown support in the comment section). The only unfortunate thing here is every markdown file has to be accompanied by a stub index.php that just `include`s the main post rendering script, but it's not like I ever have to touch those so it's fine. Here, I'll put all the code that's in every single one right here:
 
 ```
-<?php include("../post.php");
+<?php include($_SERVER['DOCUMENT_ROOT'] . '/blog/post.php');
 ```
 
 The comment section is fully custom too, and shares a backend with the [guestbook](/guestbook/). At its core it's all just PHP forms with a single JSON file as the database, which is more than fine at the scale I'm operating at. Everything else is just gravy, although there is at this point quite a preponderance of gravy.
-- 
cgit v1.2.3