News from ASCAND and 3D-Scan.Online
This is the chronological home for verified announcements from across the ASCAND ecosystem: physical capture, 3D-Scan.Online, education, museums, community activity and events.
Each article records what happened at a particular point in time. When an announcement introduces information that remains useful, it also links to the permanent page that owns the current product detail, technical explanation, instruction or support guidance.
Latest updates
News articles appear here in reverse chronological order. Each item identifies:
- its publication date;
- its principal topic;
- what was announced or reported;
- who or what the update affects; and
- where to find the current authoritative information.
Use the date as part of the meaning. A product, platform or workflow announcement describes the confirmed position when the article was published. It should not be used to infer current availability, compatibility, pricing, access, interface behavior or technical performance after those facts have changed.
Where a platform or product version is central to the update, the article should link to the corresponding Release Notes. Release Notes provide the version-level record; the news article provides context for readers.
Pagination should preserve the chronological sequence and provide a stable route to older entries. Search and category views should lead back to the same canonical articles rather than creating competing copies.
The WordPress Query Loop should insert verified published articles here. Do not publish fabricated examples or placeholder announcements.
Browse news by topic
Use the topic that best matches what you want to follow.
Product and Capture System
Announcements about ASCAND physical products, documented configurations, capture-system developments and newly published product resources.
3D-Scan.Online
Platform announcements that provide context beyond an individual version record, including meaningful workflow developments and newly available platform resources.
Education
Verified education resources, learning activities, institutional developments and events in which hands-on structured 3D capture is the principal subject.
Museums
Verified museum-oriented resources, engagement activities, collaborations and events. An article must not imply institutional endorsement, collection authorization or conservation suitability unless those facts are confirmed.
Community
Documented projects, contributions and stories whose participants, permissions, workflow context and result provenance are suitable for publication.
Events
Confirmed exhibitions, demonstrations, workshops or appearances with an absolute date, location or online destination, organizer, participation context and current status.
Categories help with browsing. They do not indicate that one update is more important, more authoritative or more commercially significant than another.
What belongs in News
News is for information whose date is part of its meaning.
Appropriate subjects include:
- a verified product or platform announcement;
- a confirmed change in availability or access;
- a newly published educational, museum or community resource;
- a documented collaboration;
- a confirmed event;
- a project or community development with publication permission; or
- an explanation of why a meaningful change matters to a particular audience.
Other content has a different owner:
- Current product facts belong on the relevant product page.
- Enduring technical explanations belong in the Knowledge Center.
- Ordered procedures belong in Tutorials.
- Fault diagnosis and current help belong in Support.
- Version-specific changes belong in Release Notes.
- Legal and privacy commitments belong in the current governing policy.
A news article can introduce and explain any of these subjects, but it should link to the permanent owner rather than becoming a competing source.
Every article should establish a verifiable record
A trustworthy update answers a small set of direct questions.
What happened? State the confirmed event or change in plain language.
When did it happen? Use an absolute date. Distinguish the date of the event from the publication date when they differ.
What does it affect? Identify the relevant ASCAND component, 3D-Scan.Online workflow, resource, audience or location without implying a wider scope.
What is confirmed? Separate released or completed work from plans, intentions, evaluation and future possibilities.
What are the limits? Include compatibility, availability, evidence, rights or participation boundaries when they are material to understanding the announcement.
Where is the current information? Link to the page that owns the lasting product fact, workflow, instruction, download, policy or version history.
Names of collaborators, institutions and participants require verification and permission. Quotations need an attributable source and approval for the intended use. Photographs and scan results must represent the actual subject and retain enough provenance to avoid becoming decorative proof of something they do not establish.
A visually appealing result does not by itself verify the capture method, object completeness, dimensional accuracy or suitability for another purpose. When a news story includes a model, the article should state only the workflow context supported by its evidence.
News records the moment; permanent pages own the lasting fact
News, evergreen pages and Release Notes answer different questions.
- News: What happened, when, and why is it relevant?
- Evergreen reference: What is currently true, and how does it work?
- Release Notes: What changed in a particular version, and where does that change apply?
For example, a news article may announce a newly available workflow. The platform or product page owns its current description. A tutorial owns the current operating sequence. Release Notes preserve the verified version and change record. Support owns diagnosis when the workflow does not produce the expected result.
This separation protects readers from obsolete guidance. An older announcement can remain a valid historical record even after the interface, access conditions or product configuration changes. It must not override the newer canonical page.
The same principle applies to privacy, rights and institutional information. A news post can report a relevant development, but current legal commitments remain with the governing policy and verified operational documentation.
Dates, corrections and archive context matter
Published articles should retain their original publication date. When an article receives a material factual correction, the correction should be visible, dated and specific enough for a reader to understand what changed.
A meaningful update may also justify a modified date. Routine formatting changes should not make an old article appear newly published.
When information has been superseded, the article should say so near the beginning and link to the current owner. When an event is cancelled or changed, its status should be updated without erasing the original context. If an article must be withdrawn, the remaining notice should identify that action without repeating material that cannot remain public.
This approach makes the archive useful. It allows readers to understand the sequence of developments while preventing an earlier announcement from masquerading as current documentation.
Follow the part of the ecosystem that matters to you
News is one way to follow ASCAND. For current information, go directly to the part of the ecosystem that owns your question:
- Explore ASCAND products for current product and configuration information.
- Explore ASCAND for education for hands-on learning pathways.
- Explore ASCAND for museums for museum engagement and learning contexts.
- Visit the Knowledge Center for enduring technical explanations.
- Read Release Notes for confirmed version-level changes.
- Contact ASCAND for institutional, partnership, media or general enquiries.
An email subscription or another notification channel should appear here only when its consent, frequency, delivery, unsubscribe and privacy behavior have been verified. Until then, this page remains the canonical chronological index.Use this page for a general enquiry about ASCAND, institutional use, a potential partnership, distribution, media or another commercial conversation.