first-machine: add step 8 to add hardware in the CONFIGURE tab#5034
first-machine: add step 8 to add hardware in the CONFIGURE tab#5034shannonbradshaw wants to merge 1 commit into
Conversation
The walkthrough ended at step 7 (Connect with code), then sent users to a "What's next" link to configure hardware. But adding hardware is part of the first-machine flow, not a follow-up: a machine that is online but has no components configured is not yet useful. Adds step 8 as a brief, action-oriented step that points at the CONFIGURE tab and walks through the per-component flow (click +, select Component, search for the model, name, configure attributes). Links to /hardware/configure-hardware/ for the deep walkthrough rather than duplicating it inline. Removes the now-redundant "Configure hardware" bullet from What's next.
✅ Deploy Preview for viam-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
viambot
added
the
safe to build
|
Hey @shannonbradshaw — CI is green and no reviewer is assigned yet. Could you request one when you have a chance? Auto-comment from overwatch. Will not re-nudge for 7 days. |
3 similar comments
|
Hey @shannonbradshaw — CI is green and no reviewer is assigned yet. Could you request one when you have a chance? Auto-comment from overwatch. Will not re-nudge for 7 days. |
|
Hey @shannonbradshaw — CI is green and no reviewer is assigned yet. Could you request one when you have a chance? Auto-comment from overwatch. Will not re-nudge for 7 days. |
|
Hey @shannonbradshaw — CI is green and no reviewer is assigned yet. Could you request one when you have a chance? Auto-comment from overwatch. Will not re-nudge for 7 days. |
2 participants
Summary
Adds a step 8 to
/set-up-a-machine/first-machine/that points users at the CONFIGURE tab to add the hardware they want to use. The walkthrough previously ended at step 7 ("Connect with code") and pushed hardware configuration into a "What's next" link, but a machine that is online with no components configured is not yet useful — adding hardware belongs inside the first-machine flow.Changes
/hardware/configure-hardware/for the deep walkthrough rather than duplicating it.Test plan
/set-up-a-machine/first-machine/renders step 8 between step 7 and "What's next."/hardware/configure-hardware/resolves on the deploy preview.Note for review
I kept the existing order (step 7 Connect, then step 8 Add hardware) per the request. The reverse order (Add hardware → Connect with code) would let the SDK code sample see the configured resources, which is arguably the more natural flow. Happy to swap if preferred.