Skip to content

Commit 821a5a7

Browse files
Restore foundation/* aliases on three pages clobbered by the rename sed
The rename-sed run replaced /foundation/ with /set-up-a-machine/ across all docs files. On three files that had /foundation/* entries inside their aliases list (not just as body links), this broke the aliases: - docs/data/capture-sync/capture-and-sync-data.md - docs/data/capture-sync/stop-data-capture.md - docs/hardware/common-components/add-a-camera.md Each had two alias rows like "/foundation/add-a-camera/" that redirected users from legacy URLs to the current canonical page. After my sed, those aliases pointed at /set-up-a-machine/add-a- camera/, which is not a real URL and does not resolve anywhere. The no-more-404 Netlify plugin flagged the resulting missing /foundation/* URLs. Fixed by restoring the original /foundation/ and /build/foundation/ aliases. Verified locally with make build-prod: - public/foundation/capture-and-sync-data/index.html OK - public/foundation/stop-data-capture/index.html OK - public/foundation/add-a-camera/index.html OK This is the kind of thing a playbook amendment should catch. The sed was right for body-text link updates, wrong for alias-list updates. Future directory renames need a targeted approach that distinguishes the two, plus a mandatory local make build-prod before pushing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent 348efb6 commit 821a5a7

3 files changed

Lines changed: 6 additions & 6 deletions

File tree

docs/data/capture-sync/capture-and-sync-data.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@ description: "Capture data from any resource and sync it to the cloud."
88
date: "2025-01-30"
99
aliases:
1010
- /data/capture-and-sync-data/
11-
- /build/set-up-a-machine/capture-and-sync-data/
12-
- /set-up-a-machine/capture-and-sync-data/
11+
- /build/foundation/capture-and-sync-data/
12+
- /foundation/capture-and-sync-data/
1313
---
1414

1515
Configure your machine to automatically record sensor readings, camera images, and other component data, then sync it to the cloud. For an overview of how data capture and sync work, see the [Manage data overview](/data/overview/).

docs/data/capture-sync/stop-data-capture.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@ description: "Stop capturing data for specific resources, all resources, or disa
88
date: "2025-01-30"
99
aliases:
1010
- /data/stop-data-capture/
11-
- /build/set-up-a-machine/stop-data-capture/
12-
- /set-up-a-machine/stop-data-capture/
11+
- /build/foundation/stop-data-capture/
12+
- /foundation/stop-data-capture/
1313
---
1414

1515
Stop data capture temporarily (during maintenance, testing, or debugging) or permanently. You can disable capture for a single resource, turn it off for all resources on a machine, or leave capture running locally but stop syncing to the cloud.

docs/hardware/common-components/add-a-camera.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ type: "docs"
77
description: "Add and configure a camera component, verify the feed, and capture an image programmatically."
88
date: "2025-01-30"
99
aliases:
10-
- /build/set-up-a-machine/add-a-camera/
11-
- /set-up-a-machine/add-a-camera/
10+
- /build/foundation/add-a-camera/
11+
- /foundation/add-a-camera/
1212
- /hardware-components/add-a-camera/
1313
- /hardware/add-a-camera/
1414
- /hardware/components/add-a-camera/

0 commit comments

Comments
 (0)