Built site for gh-pages

.nojekyll

@@ -1 +1 @@
-c5e97a84
+c51c1db1

approach/tooling.html

@@ -343,6 +343,7 @@ <h2 id="toc-title">On this page</h2>
   <ul class="collapse">
   <li><a href="#event-registration" id="toc-event-registration" class="nav-link" data-scroll-target="#event-registration">Event registration</a></li>
   <li><a href="#view-registrations-for-an-event" id="toc-view-registrations-for-an-event" class="nav-link" data-scroll-target="#view-registrations-for-an-event">View registrations for an event</a></li>
+  <li><a href="#resend-confirmation-emails-to-registrants" id="toc-resend-confirmation-emails-to-registrants" class="nav-link" data-scroll-target="#resend-confirmation-emails-to-registrants">Resend confirmation emails to registrants</a></li>
   <li><a href="#two-scenarios-for-sharing-audio-in-zoom" id="toc-two-scenarios-for-sharing-audio-in-zoom" class="nav-link" data-scroll-target="#two-scenarios-for-sharing-audio-in-zoom">Two scenarios for sharing audio in Zoom</a></li>
   </ul></li>
   <li><a href="#zotero" id="toc-zotero" class="nav-link" data-scroll-target="#zotero">Zotero</a></li>
@@ -634,17 +635,17 @@ <h3 class="anchored" data-anchor-id="event-registration">Event registration</h3>
 <li>Click Branding tab &gt; Logo: upload Openscapes hex; Banner: use a <a href="https://github.com/Openscapes/website-new/tree/main/images/banner_imgs">banner image</a> from the Openscapes website</li>
 <li>Click Email Settings tab &gt; Edit Confirmation Email to Registrants; use ‘Send me a preview email’ to check and iterate on the content</li>
 </ul>
-<div class="callout callout-style-default callout-caution callout-titled">
+<div class="callout callout-style-default callout-note callout-titled">
 <div class="callout-header d-flex align-content-center">
 <div class="callout-icon-container">
 <i class="callout-icon"></i>
 </div>
 <div class="callout-title-container flex-fill">
-Caution
+Note
 </div>
 </div>
 <div class="callout-body-container callout-body">
-<p>Each person who registers receives a unique URL for the Zoom meeting. Do not share that link, since every person using it will be signed in with one person’s name (ask us how we know ;-) ). Use ‘copy invitation’ to get a sharable link to the meeting e.g.&nbsp;to post last minute in Slack for a Community Call.</p>
+<p>Each person who registers receives a unique URL for the Zoom meeting. Do not share that link, since every person using it will be signed in with one person’s name (ask us how we know ;-) ). The root of that link is the generic url anyone can use to join e.g.&nbsp;a speaker who did not have to register, or to post last minute in Slack for a Community Call.</p>
 </div>
 </div>
 </section>
@@ -663,6 +664,11 @@ <h3 class="anchored" data-anchor-id="view-registrations-for-an-event">View regis
 <li><p>Click Download</p></li>
 </ul>
 </section>
+<section id="resend-confirmation-emails-to-registrants" class="level3">
+<h3 class="anchored" data-anchor-id="resend-confirmation-emails-to-registrants">Resend confirmation emails to registrants</h3>
+<p>Imagine people have registered and received their confirmation email with their unique Zoom link weeks in advance of your event. When it’s time to join, how do they find the link?</p>
+<p>This must be done manually for every registrant. In Zoom web portal &gt; Meetings &gt; your meeting &gt; Registration &gt; Manage Registrants &gt; View &gt; click name &gt; Resend Confirmation Email button. (see also <a href="https://support.zoom.com/hc/en/article?id=zm_kb&amp;sysparm_article=KB0068036">Zoom Support article</a>)</p>
+</section>
 <section id="two-scenarios-for-sharing-audio-in-zoom" class="level3">
 <h3 class="anchored" data-anchor-id="two-scenarios-for-sharing-audio-in-zoom">Two scenarios for sharing audio in Zoom</h3>
 <p>This Zoom resource covers two scenarios we use: <a href="https://support.zoom.us/hc/en-us/articles/201362643-Sharing-computer-sound-in-a-screen-share">Sharing computer sound in a screen share</a>. Screenshots below. Practice both beforehand, testing by recording yourself, because they’re not obvious and chances of working smoothly on the fly in a meeting are …low.</p>

search.json

@@ -767,7 +767,7 @@
     "href": "approach/tooling.html#zoom",
     "title": "Tooling",
     "section": "Zoom",
-    "text": "Zoom\nWe use Zoom as our primary meeting tool and for registrations for events that will be held via Zoom, such as Community Calls and the Pathways to Open Science series. Below are instructions for event registration, and for sharing audio in a Zoom meeting.\n\nEvent registration\nWe can set up registration for a single event like a Community Call, or for a series like Pathways to Open Science.\n\nCreate a meeting. Check ✔️ ‘Recurring meeting’ for a series.\nCheck Registration ✔️ Required > ✔️ Attendees register once and can attend any of the occurrences\nOptions > Show > Alternative Hosts: add someone else who has Openscapes Zoom license\nSave\nThe ‘Registration Link’ is the URL we add to an event page.\nSee Registration tab; defaults are ok\nClick Branding tab > Logo: upload Openscapes hex; Banner: use a banner image from the Openscapes website\nClick Email Settings tab > Edit Confirmation Email to Registrants; use ‘Send me a preview email’ to check and iterate on the content\n\n\n\n\n\n\n\nCaution\n\n\n\nEach person who registers receives a unique URL for the Zoom meeting. Do not share that link, since every person using it will be signed in with one person’s name (ask us how we know ;-) ). Use ‘copy invitation’ to get a sharable link to the meeting e.g. to post last minute in Slack for a Community Call.\n\n\n\n\nView registrations for an event\nView a list of registrants. No option to export the list here.\n\nMeetings > select a meeting (click title/date, not Edit)\nRegistration tab > Manage Registrants > click View\n\nExport a csv file of registrants\nThis one is not intuitive. H/T Emily Anderson of Coiled.\n\nAccount Management (near bottom of left nav bar) > Reports > Meeting\nEnter date of event, Select Registration Report > ✔️ Check event > Click Generate\nClick Download\n\n\n\nTwo scenarios for sharing audio in Zoom\nThis Zoom resource covers two scenarios we use: Sharing computer sound in a screen share. Screenshots below. Practice both beforehand, testing by recording yourself, because they’re not obvious and chances of working smoothly on the fly in a meeting are …low.\nScenario 1. During start of meeting, sharing welcome slides in a loop, with music from spotify playing so audience can hear, and people speaking does not disrupt music. See How to share audio with shared visuals.\n\nScenario 2. During interludes where people are silent journaling, to share audio only, not screen. See How to play audio or music without sharing your screen.\n\nIMPT: volume of shared sound is controlled in the source application. If spotify music is too loud, control volume in spotify (not your computer). See How to control the volume of a shared sound while in a meeting"
+    "text": "Zoom\nWe use Zoom as our primary meeting tool and for registrations for events that will be held via Zoom, such as Community Calls and the Pathways to Open Science series. Below are instructions for event registration, and for sharing audio in a Zoom meeting.\n\nEvent registration\nWe can set up registration for a single event like a Community Call, or for a series like Pathways to Open Science.\n\nCreate a meeting. Check ✔️ ‘Recurring meeting’ for a series.\nCheck Registration ✔️ Required > ✔️ Attendees register once and can attend any of the occurrences\nOptions > Show > Alternative Hosts: add someone else who has Openscapes Zoom license\nSave\nThe ‘Registration Link’ is the URL we add to an event page.\nSee Registration tab; defaults are ok\nClick Branding tab > Logo: upload Openscapes hex; Banner: use a banner image from the Openscapes website\nClick Email Settings tab > Edit Confirmation Email to Registrants; use ‘Send me a preview email’ to check and iterate on the content\n\n\n\n\n\n\n\nNote\n\n\n\nEach person who registers receives a unique URL for the Zoom meeting. Do not share that link, since every person using it will be signed in with one person’s name (ask us how we know ;-) ). The root of that link is the generic url anyone can use to join e.g. a speaker who did not have to register, or to post last minute in Slack for a Community Call.\n\n\n\n\nView registrations for an event\nView a list of registrants. No option to export the list here.\n\nMeetings > select a meeting (click title/date, not Edit)\nRegistration tab > Manage Registrants > click View\n\nExport a csv file of registrants\nThis one is not intuitive. H/T Emily Anderson of Coiled.\n\nAccount Management (near bottom of left nav bar) > Reports > Meeting\nEnter date of event, Select Registration Report > ✔️ Check event > Click Generate\nClick Download\n\n\n\nResend confirmation emails to registrants\nImagine people have registered and received their confirmation email with their unique Zoom link weeks in advance of your event. When it’s time to join, how do they find the link?\nThis must be done manually for every registrant. In Zoom web portal > Meetings > your meeting > Registration > Manage Registrants > View > click name > Resend Confirmation Email button. (see also Zoom Support article)\n\n\nTwo scenarios for sharing audio in Zoom\nThis Zoom resource covers two scenarios we use: Sharing computer sound in a screen share. Screenshots below. Practice both beforehand, testing by recording yourself, because they’re not obvious and chances of working smoothly on the fly in a meeting are …low.\nScenario 1. During start of meeting, sharing welcome slides in a loop, with music from spotify playing so audience can hear, and people speaking does not disrupt music. See How to share audio with shared visuals.\n\nScenario 2. During interludes where people are silent journaling, to share audio only, not screen. See How to play audio or music without sharing your screen.\n\nIMPT: volume of shared sound is controlled in the source application. If spotify music is too loud, control volume in spotify (not your computer). See How to control the volume of a shared sound while in a meeting"
   },
   {
     "objectID": "approach/tooling.html#zotero",

sitemap.xml

@@ -2,118 +2,118 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>https://openscapes.github.io/approach-guide/mentors-framework/onboarding.html</loc>
-    <lastmod>2023-12-19T18:16:43.000Z</lastmod>
+    <lastmod>2024-01-19T18:07:19.372Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/mentors-framework/index.html</loc>
-    <lastmod>2023-12-19T18:16:42.140Z</lastmod>
+    <lastmod>2024-01-19T18:07:18.500Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/contributing/resources.html</loc>
-    <lastmod>2023-12-19T18:16:41.376Z</lastmod>
+    <lastmod>2024-01-19T18:07:17.544Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/contributing/inspiration.html</loc>
-    <lastmod>2023-12-19T18:16:40.796Z</lastmod>
+    <lastmod>2024-01-19T18:07:16.952Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/contributing/setup.html</loc>
-    <lastmod>2023-12-19T18:16:39.960Z</lastmod>
+    <lastmod>2024-01-19T18:07:16.100Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/partners.html</loc>
-    <lastmod>2023-12-19T18:16:39.292Z</lastmod>
+    <lastmod>2024-01-19T18:07:15.416Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/calendar.html</loc>
-    <lastmod>2023-12-19T18:16:38.360Z</lastmod>
+    <lastmod>2024-01-19T18:07:14.516Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/index.html</loc>
-    <lastmod>2023-12-19T18:16:37.716Z</lastmod>
+    <lastmod>2024-01-19T18:07:13.876Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/seaside-chats.html</loc>
-    <lastmod>2023-12-19T18:16:36.944Z</lastmod>
+    <lastmod>2024-01-19T18:07:13.080Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/code-of-conduct.html</loc>
-    <lastmod>2023-12-19T18:16:35.480Z</lastmod>
+    <lastmod>2024-01-19T18:07:11.548Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/pre-cohort-tech.html</loc>
-    <lastmod>2023-12-19T18:16:34.620Z</lastmod>
+    <lastmod>2024-01-19T18:07:10.684Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/leading-cohort-calls.html</loc>
-    <lastmod>2023-12-19T18:16:33.240Z</lastmod>
+    <lastmod>2024-01-19T18:07:09.288Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/pre-cohort-engage.html</loc>
-    <lastmod>2023-12-19T18:16:32.108Z</lastmod>
+    <lastmod>2024-01-19T18:07:08.120Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/cohort-planning.html</loc>
-    <lastmod>2023-12-19T18:16:30.580Z</lastmod>
+    <lastmod>2024-01-19T18:07:06.588Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/about.html</loc>
-    <lastmod>2023-12-19T18:16:29.212Z</lastmod>
+    <lastmod>2024-01-19T18:07:05.208Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/index.html</loc>
-    <lastmod>2023-12-19T18:16:30.196Z</lastmod>
+    <lastmod>2024-01-19T18:07:06.200Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/design.html</loc>
-    <lastmod>2023-12-19T18:16:31.000Z</lastmod>
+    <lastmod>2024-01-19T18:07:06.996Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/lessons.html</loc>
-    <lastmod>2023-12-19T18:16:32.468Z</lastmod>
+    <lastmod>2024-01-19T18:07:08.492Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/post-cohort-followup.html</loc>
-    <lastmod>2023-12-19T18:16:33.660Z</lastmod>
+    <lastmod>2024-01-19T18:07:09.700Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/index.html</loc>
-    <lastmod>2023-12-19T18:16:35.064Z</lastmod>
+    <lastmod>2024-01-19T18:07:11.128Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/tooling.html</loc>
-    <lastmod>2023-12-19T18:16:36.404Z</lastmod>
+    <lastmod>2024-01-19T18:07:12.528Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/documentation.html</loc>
-    <lastmod>2023-12-19T18:16:37.332Z</lastmod>
+    <lastmod>2024-01-19T18:07:13.484Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/onboarding.html</loc>
-    <lastmod>2023-12-19T18:16:38.088Z</lastmod>
+    <lastmod>2024-01-19T18:07:14.244Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/qual-assessment.html</loc>
-    <lastmod>2023-12-19T18:16:38.972Z</lastmod>
+    <lastmod>2024-01-19T18:07:15.112Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/LICENSE.html</loc>
-    <lastmod>2023-12-19T18:16:39.652Z</lastmod>
+    <lastmod>2024-01-19T18:07:15.796Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/contributing/index.html</loc>
-    <lastmod>2023-12-19T18:16:40.264Z</lastmod>
+    <lastmod>2024-01-19T18:07:16.416Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/contributing/workflow.html</loc>
-    <lastmod>2023-12-19T18:16:41.092Z</lastmod>
+    <lastmod>2024-01-19T18:07:17.252Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/mentors-framework/nasa-openscapes.html</loc>
-    <lastmod>2023-12-19T18:16:41.836Z</lastmod>
+    <lastmod>2024-01-19T18:07:18.196Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/mentors-framework/engage.html</loc>
-    <lastmod>2023-12-19T18:16:42.432Z</lastmod>
+    <lastmod>2024-01-19T18:07:18.792Z</lastmod>
   </url>
 </urlset>