Page Review and Updating

F4L5E G0DS EVE-EMU page review and updating guide

Review cadence, evidence standards, update procedure, and verification rules for maintained pages.

Field	Value
Wiki platform	MediaWiki / Wikimedia-style wikitext source editing
Primary standard	F4L5E G0DS EVE-EMU Standard Guide Template
Source document	F4L5E_G0DS_EVE_EMU_Wiki_Guides.docx
Prepared date	2026-07-05

This guide defines how to review pages for accuracy, currency, formatting, and usefulness. It is intended for page owners, senior editors, corporation staff, and anyone maintaining operational documentation.

Review triggers

• A major EVE Online expansion or patch changes mechanics, skills, structures, markets, or UI.
• FC, corporation, alliance, or coalition policy changes.
• A user reports that a page is wrong or unclear.
• The page has not been verified within its review cadence.
• A related page has been rewritten and links or terminology may now be inconsistent.
• A template, category structure, or wiki skin change affects rendering.

Review cadence

Page type	Recommended cadence	Reason
Core game mechanic guide	Every major expansion or every 6 months	Mechanics, UI, and numbers can change.
Market or tax calculation page	Monthly or after major market/system changes	Prices, fees, indices, and assumptions drift quickly.
Corporation service page	Quarterly or after policy changes	Access, owners, and procedures can change.
Doctrine-support page	After doctrine change or every 3 months	Fits, skill assumptions, and escalation rules change.
Reference category or style page	Every 6 months	Standards should remain stable but not stale.
Archived or historical page	Only when archive status changes	Avoid unnecessary churn on intentionally historical pages.

Review levels

Level	Scope	Result
Level 1: quick scan	Check obvious rendering, broken placeholders, missing categories, and outdated banners.	Minor fixes or route to deeper review.
Level 2: content review	Verify steps, mechanics, requirements, risks, links, formulas, and examples.	Update page and last verified date if confirmed.
Level 3: subject-matter review	Ask an experienced player, service owner, or policy owner to validate the page.	Approve, revise, or flag disputed sections.
Level 4: structural rewrite	Rebuild the page using the standard template when structure blocks maintenance.	Publish a clean version with clear edit summary.

Evidence hierarchy

Use the strongest available evidence. A page can be clear and still be wrong if it relies on stale assumptions.

Evidence type	Use for	Caution
Current in-game verification	UI steps, stats, service behavior, live mechanics	Record date, character context, and location if relevant.
Official patch notes or support pages	Patch-related mechanics and feature changes	Confirm the page reflects the current state, not only a historical change.
Maintained external wiki pages	Cross-checking general mechanics	Do not copy style or wording directly.
FC internal policy records	Corporation, alliance, or coalition rules	Label as policy, not universal game mechanics.
Screenshots	UI state, site waves, dialog boxes, structure setup	Crop clearly and avoid exposing sensitive information.
Player reports	Bug leads, unclear instructions, missing cases	Verify before converting reports into factual claims.

Review procedure

1. Open the page in read mode and read it as a new player would.
2. Check the guide summary table for page owner and last verified date.
3. Open the page history and scan recent edits for context.
4. Check all maintenance banners and resolve what can be resolved.
5. Review the lead and quick start for accuracy and usefulness.
6. Verify requirements, skills, ISK assumptions, tools, structure services, access, and policy dependencies.
7. Check each procedure step against the current game or current FC workflow.
8. Check calculations and examples for assumptions, current values, and formula errors.
9. Check links, references, categories, and see-also entries.
10. Update content, banners, page owner, and last verified date as appropriate.
11. Preview, save with a descriptive edit summary, then check the rendered page.

Handling outdated or uncertain information

Condition	Action
Information is confirmed correct.	Leave it, improve wording if useful, and update last verified date if the review was broad enough.
Information is wrong and the correction is known.	Correct it and cite or explain the basis for the correction.
Information is probably wrong but not yet verified.	Flag the specific claim for verification and explain the suspected issue.
The whole page is outdated.	Add an update notice, summarize the reason, and assign or request an owner.
The page is structurally unusable.	Rewrite using the standard guide template or create a replacement draft.
The page is obsolete but historically useful.	Mark as archived or historical according to local wiki practice.

Last verified field

The last verified field is a promise that the page, or the relevant section, has been checked against current information. Do not update it for copyediting alone.

Edit type	Update last verified?
Typo, grammar, or formatting only	No
Broken link replacement only	No, unless the linked source was used to verify content
Checked every procedure step in game	Yes
Confirmed policy with current owner	Yes for policy pages
Updated formula with current assumptions	Yes, if assumptions and source are documented
Added a warning based on an unverified report	No; use a verification notice instead

Review checklist

• The page purpose is still valid.
• The title and lead match the page content.
• The guide summary table is accurate.
• The page owner is current.
• The last verified date is justified.
• All procedures reflect current game mechanics or current FC workflow.
• All risks and prerequisites are still true.
• Market, tax, and calculation assumptions are current or dated clearly.
• Screenshots and UI references match the current interface.
• Maintenance banners are accurate and not stale.
• Categories are approved and useful.
• The page has no unresolved placeholders.

Review record format

For important pages, add a short review record on the talk page or a designated review log page.

== Review record: YYYY-MM-DD ==
* Reviewer: [[User:Name]]
* Scope: Full page / Section only / Policy only / Formula only
* Evidence checked: In-game / Patch notes / FC policy / External reference
* Result: Verified / Updated / Flagged for review / Needs owner
* Notes: [brief summary]
~~~~

Standard maintenance notices

The exact template names depend on what has been installed on the F4L5E G0DS EVE-EMU wiki. If these templates do not exist yet, create them or use plain-text notices until the template set is available.

Notice	Suggested wikitext	When to remove
Work in progress	{{Work in progress}}	When active editing is complete or has gone stale.
Update	{{Update|reason=Needs verification after latest mechanics or policy change.}}	When content has been updated and verified.
Cleanup	{{Cleanup|reason=Needs formatting, references, or technical-writing pass.}}	When style, grammar, structure, and readability issues are fixed.
Verify	{{Verify|reason=Specific claim needs confirmation.}}	When the specific claim has been confirmed or corrected.
Merge	{{Merge|Target page}}	When merge decision is complete.

Sources consulted

The document adapts standards to the F4L5E G0DS EVE-EMU context rather than copying external guide text. Sources consulted for structure and practices:

Source	Location
F4L5E G0DS EVE-EMU Standard Guide Template	Attached file: eve_emu_standard_guide_template.mediawiki
MediaWiki Help:Starting a new page	https://www.mediawiki.org/wiki/Help:Starting_a_new_page
MediaWiki Help:SourceEditor/User guide	https://www.mediawiki.org/wiki/Help:SourceEditor/User_guide/en
MediaWiki Help:Categories	https://www.mediawiki.org/wiki/Help:Categories