Wiki content lifecycle management
This page was created by Wikiadmin on 2026-07-29. Last edited by Wikiadmin on 2026-07-29.
This page helps MDriven wiki contributors keep documentation accurate, connected, and useful as questions, product knowledge, and reader needs change.
Content lifecycle
| Stage | What to do | Concrete example |
|---|---|---|
| Identify | Capture missing topics and unclear explanations from reader suggestions, MDriven Designer questions, and YouTube discussions. | A reader cannot find an explanation of an OCL operation. Add or improve the relevant operator page, such as Documentation:OCLOperators allStates. |
| Update | Add the explanation, procedure, or example to the page that owns the topic. Keep the description concrete and use the product terminology consistently. | Add an example showing that allStates returns the names of states defined for a class.
|
| Connect | Add links that take readers to the next relevant topic. Link related wiki pages from the first relevant mention. | Link an operator explanation to related OCL material so that a reader can continue from the operator to the broader topic. |
| Review | Use reader feedback to find gaps in navigation, missing examples, and pages that need clarification. Update the affected pages and links. | If readers leave a deployment overview without reaching a deployment guide, review the links and task flow in Documentation:Deployment. |
Review triggers
Review a page when one of these events occurs:
- A reader or team member identifies a missing topic, unclear explanation, or broken learning flow.
- A question from YouTube or MDriven Designer work reveals information that readers need in the wiki.
- A related page is added or changed and the navigation between the pages should be updated.
Contribution and linking
When you edit a page, add links to the related concepts that a reader is likely to need next. Treat interlinking as part of the update, not as a separate cleanup task.
For example, a page that introduces model documentation can link to Documentation:Documtr and XPS.
Ownership and continuous improvement
Contributors can help by reporting missing topics, supplying examples, and adding links between related pages. The documentation work uses feedback to prioritize improvements.