Editorial policy
How we source, write, review and correct what we publish on Learn, the blog, the glossary, service pages and build notes.
What we publish
SupaMakers publishes implementation notes, technical explainers, interactive courses, assessments, and product documentation about applied AI. Our goal is to help operators and technical teams make better decisions about real workflows, not to fill a publishing calendar.
Experience and evidence
We distinguish between systems we have built, working demonstrations we operate, informed implementation guidance, and claims reported by third parties. Product behaviour should be verifiable through the linked tool, application, source repository, or build note. We do not invent client names, testimonials, outcome metrics, or credentials.
Sources
Claims about laws, regulations, standards, research, vendors, and market conditions should link to the most direct available source. Primary legislation, regulator publications, official documentation, and original research are preferred. A source supports the claim at the time of publication; readers should check the current source before relying on fast-changing information.
Professional and regulated topics
Material about legal, financial, healthcare, privacy, safety, compliance, or regulatory topics is educational information, not professional advice. It should not replace advice from a qualified professional who understands the reader's facts, jurisdiction, and obligations.
Updates and corrections
We review content when a material source, product, standard, or workflow changes. Significant editorial updates should receive an accurate updated date. Styling or deployment changes must not be presented as content updates. If you identify an error, send the URL, disputed passage, and supporting source to shilpa@supamakers.com.
For company ownership and contact details, see the About page. For personal-data handling, see the Privacy Policy.