Right, We've Got a Blog Now
Because every project eventually succumbs to the gravitational pull of a blog section. Here we are.
Why a Blog?
Every open-source project reaches that inevitable moment where documentation alone doesn't cut it. You need a place for the messy bits — the "here's why we did this questionable thing" posts, the release notes nobody reads, and the occasional tutorial that might actually help someone.
So here it is. A blog. Groundbreaking stuff.
What to Expect
Release notes — because changelogs are for robots, and sometimes you want the human version of "we fixed that thing that was driving everyone mental."
Tutorials — step-by-step guides for people who'd rather not reverse-engineer our code to figure out how things work. Fair enough.
Ecosystem commentary — thoughts on FluentCart, FluentCommunity, WordPress, and the general state of building things on the internet in 2026. Spoiler: it's still chaos.
The Rules
- No corporate waffle. If a post starts with "We're excited to announce," it gets binned.
- British sarcasm is not optional — it's structural.
- Every post must contain at least one mildly self-deprecating remark about the codebase.
Welcome aboard. Lower your expectations accordingly.