Is This Site AI? - AI Usage Statement

Usage of generative AI to vibe-code websites has increased a ton recently, and it's become a LOT harder to verify the origin and the authenticity of content. I believe it is important to be completely upfront to the visitor about what AI generated/assisted content it contains.

The following states how generative AI on sirkorgo.com is used:

AI Usage Statement

Last updated: August 5th, 2026

TL;DR

Published content and assets on this site do NOT use generative AI in any step of the creative process. External tools or images may occasionally include AI elements beyond my control. Code on this site is written by hand, with occasional use of help from an LLM (in moderation) to troubleshoot JavaScript and CSS issues.

If you formed a negative opinion of me or my site from this summary, I encourage you to read the detailed statement to hopefully justify whatever dissatisfies you.

In addition, I am very open to feedback to help improve the transparency of this statement. If you have any comments or concerns, you can find ways to contact me via the About page.

My Stance On Generative AI

I am heavily against the use of generative AI to fully generate "art" or code without any human input other than prompting a model. However, I believe that AI is good when used meaningfully. For example, using it to better understand concepts, or getting suggestions to help improve a work.
This stance is heavily applied to my work on sirkorgo.com and other projects/works.

Regarding content and creative assets posted on this site

Content posted on this site includes, but isn't limited to the following:

  • Blog posts, which can be found at /blog
  • Comic series & chapters, which can be found at /comics
  • Artworks, which can be found at /portfolio
  • Changelogs, which can be found at /index , on the "What's New" list
  • Assets created by me (banners, bumpers, icons, emblems)

The content and assets created by me listed above does NOT use generative AI for ANY step of the creation process, and while being served on sirkorgo.com.

Regarding code written to serve this site and tools

This site is built with Jekyll , hosted on GitHub ( sirkorgo/korgoweb ), and deployed via Vercel. I am unsure of how AI is used by the vendors I listed above, but the repository itself is open source if you'd like to inspect the code.

As for the code itself, I write it for this site myself. However, on occasion I may use an LLM to troubleshoot CSS or JavaScript bugs that I was unable to fix myself. The fixes are NEVER automated using agentic AI, and code that the AI outputs is always reviewed, understood, and applied by me.

External tools created by me for use on sirkorgo.com (Korgosketch, Korgostats) were mainly written on my own, with an LLM to help me optimize the code and help write code for functions that required skills outside of my skillset. Code output from LLMs were reviewed, understood, and applied by me, and no automation (such as agentic AI) was used to write first-party external tools used on sirkorgo.com.

The source code for the following first-party tools used on sirkorgo.com are available on GitHub, open for inspection:

Regarding third-party assets, images, and tools

  • Blog posts may occasionally feature third-party images that utilize AI, though this is never intentional.
  • Assets from other sites (buttons, webrings): I am unsure about the AI usage for the creation and moderation of webrings, along with the creation process of site buttons that may be served on my site. Webrings that I participate in, and buttons that are served on sirkorgo.com may be AI generated, as I may be unaware of the third-party's AI usage, and it is beyond my control
  • External tools from third-parties (WidgetStar, Atabook, CursorParty): I am unsure about third-parties' usage of generative AI to create and maintain external tools; those tools on sirkorgo.com may utilize AI, as I may be unaware of the third-party's AI usage, and it is beyond my control. The source code of CursorParty, a tool I use on my site, is open source on Github ( partykit/cursor-party ), free to be inspected.