Knowledge HubGive each document an identity
Assign a stable identifier and record product, version, language, audience and source. Multiple pages can link to the same primary record. Matching filenames do not prove identical content.
Separate server timestamps, dates stated in the document and project review dates. A download date should not replace all three.
Freeze the acceptance baseline
Record the specifications and guides used during testing. When APIs, models or environments change, identify affected resources and the people responsible for reviewing them.
Archived versions can remain useful for older deployments. Label them clearly and direct new projects to confirmed applicable material rather than deleting every earlier edition.
Treat translations as linked versions
Link Vietnamese and English editions by content identity rather than title alone. Track the translation source and changes to detect stale editions. Keep technical identifiers consistent.
If the source file exists in one language only, label it clearly. A translated summary does not mean the downloadable document was translated.
Assign publishing responsibilities
Product owners confirm scope, engineers review examples, editors check presentation and translators check terminology. Leave ownership fields unassigned when no responsible person is confirmed.
Maintain change records, link checks and review triggers aligned with product changes. Meaningful updates should reach the content, search data and metadata together.