Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update configure.md #3646

Merged
merged 2 commits into from
Nov 5, 2024
Merged

Update configure.md #3646

merged 2 commits into from
Nov 5, 2024

Conversation

npentrel
Copy link
Collaborator

@npentrel npentrel commented Oct 31, 2024

@viambot viambot added the safe to build This pull request is marked safe to build from a trusted zone label Oct 31, 2024
@npentrel npentrel force-pushed the npentrel-patch-3 branch 7 times, most recently from 901fade to e894fad Compare October 31, 2024 11:10
Comment on lines +76 to +82
You will now create a configuration that describes any connected hardware as well as any software your device uses.
The {{% glossary_tooltip term_id="component" text="_components_" %}} in your configuration can describe:

- Physical hardware, such as arms, motors, or cameras.
- Wrappers that provide additional functionality for other configured components, for example a failover motor that switches from one motor to another if the primary motor fails.
- Software that maps to the API calls that you would use for existing hardware types. For example, a temperature sensor may provide temperature readings based on an online service instead of hardware readings. Another such type of sensor that is frequently used returns _readings_ confirming it is safe to sync data or reconfigure a machine.
- Software that does not map well to the existing APIs, such as a switch that you'd like to be able to turn on an off. For these types of components, you use the generic component API.
Copy link
Collaborator Author

@npentrel npentrel Oct 31, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@IanWhalen I am rewriting this based on yesterday's discussion to test how we can trim/clarify this. While I've trimmed the steps, I think there is actually vital information missing. The physical hardware part is fairly obvious. The other three aren't. Especially the latter two are things that once people get it, get folks excited - based on our SEs.

We need to also consider teachable moments as we shorten content. At some point we do need to explain what's possible with the platform. I think we can skip over other parts of this but I'd assume this isn't one. Something to run by the SEs though.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i don't know if I want to think about this in terms of a diff. I expect I would like everything to be written from scratch as much as possible given the new IA we come up with.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok - I will merge this for now, since it removes some weirdness and we can see how a rewrite turns out

docs/how-tos/configure.md Outdated Show resolved Hide resolved
docs/how-tos/configure.md Outdated Show resolved Hide resolved
Co-authored-by: Sierra Guequierre <[email protected]>
@viambot
Copy link
Member

viambot commented Nov 4, 2024

You can view a rendered version of the docs from this PR at https://docs-test.viam.dev/3646

@npentrel npentrel merged commit abaef4c into main Nov 5, 2024
10 checks passed
@npentrel npentrel deleted the npentrel-patch-3 branch November 5, 2024 14:44
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.

4 participants