I built an internal knowledge base plugin for #WordPress. Check it out at: https://t.co/fO0okseS6G
It's made for teams operating in WordPress that want a better handle on their organizational knowledge.
Let me know what you think. π
I'm still thinking about this article that Danny shared yesterday.
I rarely have my head in the clouds when it comes to AI. I consider myself aware. Something about this article is weighing heavy on me, though. I'm not sure what.
@SeanChDavis Right? If he just left it at this post (which I think is quite good), I could sympathize. But this path of active resistance and hindering how other people work, meh.
https://t.co/MprJH5E7sd
@DerekAshauer Nice! I wish I had done the same. I was just a user turned DIYer for my own early side projects. This was long before I ever knew I'd earn a living from it!
@PineDigitalCo Sorry, re-reading your post and it sounds like you want to keep the actual docs site separate? I originally thought you were talking about changing course and bring the docs in fully. Either way, I've seen both happen. π
@PineDigitalCo Totally possible. That's sort of Keystone is. https://t.co/fO0okseS6G
You'd basically just need to create a custom view in admin for the doc entries, which would most likely be custom post types.
It basically felt like building a theme inside of WP admin.
@dannyvankooten Good read! I'm not mad at that article/position at all. I respect it.
Jumping from that position to literally prompting AI through users' workflows was indeed a wild and ironic decision. It makes me think he was trying to make a specific point, welcoming the smoke.
@rmelogli I've been in partnerships where someone else handles the marketing, which I am cool with. That's basically how it has to be for me, because I will not put much effort into selling something.
I know some folks are still on the fence about using AI to write code. As a developer, I've yet to feel like I've handed over my responsibility to solve problems, which was the point of writing the code.
I don't know. Meticulous prompting feels quite the same.
@DaronSpence I hear you! I've definitely seen it play out that way. It makes documented knowledge transfer a short-term solution at best.
Thanks for the input!
@DaronSpence So you're saying there's never really a clean "here's everything you need to know" moment, but instead an ongoing knowledge transfer (aka support)?
Launching https://t.co/36UBUXMmiq.
A platform-agnostic spec of what a good website does: SEO, accessibility, security, agent-readiness, performance, privacy, i18n.
Every claim cites a source. Ships with a checklist, llms.txt, MCP server, and Agent Skill.
Free. Open Source.
@PineDigitalCo Got it. That's actually how I've always done it as well.
We almost always had living documents (throughout development) that could eventually serve as reference documentation. Then I would make myself available in some way after the transfer.
Thanks for the input!