Create consistent our-handbook style + instructions for contributors

[NatalieZelenka]

• Decide how to leave instructions for users of the handbook
  • @jatonline thought that we could use jb admonitions ("hints")
  • @NatalieThurlby was currently using html comments
  • Add this to contribution instructions
  • Figure out how they should be cleaned up
    • a script that will "tidy/clean" the template
    • CSS to make certain elements not render online - perhaps only added at the end
• Consistent wording of manager/PI/Group leader and team member/group member/student/etc
• How opinionated should the handbook be?
  • Provide different options where possible
• The handbook isn't a tutorial for things that are explained well elsewhere (e.g. Open Science), but it's a place where group leaders can make commitments about how they are going to run things (until they review them next). The template is a place where people can see the menu of different ways to run a group, and make a decision to choose something.

[jatonline]

Some ideas... It would be good to have a unified way of leaving 'notes' or guidance folks filling in the template handbook.

Use cases:

• It might be the first time they're filling in the template and they need some inspiration
• They might be revisiting a page after some time and would still find the notes helpful
• They might be working with a non-technical colleague that doesn't understand Markdown/MyST and so it would be helpful to render the notes in the built version of the book, so the colleague can help
• But it would be good if the notes could be switched off or hidden somehow, when the template is completed

[lauren-cadwallader]

I think it would be useful to have different types of instructions/hints so some are like "you need to do this" (a direct instruction) and others are like "you might be able to find this information from your Research Office" (a hint to make things better/easier).

[jatonline]

Where we have separate instructions for authors editing the handbook in their web browser or on their local machine, we could also suggest the use of tabs to split each set of instructions (see #53)