How this publication is run.
StorageFlo.io publishes articles for self-storage operators, owners, marketers, and the engineers who build alongside them. This page names who publishes the site, how each desk is run, who reviews every piece, and how to reach us if you find something wrong.
StorageFlo.io is published by South Star Holdings LLC.
StorageFlo.io is the publication name. The legal entity that operates the site is South Star Holdings LLC, a Delaware limited liability company. Governing law and venue for any dispute with the publisher are described in the Terms of Service.
The publisher is the accountable party for everything published under the StorageFlo.io masthead, including the articles section.
Every article is reviewed and edited by the StorageFlo.io editorial team.
Articles are bylined to a desk, not an individual. Every draft is reviewed by the StorageFlo.io editorial team before it ships. The team is accountable for fact-checking, source verification, and the published voice of each desk.
Articles list the editorial team as the editor in their structured data. We may add named contributors in the future for guest pieces; if that happens, the article will carry a clear named byline and this page will be updated.
Seven editorial desks. Each one is a voice convention, not a person.
Every article is published under one of the desks below. Desks are editorial voice conventions and accountability surfaces. They are not biographies; the desk is the masthead, not a pseudonym for an individual.
- EDStorageFlo.io Editorial
Main company voice. Product updates, opinion pieces, and announcements from the StorageFlo.io team.
- ADStorageFlo.io Analytics Desk
Traffic, GA4, conversion, renter behaviour, and what the data actually says about self-storage demand.
- MDStorageFlo.io Marketing Desk
Local SEO, Google Business Profile, paid acquisition, referral programs, and website conversion for storage operators.
- ODStorageFlo.io Operator Desk
Day-to-day facility operations. Rate raises, auctions, signage, hiring, move-ins, and what the front desk actually sees.
- INStorageFlo.io Integration Desk
SiteLink, storEDGE, Easy Storage Solutions, payments, webhooks, and the technical seams between the systems operators already run.
- IDStorageFlo.io Industry Desk
Acquisitions, REIT filings, regulation, association news, and market shifts that affect the operators reading the rest of the blog.
- JCFounder Notes
Building StorageFlo.io in public. Product decisions, lessons from the operator side, and plain-spoken updates from the founder.
Every article passes through a written checklist before publishing.
A draft moves from _drafts/ to published content only after the editorial team signs off on each of these:
- The article has a clear accountable publisher and a documented review trail.
- No invented credentials, customer stories, locations, or experience.
- The article helps a real storage operator, owner, marketer, or developer. It adds something a reader could not get by searching the source links directly.
- All factual claims that need support have source links. Industry-data articles carry at least three credible sources.
- Live product features are described as live; roadmap features are described as roadmap. StorageFlo.io is never described as a bank, payment processor, legal adviser, or full facility-management system.
- Build and typecheck pass; the page renders cleanly on desktop and mobile; the RSS and Atom feeds remain valid after publish.
Every claim that needs a citation gets one.
The sources block at the bottom of an article is the citation list, not decoration. If a number, quote, or product behaviour appears in the body and a careful reader would want to verify it, the source link is below. External quotations stay within fair-use length and attribute the speaker by name.
Industry data we re-publish (REIT 10-Q tables, SSA association numbers, GSC trend snippets) honors the source's attribution or terms-of-use line and credits the source inline, not just in the trailing sources block.
Competitor product names and trademarks (SiteLink, storEDGE, Yardi Breeze, Hummingbird, Public Storage, CubeSmart, Extra Space, and others) are spelled exactly as the owner spells them and are not styled as if they were StorageFlo.io properties.
Articles carry both a publish date and an updated date.
Every article surfaces a publishedAt and an updatedAt date in the byline. The two dates differ when an article has been revised after publication.
Material corrections, a wrong figure, a misattributed quote, a product description that no longer matches what ships, are surfaced in a short editor's note at the top of the article body, dated, with what changed and why. Silent re-saves are reserved for typo fixes, punctuation, and broken-link repair where the meaning of the article does not change.
If you spot something wrong, write to [email protected] with the article URL and what you believe to be wrong. We respond to corrections requests within five business days.
The editorial team uses every tool that helps the article without compromising the byline.
Drafting tools, including large language models, are used internally to research topics, structure outlines, draft prose, and check style consistency. Every published article is reviewed and edited by the StorageFlo.io editorial team before it ships, and the team is accountable for the published content. Tools that produced drafts are not credited in the byline because they are not the accountable party.
One inbox for editorial concerns and proposals.
For corrections, source disputes, guest-contribution proposals, or any editorial concern: [email protected]. For general support questions about the StorageFlo.io product, use the support page instead. That inbox is faster for product issues.
Give tenants the flow your team wishes they had.
Bring websites, maps, contracts, payments, communications, and integrations into one booking path that works for small facilities and growing portfolios.