Blueprint pages should show scan logic
A useful fragment page needs more than a name. It should show the number of scans, the likely route, whether a tool is required, what danger to expect and what the blueprint enables. This helps players decide whether the dive is worth doing now.
| Blueprint path | Why players search it | First-page treatment |
|---|---|---|
| Scanner | Core exploration and data collection | Starter recipe and first use |
| Habitat Builder | Base construction blocker | Scan route, recipe, base basics |
| Tadpole | Mobility and oxygen extension | Fragment route and upgrade notes |
| Power tools | Base reliability | Power source comparison |
| Upgrade stations | Progression crafting | Prerequisites and route order |
Fragment data needs revision dates
Fragment guides can age quickly. Add a checked date to every route and keep a short change log when a patch moves scan locations or changes recipes.