archive

To archive an article without breaking external links, move the file to an archive/ directory while preserving its original URL path. This ensures external references continue resolving and visitors see an informative archival notice instead of a broken page.

When retiring content, the frontmatter is automatically updated with archived metadata to annotate the article's status. This preserves the file's historical context while clearly marking it as archived for future readers and workflows.

Yes, the content retirement workflow appends a changelog entry to obsidian/workflow/changelog.md. This logs the archival operation for traceability, ensuring you maintain a clear historical record of when and why articles were retired.

Yes, the workflow scans for references to the archived article and surfaces them for potential updates or redirects. This reference integrity check helps you identify and manage internal links that might need adjustment after the file moves.

The best way to retire outdated content while keeping readers informed is to move it to an archive/ directory with an archival notice. This preserves the original URL so external citations resolve correctly, while visitors see an informative retirement message.

You should not use this archiving approach for articles not located under the obsidian/ directory, as the workflow specifically maps obsidian/ paths to archive/ paths. It is designed for retiring content while preserving URLs, not for permanent deletion.