396840
results for ""a""
-
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
at
2026-06-20 14:52
-
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
at
2026-06-20 14:51
-
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
at
2026-06-20 14:46
-
welp im going to try a few of them
WinnerWind
at
2026-06-20 14:38
-
i hate that i had to look up what a docstring was
WinnerWind
at
2026-06-20 14:35
-
In a way I wish i could automate this very boring process
WinnerWind
at
2026-06-20 14:30
-
thamara_k[d]: Love the coziness! Reminds me of a good book! Site's coming up great, thamara_k[d].
kenomatik
at
2026-06-20 14:00
-
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
WinnerWind
at
2026-06-20 13:31
-
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
WinnerWind
at
2026-06-20 13:28
-
That sounds like a good question for #indieweb-random. This channel is specifically for talking about personal websites 🙂
[capjamesg]
at
2026-06-20 10:24
Sort by:
Filter results by:
Tag
Query took 0.02s.
Search tips
- Exclusion
- +foo -bar
- Logical OR
- foo OR bar
- Exact phrase
- "foo bar"
- Partial words
- foo*
- Particular fields only
- title:foo
- domain:example.org
- nick:somebody
- after:2016-11-23
- before:2016-11-23
- date:2016-11-23