Blume buying guide: Keep old links working when moving Markdown to a site

Use three mock pages to check navigation and deep links before replacing an existing documentation site.

Source: useblume.dev
September 13, 2026
1 min

If your product docs already live in Markdown but you want to choose the host yourself, the Blume framework at useblume.dev is worth evaluating. Its Telemetry case records the first documentation commit on August 7, 2026 and describes a build to independently hosted static files. That supports the feasibility of a new site, not automatic preservation of existing navigation and links.

Make a paper migration map without building or deploying. Invent three pages: Getting started, Install and Upgrade. An old support note links to “Check the version” within Install. Ask a colleague to reach it from the homepage navigation and then via the old address. Opening the right page but missing the heading fails. Record each old address, expected landing point and who restores the old site if that check fails.

A new site without outside bookmarks can start with a small check. Where old URLs are widely cited, budget for redirects, heading anchors and rollback. Open source does not remove build upkeep. Check that the static files fit your host and that original Markdown and the URL inventory can be retained. Keep the existing site if it is stable and migration does not meaningfully reduce maintenance.

Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.

Original source:useblume.dev