Purpose

Articles become inaccurate not because writers make mistakes, but because the world changes around them. This document lists the events that should trigger a mandatory article review.

Platform release triggers

When a new School Vault version is released, review all articles that describe the changed feature area:

  • Any UI change (renamed menu item, new screen layout, removed button), review articles in the affected track immediately. [Screenshot: description] placeholders in those articles also need updating if the UI has changed.
  • New feature, check whether any existing article should link to a new article that explains the feature.
  • Feature removal, find all articles that mention the removed feature and update them. Do not leave instructions for things that no longer exist.
  • Changed limit or pricing, e.g. if the subscription price changes from ₦7,500 to a different amount, every article that states the price must be updated before the release date.

Integration partner triggers

External integrations can change without notice:

  • Paystack dashboard UI changes, if Paystack moves their API keys section to a different location, article 5.4 becomes incorrect. Check Paystack's changelog quarterly.
  • Termii pricing or API changes, affects article 4.6.
  • WhatsApp Business API policy changes, Meta changes messaging policies periodically. Article 4.6 covers WhatsApp.
  • Nigerian banking regulations, NIBSS or CBN policy changes can affect how DVAs work (article 5.3).

Regulatory triggers

  • NDPR/NDPA amendments, NITDA guidance updates. Article 8.4 must reflect current law.
  • NERDC curriculum changes, if the national curriculum is revised, articles 2.6 and the grade band table in article 6.2 need reviewing.
  • Nigeria National Immunisation Schedule changes, article 4.3.

Stale date triggers

The stale_after date on each article generates an automatic review reminder. When the Academy admin receives a stale article alert:

  1. Open the article.
  2. Read through it against the current live platform.
  3. If the article is still accurate: update last_reviewed and stale_after only.
  4. If the article needs corrections: make corrections, increment the version, add a changelog entry, update all date fields.

User feedback triggers

If a user contacts support with a question that the article should have answered but did not, the article has a gap. After resolving the support query:

  1. Add the missing information to the relevant article.
  2. Add the missing scenario to the Common Mistakes section if appropriate.
  3. Update all date/version fields and add a changelog entry: "Added guidance on [topic] following support query."