Add description of custom cable required for daisy chain adapter

[elsevers]

Closes #166

Notes

Self-Review

1. Are all files under 300 kB (if not, please carefully assess whether it is worth committing them)? Yes
2. Are all files named according to the appropriate naming convention, i.e., dash-case, camelCase, snake case? Yes
3. Do all Markdown files follow the CONTRIBUTING article template? N/A - this follows the docs.amdc.dev article template
4. Do all links work in the material that the PR is adding? Yes
5. Is the PR configured to close the correct issue(s)? Yes
6. Did the PR fully address the Approach section of the issue(s) it is closing? Yes

Reviewer Instructions

Reviewers, please copy and paste a suitable review checklist into your review and answer all questions.

Appendix

This section should be the same for all PRs. Do not edit this section when creating a PR.

Review Checklists

Checklists maintained by the eLev lab for research repositories include:

• Report checklist
• Publication archive checklist (select a checklist from the Approach that corresponds to the step this PR seeks to complete).
• Standard checklist (if none of the above apply).

Standard checklist

1. Are all files under 300 kB (if not, please carefully assess whether it is worth committing them)? **Yes or No**
2. Are all files named according to the appropriate [naming convention](https://github.com/Severson-Group/research-repo-template?tab=readme-ov-file#file-naming), i.e., dash-case, camelCase, snake case? **Yes or No**
3. Do all Markdown files follow the [CONTRIBUTING article template](https://github.com/Severson-Group/.github/blob/main/CONTRIBUTING.md#markdown-documentation-template)? **Yes or No**
4. Do all links work in the material that the PR is adding? **Yes or No**
5. Is the PR configured to close the correct issue(s)? **Yes or No**
6. Did the PR fully address the `Approach` section of the issue(s) it is closing? **Yes or No**

Please work on addressing any **No** items.

[AwesomeTornado]

@elsevers The graphic you have attached does not render properly when using the dark mode theme for the website. I've approved this because it seems to be the standard, but it should really be changed.

Other than that, docs compile well, no warnings, page renders properly, markdown is formatted well.

1. Are all files under 300 kB (if not, please carefully assess whether it is worth committing them)? Yes
2. Are all files named according to the appropriate naming convention, i.e., dash-case, camelCase, snake case? Yes
3. Do all Markdown files follow the CONTRIBUTING article template? Yes
4. Do all links work in the material that the PR is adding? Yes
5. Is the PR configured to close the correct issue(s)? Yes
6. Did the PR fully address the Approach section of the issue(s) it is closing? Yes

[AwesomeTornado]

Export SVG with white background if possible to allow for dark mode viewing.
I've attached a screenshot of what the graphic looks like on my device.

[elsevers]

Nice catch. I discovered that this theme let's us have separate graphics for light vs dark mode. Take a look at what I just pushed up on the branch and see what you think. We can deploy it to other graphics as well.

:width: 75%
:align: center
:class: only-light

:width: 75%
:align: center
:class: only-dark

[AwesomeTornado]

@elsevers It's looking better but not fully there yet. There is supposed to be text on top of the ovals, but it is invisible because it is black. Change the text color, highlight it with a light color, or place a light colored box behind it and it should be good to go.

[elsevers]

Nice. Got it now.

[AwesomeTornado]

@elsevers This looks amazing!

1. Are all files under 300 kB (if not, please carefully assess whether it is worth committing them)? Yes
2. Are all files named according to the appropriate naming convention, i.e., dash-case, camelCase, snake case? Yes
3. Do all Markdown files follow the CONTRIBUTING article template? Yes
4. Do all links work in the material that the PR is adding? Yes
5. Is the PR configured to close the correct issue(s)? Yes
6. Did the PR fully address the Approach section of the issue(s) it is closing? Yes