Colophon

Table of Contents: Key Principles / Technologies & Techniques / Writing and Editing / Credits / Site History

Or, how this site was made.

Key Principles

This website was created, handcoded, and tested for accessibility by yours truly. This is a personal, text-first, static, website that uses minimal JavaScript, images, and styling. As an advocate of the IndieWeb movement, this website is free of tracking services and corporate marketing. The webmaster is the sole owner of the website and its content. They are committed to the accessibility of this website, taking great care to adhere to it principles and improve the accessibility of new content and versions of this site.

Technologies & Techniques

This site was drafted in Obsidian, turned into HTML/CSS, in VSCode, tested for accessibility on Chrome and Firefox Desktop, and on Ecosia for mobile, and hosted in Neocities, all using a refurbished HP Elitebook.

I use git to track changes—both in Obsidian and VSCode—and upload it to a private Github repo. For web development, I apply the git-flow workflow system. Keeping it short, I have three active branches, main (branch that gets sent to Neocities), develop (for quick changes and base branch for final branch type), and feature-NAME (can be one or multiple). The last focuses on testing specific additions to the website like content, layouts, or color schemes.

To transfer the content from Obsidian to HTML, I literally copy-paste the content from the Github. This is why I have found it useful to apply git-flow. feature-NAME has been a lifesaver because I can see all the edits and/or new content I need to add in one place. I use handcoded templates in HTML and Markdown to speed up the setup process to create new pages, make more templates as needed.

Writing and Editing

Most of the content is written in Obsidian. All pages start as Markdown files. This helps me focus on just getting the words down as I can get lost in the fine details in web development. I must note however that minimal HTML can show up depending on the creative process, usually bits of code that will be sent to VSCode to be usable.

Folder structure is also tested in Obsidian as I've found it's a real pain to fix broken links on the HTML stage. Editing might occur in VSCode if I notice grammatical errors or something else I feel like adding.

Site History

It's tentative launch date is 2025 Pride Month. The vision for this site is a hub for all my past and future original and fandom related-writing.

Credits