Define the need
Before writing, we identify the question, intended audience and action the page should support. A page with no identifiable utility is not published merely to occupy a search query.
We favour project-specific value: structured data, collection organisation, explicit comparisons and useful source links.
Collect and qualify
Information comes from the relevant websites and, when needed, primary or recognised sources. We distinguish verifiable claims, editorial presentation and opinion.
Date, author, responsible organisation, proximity to the event and commercial interest help determine how much confidence a source deserves.
Write and review
AI tools may suggest a structure, rephrase, translate or draft. They are not sources and their output is not treated as true by default.
Review looks for contradictions, overconfident wording, unsupported figures, broken links and ambiguity. The final text must remain proportionate to what was checked.
Publish, date and correct
Important pages expose update dates through metadata. Volatile information needs more frequent review than methodological content.
A precise report triggers a new reading. Content may then be corrected, expanded, annotated or removed.
What the method cannot guarantee
No reasonable process guarantees that every page is error-free or instantly current. The method reduces risk and makes choices explicit; it does not turn this portal into a universal official source.
For health, law, finance, safety or another high-impact decision, consult a qualified professional or competent authority.
A hierarchy of sources
For a website record, the first source is usually the website itself: homepage, about page, legal notice, documentation or service pages. This shows what the project says, but does not always confirm that every statement is accurate.
When external verification is necessary, we prefer official text, documentation from the responsible body, original data or the full document before commentary about it. Recognised media and specialist publications can add context, while anonymous aggregators and repeated summaries carry less weight.
A secondary source can be excellent for explanation. It should simply not be presented as primary evidence when a more direct source exists.
Risk-based checking
A general category, an available language or the existence of a contact page can be observed directly. A statistic, legal duty, health recommendation or safety claim requires stronger precautions.
We consider the possible severity of an error, how quickly the information can change and whether readers can verify it themselves. As risk rises, the text should state its limits, point to a competent authority or avoid a conclusion that is too broad.
This approach prevents the same level of certainty from being applied mechanically to information of very different kinds.
Pre-publication control
Final review checks that the title matches the content, each section answers a useful question and repetition is not hiding a lack of information. Links, names, dates and comparative wording are checked separately.
We also look for signs of artificially expanded text: interchangeable introductions, conclusions with no additional value, lists that merely repeat the previous paragraph and vague statements that cannot be assessed.
A page is ready when its usefulness can be explained clearly, its limits are visible and readers know which source to consult next.
Editorial maintenance
Reports, inaccessible links, redirect changes and inconsistencies found during review feed the maintenance process. A simple correction can be made directly; a substantive change requires the sources to be qualified again.
We avoid changing a date merely to create an appearance of freshness. An update should reflect a real change to the text, structure, links or published information.
When a page can no longer be maintained usefully, removing it is preferable to keeping content that is clearly outdated.