Lêst bywurke:
2 wiken lyn
Before making any edits, it's important to understand that we treat content workflow differently based on the significance of the changes.
All new articles and major changes to support articles need to be accompanied by a content request via Bugzilla (see How to submit a SUMO Knowledge Base content request), while minor changes can be submitted directly in the article without content request.
Table of Contents
What qualifies as minor changes
Here are what we consider to be minor changes:
- Fixing small typos
- Removing unnecessary white spaces
- Correcting spelling, grammar or punctuation errors
- Fixing wiki markup formatting (headings, bullets, numbering, spacing, indentation)
- Updating small factual details (for example: version numbers, button or menu labels) without rewriting sections
- Updating sections and replacing them with existing templates without changing the original context
- Correcting outdated or unsupported content, including maintenance updates such as adding or removing version tags, without substantial change to the underlying guidance
- Removing content and markup related to product versions that are no longer supported
- Improving readability or clarity through small instructional refinements, simplified wording, or incorporating visual cues for accessibility (for example: adding icons and menu references) without substantially changing guidance or article structure
- Updating broken links, links to renamed KB articles or links with the same target content
- Adjusting tone to meet Mozilla’s support content standards
- Replacing outdated UI screenshots with updated versions (up to 3 screenshots maximum)
- Updating keywords
- Adding or updating a search summary
What qualifies as major changes
Major changes to Knowledge Base (KB) support articles require a Bugzilla request to facilitate coordination with product stakeholders, ensure content accuracy, track progress, and support cross-functional collaboration.
Below are changes we consider major:
- Creating new article
- Changes that require validation from product stakeholders or close coordination with them, including:
- Updates related to release readiness
- Substantial content additions (such as new instructions, FAQs or troubleshooting steps)
- Replacing outdated screenshots or adding new screenshots beyond 3 images
- Substantial changes affecting user guidance or article structure that require review by the Content team, including:
- Removing an existing section
- Extensive rewriting of paragraphs or sections
- Large-scale formatting or structural changes (such as reorganizing multiple sections or changing article flow)
- Changing the scope or intent of the article
- Updating, adding, or removing screencasts, GIFs or videos
- Rewriting or renaming section headings that may affect anchor links or article navigation
To learn more about Knowledge Base contribution, please check out How to contribute to the Knowledge Base.
