#dev 2026-06-20
2026-06-20 UTC
cotsuka, ax562, grufwub, k3can, turalyon, chr0m4, Maxpm, vriska, duanin2, oodani and mahboubine joined the channel
#
WinnerWind I'm starting to document my static site generator and I was curious how everyone else documents their static site generator. Just opened an Obsidian Vault to write down all the methods but a part of me thinks that this could get tedious fast
#
[capjamesg] I used my static site generator to build the docs for my generator 😄
#
[capjamesg] You can see them here: https://jamesg.blog/aurora
#
[capjamesg] With that said all those docs are for the old version I don’t really support any more.
#
WinnerWind [capjamesg]: holy, that's smart. dogfooding makes sense :)
#
WinnerWind the nice thing about my ssg is that it does support some OFM so i could author it in obsidian then use the SSG to make it into a site
Pixi` and Kolev joined the channel
#
WinnerWind oh boy i regret not wriitng documentation before. this is boring
#
WinnerWind In a way I wish i could automate this very boring process
#
WinnerWind not using AI or anything. I mean as in something that could read my file and automatically make documentation based on the comments. Godot does this already and I love it so much for it, but I can't find any good solutions for Python. Everyone seems to be writing xml
#
[capjamesg] There are ways to programmatically read docstrings in Python but the only ones I have used are extensions to existing SSGs like Sphinx’s autodoc.
#
WinnerWind i hate that i had to look up what a docstring was
#
WinnerWind welp im going to try a few of them
#
[capjamesg] We’re all always learning!
#
WinnerWind OK wow, all of these documentation solutions are a hot mess. none of them output to markdown. all of them decide that i want HTML and the ones that do allow markdown support are absolutely borked. I guess taht means its time to make my own (how many times have I done that now?)
#
WinnerWind im kind of doing that. im writing a secondary script that spits out markdown and then sends it to the documentation folder. then my static site generator will read the markdown files and make the docs
#
WinnerWind because of the nature of my SSG i could just feed it the project directory itself then through a series of plugins make it into a static site but that sounds like hell
#
WinnerWind the joke of python typecasting a string into a toyota yaris 2004 cannot be more true in my SSG. it is more than willing to turn a text file into an image provided the plugin asks for it
ZodiacalComet joined the channel
#
ZodiacalComet Feel the inspection of function signatures and its attributes
#
ZodiacalComet And first time I hear of that joke, crazy xd
#
WinnerWind ZodiacalComet: not the place for memes but its from [this post](https://www.reddit.com/r/ProgrammerHumor/comments/1hx77fw/justuseatryblock/) got pretty popular while it lasted and its become a bit of an inside joke in computer science class
cotsuka joined the channel
#
WinnerWind today's the first time ive ragequitted while coding. time to relax by making some low stakes HTML and CSS
#
WinnerWind I'm just going to go back to using premade doc solutions and deal with the fact that they're HTML based
cotsuka, mossymaker, proofreed and JadedBlueEyes1 joined the channel
#
chr0m4 this is the way, using Claude at work is more mentally draining than coding myself, I sometimes enjoy a lot just typing some good ol html and css for my website
[snarfed] joined the channel
CRISPR joined the channel
#
WinnerWind [snarfed]: these are helpful, but what you do is slightly different. thanks though!
cotsuka, CRISPR, ttybitnik, luca, Xe, hisacro, rrix, rrix_, WinnerWi-, ax562 and rozodru joined the channel
