The archive separates an event announcement, a program listing and a post-event recap. Each source answers a different question and is described according to its date and publisher.
Names and schedules
Session titles, speakers, times, rooms and sponsor relationships appear only when a dated record supports them. A theme announcement is not treated as a confirmed session slot, and a missing field is not filled from a later conference.
Current status
Registration, ticket sales, travel arrangements and event services are not current here. Historical prices or deadlines, if documented, remain tied to the original period and are not presented as offers.
Submitting a correction to the event record
Send the page URL and a dated source to the editor. Changes are made when the record supports them. The separate crypto-donations explainer is not evidence about the 2018 program.
Use the correct type of evidence
A pre-event announcement establishes what the organizer planned or promoted. A post-event recap records what the organizer later said happened. A session listing may establish a title or time only when those fields appear in the dated schedule. Keep the date and document type with a claim when editing or quoting it.
Do not fill historical gaps by inference
Do not invent a speaker, session room, sponsor, ticket inclusion or attendee outcome from a broad theme. A supplier mentioned in a later corporate story is not automatically a conference sponsor. If the material is incomplete, explain what it supports and leave the unknown field out.
Separate the archive from current guidance
Prices and deadlines belong to the 2018 edition. Current venue, registration, company and product details require current sources. Cryptocurrency-giving content is a separate modern explainer and should never be attributed to the conference without event-period evidence.
Corrections and page maintenance
Send the page URL, the exact passage and a dated source to the editor. Corrections are checked against the event edition before page text, title and structured data are updated. Links and images are reviewed in context so they clarify the page instead of implying current availability.
Prepare a factual update
A dated record is easier to maintain when every revision has a traceable source.
- Identify the event edition and date the statement concerns.
- Prefer the organizer’s dated record for schedule and attendance claims.
- Add attribution and retain the source version with the page update.
Images, names and data
Images should represent event materials, wayfinding or abstract program context. Do not fabricate portraits of speakers or logos of supposed sponsors. Alt text should describe the actual visual content; captions should help a reader interpret a route, schedule or document. Historical names and figures must remain consistent with the dated record.
Structured data and search fields
Page titles and descriptions should describe visible content. FAQ schema is used only where the question and answer appear in the page body. Breadcrumb data follows the current route or its preserved historical path. Utility pages such as contact and privacy are not treated as primary search landing pages.
The archive method describes how event announcements and post-event accounts are kept distinct. Browse the archive index for the retained conference routes.
Corrections to the event record
How should I report an incorrect date or venue detail?
Send the page URL and a dated organizer or venue source that supports the correction. The archive can then compare the claim with the relevant edition.
Will an archive gap be filled from memory?
No. A detail is included only when a usable source supports it; uncertain titles, schedules and outcomes remain unasserted.