Skip to content

Fix 13 app-linked anchor URLs across 10 pages#4975

Merged
shannonbradshaw merged 4 commits intoviamrobotics:mainfrom
shannonbradshaw:fix-app-anchors
Apr 18, 2026
Merged

Fix 13 app-linked anchor URLs across 10 pages#4975
shannonbradshaw merged 4 commits intoviamrobotics:mainfrom
shannonbradshaw:fix-app-anchors

Conversation

@shannonbradshaw
Copy link
Copy Markdown
Collaborator

Summary

The Viam app links to docs pages with specific #anchor fragments that don't exist after the IA migration. Users land at the page top instead of the relevant section. This PR adds custom heading IDs and HTML anchors so the 13 anchored URLs resolve correctly.

What's fixed

All 13 anchors verified in built HTML output (make build-prod + grep for id=).

App URL anchor Destination page Fix
#configure-agent-provisioning fleet/provision-devices.md Custom ID on "1. Create the defaults file"
#configure-networking-settings-for-tunneling fleet/system-settings.md Custom ID on "Configure tunneling"
#sbc-setup-instructions set-up-a-machine/overview.md Custom ID on "3. Select your platform"
#program-control-logic-in-module build-modules/write-a-logic-module.md Custom ID on "Steps"
#configure-hardware-on-your-machine hardware/configure-hardware.md Custom ID on "Add a component"
#machine-parts hardware/multi-machine/overview.md Custom ID on "Pick a pattern"
#teleop data/visualize-data.md Custom ID on "Build a Viam Teleop dashboard"
#dashboard data/visualize-data.md HTML anchor before same heading
#configure-data-capture data/capture-sync/capture-and-sync-data.md Custom ID + alias moved from data/_index.md
#supported-resources data/capture-sync/capture-and-sync-data.md New thin section
#upload-your-training-script train/train-a-model.md Thin pointer to custom-training-scripts
#click-for-more-information-on-parsing-command-line-inputs train/train-a-model.md Thin pointer to custom-training-scripts
#browse-supported-hardware-by-component-api hardware/configure-hardware.md HTML anchor + registry link

Not fixed (requires content work)

4 fleet API method anchors (#getlocationmetadata, #getorganizationmetadata, #getrobotmetadata, #getrobotpartmetadata) on reference/apis/fleet.md — the methods aren't documented on that page yet.

Test plan

  • vale 0 errors on all 9 changed files
  • make build-prod clean
  • All 13 anchor IDs verified in built HTML
  • Netlify deploy preview

🤖 Generated with Claude Code

The Viam app links to docs pages with specific anchors that no longer
exist after the IA migration. This adds custom heading IDs and HTML
anchors so users land at the right section instead of the page top.

Group 1 - custom heading IDs on existing headings:
  fleet/provision-devices.md: #configure-agent-provisioning
  fleet/system-settings.md: #configure-networking-settings-for-tunneling
  set-up-a-machine/overview.md: #sbc-setup-instructions
  build-modules/write-a-logic-module.md: #program-control-logic-in-module
  hardware/configure-hardware.md: #configure-hardware-on-your-machine
  hardware/multi-machine/overview.md: #machine-parts
  data/visualize-data.md: #teleop, #dashboard

Group 2 - alias target change + anchors:
  data/capture-sync/capture-and-sync-data.md: #configure-data-capture,
    #supported-resources (moved alias from data/_index.md)

Group 3 - thin pointer sections:
  train/train-a-model.md: #upload-your-training-script,
    #click-for-more-information-on-parsing-command-line-inputs

Group 4 - thin anchor + registry link:
  hardware/configure-hardware.md: #browse-supported-hardware-by-component-api

All 13 anchors verified in built HTML output.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 18, 2026

Deploy Preview for viam-docs ready!

Name Link
🔨 Latest commit b0ce914
🔍 Latest deploy log https://app.netlify.com/projects/viam-docs/deploys/69e3c8e59e74e80008bf1d1f
😎 Deploy Preview https://deploy-preview-4975--viam-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 45 (🟢 up 5 from production)
Accessibility: 99 (no change from production)
Best Practices: 83 (🔴 down 9 from production)
SEO: 89 (no change from production)
PWA: 60 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@viambot viambot added the safe to build This pull request is marked safe to build from a trusted zone label Apr 18, 2026
shannonbradshaw and others added 3 commits April 18, 2026 13:45
- set-up-a-machine/overview.md #sbc-setup-instructions: replace generic
  tip box with direct links to supported SBC setup guides
- data/capture-sync/capture-and-sync-data.md #supported-resources: add
  table of component types and capturable methods (verified against
  rdk/components/*/collectors.go)
- train/train-a-model.md #upload-your-training-script: add upload steps
  with CLI command instead of bare pointer link
- train/train-a-model.md #click-for-more-information-on-parsing-command-
  line-inputs: add the actual flags (--dataset_file, --model_output_directory,
  custom --key=value args) verified against rdk/cli/ml_training.go

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Replace the hand-picked list of 6 boards in set-up-a-machine/overview.md
with a single link to the device-setup landing page. The landing page
lists all 9 supported SBCs plus the ESP32 microcontroller section.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@shannonbradshaw shannonbradshaw merged commit 12b6514 into viamrobotics:main Apr 18, 2026
12 checks passed
@github-actions
Copy link
Copy Markdown

🔎💬 Inkeep AI search and chat service is syncing content for source 'Viam Docs'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe to build This pull request is marked safe to build from a trusted zone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants