Skip to content

Editorial and Privacy Policy

These notes are designed for public use. Technical rigor and privacy are part of the content standard, not optional review steps.

Technical standard

Substantial articles should include:

  1. learning objectives and prerequisites;
  2. a precise definition and an intuitive explanation;
  3. explicit preconditions and postconditions;
  4. an example or execution trace;
  5. pseudocode or executable code;
  6. a correctness argument when an algorithm is presented;
  7. time and auxiliary-space analysis;
  8. limitations, edge cases, and common mistakes;
  9. exercises; and
  10. references to primary specifications or established textbooks.

Claims about a particular library or framework version must be checked against its official documentation. Measurements must describe the environment and methodology; a single timing result is not a general performance claim.

Public-safe examples

Examples must not contain or indirectly reveal:

  • names of private, work, client, or research projects;
  • real internal hostnames, repositories, account identifiers, or datasets;
  • credentials, tokens, personal records, or realistic secret values;
  • private architectural diagrams, incidents, metrics, or business rules; or
  • details copied from non-public systems.

Use neutral domains such as books, shapes, tasks, and graph vertices. Use reserved example domains such as example.com for network examples.

Language and translations

English is currently canonical. Technical identifiers remain in English in all future translations. A Brazilian Portuguese page must preserve definitions, contracts, code, formulas, citations, and semantic structure. Corrections land in the English source first and are then propagated to translations.

Page checklist

  • [ ] The title describes one clear topic.
  • [ ] Terminology agrees with the glossary.
  • [ ] All code and internal links have been validated.
  • [ ] Complexity states the relevant case and space convention.
  • [ ] Theory and implementation-specific behavior are distinguished.
  • [ ] No example exposes personal or non-public context.
  • [ ] Sources support claims that are not derived on the page.