markdown file

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-08-28

Final complete day: 2026-08-28. Attention was 0.2% — this entity appeared in 5 of 2,594 analyzed posts/comments in the seven days ending that day (5 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-08-27 12:48 UTCComment

   That makes total sense - WordPress would fight you on template consistency every time. Given what you've said (keep your exact templates, but give a non-technical person a Facebook-simple posting UI), the pattern a few others here are converging on is probably your best bet: a static site generator (11ty, Astro, or Hugo) paired with a git-based headless CMS like Decap or PagesCMS. Your templates stay exactly as they are since the SSG just renders your existing markup, and the CMS gives your contributor a simple form that commits a Markdown file behind the scenes - no database, no admin panel bloat. Only real tradeoff is a short rebuild/redeploy delay after each post (seconds to a couple minutes depending on host), which is usually a non-issue unless they need instant publishing.

2. 2026-08-26 03:09 UTCComment

   "Yea, but do you think Claude is right?" This sometimes slows people down. "Well, sure." "Ok... why?" If they continue to just kind of gesture vaguely at the shoggoth this is a good time to remind them what we're paid to do. "Look, I get it; Claude is a great resource and I use the hell out of it too... but if we follow Claude's advice and Production falls over, catches on fire, and wipes out our Q3 profits they're not gonna blame Claude. So what do *you* think?" There is a fine line between trusting Claude to take care of the implementation details (I legitimately don't know the name of the bucket that's holding Terraform state; Claude created it because we all know you need a bucket to hold TF state and I don't care what it's called until I do... and then I'll ask Claude) and trusting Claude blindly on a judgement call where there's real risk or context on the line. That said, I think we may be reaching the end of the usefulness of knowledge sharing. If this dude is just deferring to Claude on a KT task it means he doesn't actually have the context you need; Claude does. Just ask him to have Claude spit out a markdown file containing the full context necessary to read another agent in on the task up to this point and go on about your day. One thing LLMs are *really* good at is extracting answers from a context lake.

3. 2026-08-25 09:50 UTCComment

   Echoing some other advice here, I use PagesCMS with Markdown files and Astro as my framework. It's perfect for blogs and gives you a UI for free for client to add their own content.

4. 2026-08-24 22:26 UTCComment

   I had a customer with similar needs, they wanted no database, so we used the markdown files approach, but added PagesCMS and github to give their blog contributors a way to easily add and manage content without being able to edit other pages, the downside is that the page has to re-deploy via github actions on each modification, but given is only a handful of contributors, always in sync, this has not been an issue.

5. 2026-08-24 22:25 UTCComment

   Totally depends on the current stack of the website. If you’re dealing with static HTML, then tools like Eleventy or Hugo can run your blog posts as markdown files, super straightforward. But if it’s a JavaScript framework kind of thing, then Astro usually handles this really well, and with minimal setup too.