-
Notifications
You must be signed in to change notification settings - Fork 184
docs(stacker): Stacker instruction manual PR #18664
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
base: edge
Are you sure you want to change the base?
Conversation
Committing Stacker instruction manual files.
Committing Stacker instruction manual files.
b831393
to
b38beb8
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## edge #18664 +/- ##
=======================================
Coverage 56.91% 56.91%
=======================================
Files 3243 3243
Lines 282323 282323
Branches 35451 35451
=======================================
Hits 160680 160680
Misses 121440 121440
Partials 203 203
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Lots of code style comments. Happy to talk through them and make decisions on standardizing things across docs sites.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should come up with a standard format for cover pages. Probably one of:
- Same as print covers. Just logo, title, hero, company name, date.
- Print cover info + Product Description. This is probably good for SEO or RAG or whatever.
Either way, I would move Manufacturer Description to the Additional Product Information page. Some print pubs have that ordering anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, will move the mfg description to the back, to the Additional Info page.
Here's my thinking about the home/landing page: I put the product description on this page because without it, the page doesn't have much information value. It's just an image and date of publication. The product summary seems nice here as it adds a small amount of information to what would otherwise be just a page with a picture. A little different than the manuals, but as a landing page, now it shows you the thing and provides a short description.
docs/stacker-manual/docs/index.md
Outdated
<img src="/images/tm-opentrons-flex.png" alt="flex-tm" style="width:70%"> | ||
</a> | ||
|
||
# **Stacker Module GEN1 Instruction Manual** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
H1 should never need or have bold styling.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed bold, but the text looks too skinny to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll make sure we have the right weight across the board in our theme CSS file.
docs/stacker-manual/docs/index.md
Outdated
<b>[Opentrons Labworks Inc](https://opentrons.com/)</b><br> | ||
August 2025 | ||
/// | ||
</figure markdown> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Closing HTML tags don't have attributes. (This would be an error if you were doing HTML validation.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My code here is super-wonky. Going to fix it.
docs/stacker-manual/docs/index.md
Outdated
|
||
## Product Description | ||
|
||
The Opentrons Flex™ Stacker is an external module that provides automated, high-capacity storage for ANSI/SLAS compatible labware such as well plates, tip racks, and reservoirs. It also includes a shuttle, which moves labware from the Stacker to the deck where it can be accessed manually or by the Flex Gripper. While ideal for high-throughput NGS workflows, the Stacker can help streamline a wide range of automated liquid handling protocols. When attached, the Stacker increases your robot’s labware storage capacity and throughput, allowing you to run longer, more complex protocols without interruption. Each Flex supports up to four attached Stackers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use unicode everywhere. It makes the source more readable. So ™
here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would recommend not repeating "stacker" in file names. The ultimate URL for this page would be something like docs.opentrons.com/stacker-manual/stacker-compliance
. This is one reason I think just stacker
would be better for the parent directory as well: docs.opentrons.com/stacker/compliance
is very clean and includes all the same information.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shortening the file names. Dropping stacker-
.
.center-image { | ||
display: block; /* Make the image a block-level element */ | ||
margin-left: auto; /* Push it to the center horizontally */ | ||
margin-right: auto; /* Push it to the center horizontally */ | ||
} | ||
|
||
/* New class for end-of-doc trademark text */ | ||
.trademark-text { | ||
font-size: 0.85em; /* set size */ | ||
color: #555; /* set color */ | ||
display: block; /* text acts like a paragraph */ | ||
margin-top: 2em; /* spacing at top */ | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These look like ""helpful"" LLM comments 🤖 They're noisy and we should remove them.
- md_in_html | ||
- toc: | ||
permalink: true | ||
title: <u>Page Contents</u> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove the underline here and rely on theme CSS (if we decide to underline it at all; it looks like a link, but it's not)
copyright: | ||
Copyright © OPENTRONS, 2025. ALL RIGHTS RESERVED | ||
|
||
nav: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tended to put nav near the top of the YAML file, but it clearly doesn't matter.
docs/stacker-manual/docs/.gitignore
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can remove this, should be covered by the main docs/.gitignore
.
|
||
 | ||
|
||
The The following table lists and describes the function of each cable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👯
The The following table lists and describes the function of each cable. | |
The following table lists and describes the function of each cable. |
docs/stacker-manual/docs/index.md
Outdated
@@ -0,0 +1,30 @@ | |||
<a href="https://opentrons.com/"> | |||
<img src="/images/tm-opentrons-flex.png" alt="flex-tm" style="width:70%"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't spot this on my first pass through, but these URLs should not have leading slashes. That makes them absolute URLs, which will break in just about any deployment scenario. For example, if this image is meant to be at docs.opentrons.com/stacker-manual/images/tm-opentrons-flex.jpg
this would instead point to docs.opentrons.com/images/tm-opentrons-flex.png
, which wouldn't exist. Start with ../
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's what I did in a first draft, used ../
However, that didn't work, didn't render the image in a local build while just /
did work. But now ../
works so, reasons I guess?
…entrons into docs-stacker-manual
Mostly markdown, CSS, and HTML refactoring.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Making changes in a new push.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shortening the file names. Dropping stacker-
.
!!!warning | ||
Changes or modifications to this module not expressly approved by Opentrons could void the user’s authority to operate the equipment. This device complies with part 15 of the FCC Rules. | ||
|
||
!!!note | ||
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide a reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at their own expense. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed call-out text. Instead, the FCC warning and note will be H4s under the FCC H3.
They won't appear in the page-level TOC as toc-depth: 3
, but the FCC section will.
|
||
Le présent produit est conforme aux spécifications techniques applicables d’Innovation, Sciences et Développement économique Canada. | ||
|
||
CISPR 11 Class A |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make H4
|
||
CISPR 11 Class A | ||
|
||
!!!caution |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed admonition in favor of Caution as part of the text.
|
||
#### WEEE Policy | ||
|
||
Opentrons is dedicated to adhering to the EU Directive on Waste Electrical and Electronic Equipment (WEEE – 2012/19/EU). Our goal is to ensure that our products are properly disposed of or recycled once they reach the end of their useful life. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixing to use em, but keeping vertical-align
so icon stays centered with line of text.
|
||
After your Stacker is attached to the deck and powered on, instructions and animated images on the touchscreen take you through a guided setup. | ||
|
||
<img src="/images/touchscreen-map.png" alt="deck map" class="center-image" style="width:80%;"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing style="width:80%;"
No CSS in this one. The border is part of the image. For next time, CSS FTW.
|
||
<img src="/images/touchscreen-map.png" alt="deck map" class="center-image" style="width:80%;"> | ||
|
||
Because you can install a Stacker anywhere in column 4, and connect it to any port on the power/data hub, the touchscreen setup process gives you the opportunity to tell Flex where this module is on the deck. See [Post-Installation Procedures](stacker-postinstall.md#). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The #
is valid, but redundant. Will remove.
 | ||
|
||
## Stacker Box Parts | ||
|
||
The Stacker is packaged separately from the User Kit and ships with its own set of parts. The Stacker box contains the following items: | ||
|
||
 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will completely redo this set of image. The numbers refer to different versions of trying to get the images to look right. As separate images and using CSS, these should look better.
<th>Stacker status</th> | ||
</tr> | ||
<tr> | ||
<td><span class="my-dot white"></span> White</td> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's try status-dot
?
<figure class="general" style="margin-top: 150px;"> | ||
<img src="/images/tm-opentrons-full-blackcolor.svg" alt="opentrons-logo" style="width: 60%;"> | ||
<figcaption> | ||
<p><b>Post-sales & contacting Opentrons</b></p> | ||
<p>If you have any questions about the use of the system,<br> | ||
abnormal phenomena, or special needs, please contact:<br> | ||
<a href="mailto:[email protected]">[email protected]</a>. Also visit <a href="https://www.opentrons.com">www.opentrons.com.</a></p> | ||
</figcaption> | ||
</figure> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Less wonky with a CSS fix. Will commit shortly.
Committing Stacker instruction manual files.
Mostly markdown, CSS, and HTML refactoring.
309432a
to
7356731
Compare
…entrons into docs-stacker-manual
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Made changes and pushed revisions.
Committing Stacker instruction manual files.
Overview
This is the Stacker instruction manual.
Test Plan and Hands on Testing
Will review the text for the usual style, grammar, and the usual writing stuff. Also, check to make sure links work and images appear as expected. This doesn't have some of the recent CSS, but posting it up anyway to get started.
Changelog
No changes. This is new content.
Review requests
Nothing specific. Please review and comment.
Risk assessment
Low to medium as this is a new docs feature. Who knows what horrors may lurk within.