JamForce Editorial Policy

Published 24/07/2026

JamForce exists to make Salesforce easier to understand without hiding the details that matter in a real org. This policy explains who creates the content, how claims are checked, where tools such as AI fit, and what happens when something needs correcting.

Who Writes and Owns the Content

JamForce is written and edited by James Winter, a New Zealand-based Salesforce Platform Architect with experience across administration, development, integration, and platform design.

James chooses the topics, reviews the sources, edits the final wording, and takes responsibility for what is published. External tools can support that work, but they do not become the author or make the final editorial decision.

How Topics Are Selected

Topics are chosen because they answer a practical question for someone learning or working with Salesforce. That may be a beginner concept that deserves a clearer explanation, a design decision with important trade-offs, or a platform change that affects existing guidance.

The aim is not to publish for volume. A useful article should help the reader understand why something matters, how it works, what can go wrong, and what to check before using it in their own org.

Sources and Factual Review

Official Salesforce documentation is the starting point for claims about platform behaviour. Depending on the topic, that may include Salesforce Help, the Developer Documentation, release notes, Trailhead, product pages, or published limits and security guidance.

Release status, product names, licensing, editions, limits, retirement dates, and security behaviour are treated as time-sensitive. Where those details affect a recommendation, the relevant article should link to a primary source close to the claim.

Official documentation still needs interpretation. JamForce distinguishes between:

• Documented behaviour: what Salesforce currently states the platform supports or requires.
• Implementation guidance: a recommendation based on the documented behaviour, technical judgement, and the needs of a particular org.
• Opinion: a clearly framed view about design, maintainability, learning, or operating practice.

First-Hand Experience and Researched Guidance

First-hand observations are based on work James has genuinely performed or situations he has directly encountered. They are presented as experience, not as a universal result.

Researched guidance is not rewritten to sound like a client story or personal experiment. If an article uses an illustrative scenario, it should be clear that the scenario is there to explain the concept rather than prove a real project outcome.

Code Examples and Testing

Code, queries, and configuration examples are reviewed for their teaching purpose and checked against relevant Salesforce syntax and documentation. Where a release-sensitive behaviour or important limit has been tested in a suitable Salesforce environment, the article should say what was verified.

Not every snippet is a complete, standalone deployment project. Some examples deliberately omit surrounding classes, data, error handling, or org-specific configuration so the main idea remains visible. Treat every example as a starting point: adapt it to your data model, security model, API version, and operating constraints, then validate it in a sandbox, scratch org, or Developer Edition org before production use.

JamForce does not claim that every code example has been compiled as one programme-wide test suite. High-value examples are being reviewed progressively, and articles should not imply a stronger level of testing than was actually performed.

AI Assistance and Human Responsibility

AI may assist with brainstorming, organising research, drafting, editing, summarising source material, or checking consistency across the site. Automated tools also help find broken links, invalid metadata, accessibility problems, and other repeatable issues.

AI output is not treated as a source of truth. Platform claims still need an appropriate source or practical verification, and generated wording is reviewed for accuracy, context, and the JamForce voice. James reviews, edits, and approves the final content and remains responsible for it.

JamForce articles do not disclose confidential client information. Examples are generalised, illustrative, or based on information that can be shared publicly.

Publication and Update Dates

The metadata shown near the top of a page has a specific meaning:

• Published is the date the page first became public.
• Updated appears after a substantive public change, such as a factual correction, a changed recommendation, new release or security guidance, or a rewrite that changes the article’s meaning.

Minor spelling, grammar, formatting, or link-maintenance edits do not normally change the Updated date. Dates are not batch-changed simply to make older content look fresh.

Corrections

If you find an error, use the Contact form. Please include:

• The article URL and section heading
• What appears incorrect or unclear
• What you expected instead
• An official source, Salesforce release, API version, or reproducible example if one is available

The report is checked against the relevant source and, where practical, reproduced in a suitable non-production environment. If the correction materially changes the guidance, the article is updated and its dateModified value changes. A correction that could significantly affect implementation, security, data, or platform behaviour also receives a dated note near the relevant section or at the top of the article.

Small spelling, grammar, or formatting fixes may be made without a public correction note or a new Updated date. If a suggested change is not accepted, that may be because the current wording is supported, the behaviour depends on org configuration, or the available evidence is inconclusive.

Advertising and Editorial Independence

JamForce may display Google AdSense advertising to help cover the cost of running the site. Advertisers do not select topics, review drafts, or determine conclusions and recommendations.

JamForce does not currently publish paid sponsored articles or use affiliate links. If either is introduced, the commercial relationship will be clearly labelled so readers can distinguish it from independent editorial content.

Contact

Questions about this policy, article suggestions, and correction reports can be sent through the Contact Us page. Information about analytics, advertising, the consent message, and contact-form data is covered by the Privacy Policy.