Blog
Insights, tutorials, and updates from the Fanpino team.

The Search Console Warning That Wasn't About Our Site
79 URLs in a Search Console bucket we'd written off as harmless turned out to be an old subdomain with an expired certificate. The fix was deleting one DNS record.

A Bug Report That Didn't Quite Reproduce, and Why We Fixed It Anyway
A researcher reported a stored-XSS path through PDF attachments in FanDesk tickets. The exact path likely didn't reproduce as described; we hardened the code anyway.

A Quarter of Our "Direct" Traffic Was a Bot, and Analytics Never Said So
Our Direct channel's engagement rate looked mediocre for weeks. The real number was 12 points higher, once we found and excluded the traffic that was never a visitor.

Why We Send Container Logs to stdout, Not Files
A routine nginx rebuild wiped evidence we didn't know we needed. The fix was two lines, but finding out we needed it took longer than it should have.

No Manual Re-Entry: Why SteelFlow Pulls the BOM Straight From the Tekla Model
Every manual re-entry of a Tekla model's part list into a spreadsheet BOM is a chance for drift. SteelFlow's Tekla plugin makes the BOM a mechanical consequence of the model, not a separate task.

Linked by Default: Why SteelFlow Ties WPS-WPQ, NDT, and NCR/CAPA to Every Part
Welder qualification, procedure approval, and inspection results usually sit in three disconnected records. SteelFlow keeps them linked to every part from the start, so an audit or a failure doesn't require manual reconstruction.

Bilingual Standards, Not Informal Translation: Why Probe361 Maintains Persian Content Clause-by-Clause
An informal WhatsApp translation of a welding standard drifts from reality every time a revision ships. Probe361 maintains clause-by-clause Persian translations mapped to the exact original clause.

Why a Personally-Paid Reference Tool Has to Earn Its Renewal, Every Time
Enterprise software gets adopted top-down. A tool an inspector subscribes to personally has to earn its renewal on a job site with no signal, which is why offline favorites matter more than any feature list.

Multi-Location Repair Shops: Why Data Isolation Matters Before You Need It
A spreadsheet survives one repair shop location. The second branch is where per-shop data isolation, role-based access, and audit logs stop being nice-to-have and start preventing real disputes.

A Repair Quote in Seconds, Not a Guess: AI-Assisted Diagnostics in Mobile Master
A counter quote is usually a tech's memory of similar repairs, accurate often enough to matter when it's wrong. Mobile Master grounds AI-suggested quotes in the shop's own repair history, not an industry average.

FanProfile: Why a Faculty Directory Gets Its Own App, Not a CMS Page Type
A public faculty directory has a different audience, traffic shape, and permission model than a CMS admin panel. FanProfile is its own REST API for exactly that reason.

Why FanCover Runs as Its Own Isolated Service, Not a CMS Module
Staff insurance data shouldn't share a trust boundary with a public website's CMS. FanCover runs as its own service with a dedicated database and national-identity login instead of a password.
Last updated: