One Primary Intent Per Page

Before drafting, we define the main question or task the page should solve. The page should stay inside that information territory rather than becoming a generic summary of everything related to the platform.

If another page already owns a detailed topic, we avoid recreating the same explanation and instead use a brief contextual reference where genuinely necessary.

Official Sources Come First for Product Facts

For changeable platform details—such as pricing, plans, modes, login methods, assignments, reports, limits, privacy settings, or feature availability—we prefer the platform's current official website, help center, documentation, policy pages, or product interface.

Secondary sources may provide context, but they should not replace a current primary source when the primary source is available.

Volatile Facts Are Treated as Time-Sensitive

Product interfaces and commercial terms can change. We therefore avoid treating old prices, old mode lists, old plan limits, or retired terminology as permanently true.

Where a detail is especially changeable, we either verify it close to publication/update time or write the explanation so it remains useful without pretending a temporary value is permanent.

Original Explanations, Not Source Repackaging

Research supports the article; it should not become copied source text. We write original explanations, workflows, decision aids, examples, troubleshooting structures, or practical context designed for the page's specific audience and intent.

We do not create fake firsthand experiences, fabricated quotes, invented statistics, or fictional user outcomes to make an article appear more authoritative.

Reviews & Comparisons Need a Defined Lens

A review or comparison should state what is actually being examined: for example setup, classroom workflow, question creation, reporting, self-paced use, accessibility, or pricing structure.

We distinguish observed/documented product differences from opinion, and avoid presenting promotional claims as established facts.

Learning Claims Require Care

We avoid claiming that a tool automatically improves retention, achievement, motivation, or learning outcomes merely because it is interactive or game-based.

Where educational research is discussed, the claim should match the strength and population of the evidence rather than being stretched into a universal promise.

AI May Assist, but It Does Not Replace Verification

AI tools may assist with organization, drafting, editing, coding, summarization, or research workflows. AI-generated wording or analysis is not treated as proof that a factual claim is correct.

Important product facts should still be checked against appropriate evidence, and final content should be reviewed for hallucinated details, unsupported claims, repetition, and unclear attribution.

Images Should Match What They Represent

Images may be original, appropriately licensed, supplied by an authorized source, or created with generative tools. Illustrative or AI-generated visuals should not be presented as proof of an official product interface when they are not an actual screenshot.

Location-, feature-, or interface-specific imagery should be selected carefully enough that it does not mislead the reader about what is actually being shown.

Guest or Contributed Content Uses the Same Standards

A submission, partnership proposal, or guest contribution does not automatically qualify for publication. Material should be original, relevant, useful, and capable of meeting the same factual and editorial standards applied to internally produced content.

Commercial involvement should not be disguised as independent editorial judgment. Where material is sponsored or otherwise requires disclosure, it should be identified appropriately.

Errors Should Be Corrected, Not Defended

If a factual problem, outdated product detail, broken instruction, or material ambiguity is identified, we review the evidence and update the page when a correction is justified.

Minor wording or formatting fixes may be made without a separate notice. Material changes should be reflected in the page itself so readers see the corrected information rather than an outdated version.

Dates Should Reflect Meaningful Work

Updating a page date should correspond to a meaningful review, factual update, structural improvement, or other substantive change—not simply changing a timestamp to make old content appear fresh.

Useful Content Comes Before Search Decoration

Titles, headings, internal links, structured sections, and search optimization should help users understand the page. They should not be used to hide thin content, inflate word count, or force unrelated keywords into an article.

Our goal is a page that still makes sense and remains useful even when read without considering search rankings.