Some initial thoughts:

• If we do end up using the Nutshell extension, I'd recommend a top-level folder in site to the effect of nutshell and then naming the file/instruction with the contents instead of a floating unclear step-1.qmd etc.
• We might also want to change the whole instruction to a variable e.g.[:Log in to ValidMind](/nutshell/login.qmd#x-step-1).
• I was able to get the table to perform a bit better with some non-breaking spaces, but the solution isn't ideal...
• The little dots animation prefacing the "link" seems to be baked into the JS file, and I'm sure we could modify it (perhaps to 3 lines of defense, converging into a checkmark on hover...?) but it does seem sort of juvenile overall in contrast to the rest of the site.

Overall, after playing with it, and on consideration of "less links in the instructions and simpler is better for both author and user," I think I'd rather us resurrect a Log in to ValidMind guide that is linked in the Prerequisites section of each relevant page.

• For example, we have a "You are logged into the ValidMind Platform UI" list item already in some articles such as Collaborate with others. EDIT: It looks like this line was removed when we added the login page, but here is what it used to look like:

• This would greatly cut down on the loginloginlogin links on pages with many sets of instructions, and allow us to update one central page with less fuss re: login instructions.

Example option one	Example option two

I personally prefer option two, and that allows us to make it a simple variable instead of an include as well!

Closing — while we liked what Nutshell could do, it's not quite what we are looking for. This work will feed into a redesigned "Prerequisites" section as proposed by @validbeck instead.