Estimated reading time : 3 min · Published
Name the contributions you actually need
Explain what people may submit and why: correct a record, ask a question or supply an authorised testimonial. Omit fields no one can verify. Put understandable rules near the form, with examples instead of an abstract list.
Mozilla’s participation guidelines provide an example of an explicit behavioural framework, not a universal legal template. Adapt your rules to the audience and available moderators, and have service-specific obligations reviewed where needed.
Define a decision workflow
Choose useful states such as received, under review, published, refused or awaiting clarification. Define who decides and when a second reviewer is needed. Preapproval may suit some contributions, whereas immediate publication creates different monitoring needs.
Announce only response times the team can maintain. Receipt confirmation should not promise publication. For a directory, request a primary source and verify the proposed record before changing existing information.
Fictional case: an approved comment contains an author-supplied link. Editorial approval does not make received HTML safe to display. For plain text, retain context-appropriate escaping or use textContent on an ordinary element. If HTML formatting is intentionally allowed, use a maintained sanitizer with an explicit policy; searching for forbidden words is not a substitute. Do not later reinsert a raw version through innerHTML.
Handle links separately. For this example’s web link, validate the destination and permitted HTTP/HTTPS schemes, then correctly encode the attribute value. Google recommends rel="ugc" for user-content links and rel="sponsored" for paid placements. These qualifications describe a relationship to the search engine: they neither sanitize HTML nor verify facts. Keep the version actually reviewed; if the author edits after approval, apply the planned review process again before publication.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
| Fictional check | Technical reference | Expected result |
|---|---|---|
| Received, unreviewed contribution | Moderation state | Receipt alone does not make it public |
| Approved plain text | Contextual escaping or textContent | Text displays without being interpreted as HTML |
| Allowed formatting HTML | Maintained sanitizer and explicit policy | Allowed HTML is not later replaced by the raw version |
| User-supplied web link | URL validation; rel="ugc" as appropriate | The link is qualified without claiming rel prevents injection |
Support proportionate reporting
Provide a way to report an error or problematic content from its context. Ask for the relevant address and explanation without requiring sensitive copies for a simple correction. Define a recipient and a process for time-sensitive reports.
Test a valid submission, incomplete request, repetition and lost notification. Check that refusals are understandable and one person’s contribution is not attributed to another. Keep acceptance examples synthetic rather than publishing simulated testimonials.
Retain a useful decision record
Record state, reason and owner while limiting stored information. Separate internal notes from material suitable for publication. Plan contribution correction or removal according to applicable rules and context.
Review difficult cases to identify missing information, unrealistic timelines and confusing steps. Deliver an owner-assigned receipt–decision–publication–reporting workflow with examples and stated limitations.
Primary documentation : Mozilla : Community Participation Guidelines.
Reference documents
- OWASP : Input Validation Cheat Sheet · Source consulted
- Google Search Central : Qualify outbound links · Source consulted
- OWASP : Cross Site Scripting Prevention · Source consulted
- Mozilla : Community Participation Guidelines
Content updated on
