<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type"/>
</head>
<body style="height: 100% !important; width: 100% !important; background-color: #F7F9FA; margin: 0; padding: 0;">
<!-- Preheader -->
<table border="0" cellpadding="0" cellspacing="0" align="center" style="font-family:Arial,Helvetica,sans-serif;font-size: 13px;color:#131619;background-color: #F7F9FA; width: 100%; height: 100%;padding-bottom: 10px;">
<tr>
<td style="vertical-align: top">
<table border="0" cellpadding="0" cellspacing="0" align="center" style="width:700px;">
<tr>
<td style="vertical-align: top;padding: 0px; background-color: #f4f5f9">
<table border="0" cellpadding="0" cellspacing="0" align="center"
style="margin-left: 0px;margin-right: 0px;width: 100%;background-color: #ffffff;padding-bottom: 37px;">
<!-- email header -->
<tr>
<td style="padding-top: 28px;padding-bottom: 28px;padding-left:32px;background-color:#0B5CFF;text-align: left;">
<a href= "https://zoom.com">
<img src="https://click.zoom.us/l/84442/2022-12-29/c4ns1t/84442/1672332921RKagdau8/Logo_white_2022.png" style="border-style: solid;" width="110" height="25" border="0"/>
</a>
</td>
</tr>
<!-- email body -->
<tr>
<td style="padding-left: 32px;padding-right: 32px;">
<table border="0" cellpadding="0" cellspacing="0" align="center"
style="width: 100%;font-size: 16px;color:#131619;">
</table>
<table border="0" cellpadding="0" cellspacing="0" style="width: 100%; height: 100%;">
<tbody>
<tr style="height: 24px;"></tr>
<tr>
<td colspan="2">
<table border="0" cellpadding="0" cellspacing="0" align="left" style="padding-top: 5px;padding-bottom: 5px;width: 100%;font-size: 13px;color: #39394d;font-family: Arial;background: #F2F2F4;">
<tr>
<td align="left" width="55" style="width: 55px;mso-line-height-rule: exactly; line-height: 30px;vertical-align:top;padding: 7px 12px 10px 12px">
<img width="55" height="25" src="https://st3.zoom.us/static/6.3.33335/image/summary/summary_new_logo_v2.png" style="width: 55px; height: 25px; border-width: 0; border-style: solid;vertical-align: bottom;" />
</td>
<td align="left" style="text-align: left; font-size: 13px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: middle;">
Meeting summary with AI Companion now supports additional languages in preview.
</td>
<td align="left" width="80" style="width: 80px;text-align: left; font-size: 13px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: middle;">
<a style="display: inline-block;color: #0B5CFF;text-decoration: none;font-weight: 600" href="https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0058013#languages">Learn More</a>
</td>
</tr>
</table>
</td>
</tr>
<tr style="height: 24px;"></tr>
<tr>
<td colspan="2" style="font-size: 19px;color: #131619;font-family: Arial,Helvetica,sans-serif;line-height: 25px;font-weight: 700;">
<table border="0" cellpadding="0" cellspacing="0" align="center" style="width: 100%;font-size: 19px;color: #39394d;font-family: Arial;">
<tr>
<td align="left" style="padding-right: 24px;mso-line-height-rule: exactly; line-height: 25px;text-align:left;font-size:19px;color:#39394d;font-family:Arial,Helvetica,sans-serif;vertical-align:top">
<strong>Meeting summary for Monthly Documentation Meeting (04/09/2025)</strong>
</td>
</tr>
</table>
</td>
</tr>
<tr style="height: 32px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Quick recap</strong>
</td>
</tr>
<tr style="height: 6px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
The team discussed the organization and design of the training page, including the need for better direction for users and the possibility of renaming certain sections for clarity. They also explored the integration of Jupyter notebooks into their user guide for open seas, acknowledging both the benefits and limitations of this approach. Lastly, they discussed the use of Jupyter notebooks for training materials, the process of creating a user guide, and the need for an index or map to organize their various projects.
</td>
</tr>
<tr style="height: 32px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Next steps</strong>
</td>
</tr>
<tr style="height: 6px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Wes to follow up with Krishna regarding the output of the training repos he developed and the location of any mystery Make docs.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Hedda and Wes to review the content of the Jupiter books found by Wes.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Scott and Krishna to better inform the team about the what and why of using Jupiter books for training materials.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Team to create an index or map of all existing training materials, including those from Scott and Krishna, and Silvia's work.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Team to decide on organization and presentation of training materials to users, considering how to group different types of content.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Silvia to reach out to Hedda for brainstorming on how to organize and present her training materials.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Team to review and discuss the organization of training materials at the next meeting.
</td>
</tr>
<tr>
<td colspan="2" style="font-size:14px;line-height:32px;color:#dedede;border-bottom: 1px solid #dedede;padding-top:22px;">
</td>
</tr>
<tr>
<td colspan="2" style="font-size:14px;line-height:32px;padding-top: 22px;">
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Summary</strong>
</td>
</tr>
<tr style="height: 6px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Training Page Link Redirect Issues</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Wesley demonstrated the training page, which includes a link to the user guide and a list of repositories. However, the team encountered issues with the links, as they were not redirecting to the expected repositories. Ellen suggested reaching out to Krishna for clarification, as he had previously mentioned migrating the training repositories. The team agreed to assume that Krishna would answer their questions and provide the necessary documentation.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Improving Training Page Design and Resources</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
In the meeting, Hedda discussed the need to improve the design of the training page, suggesting the addition of more cards and better direction for users. Ellen proposed renaming the 'training repo' to 'training resources' for clarity. The team agreed to link training resources to specific repositories for better user experience. Silvia suggested adding a link to the bottom of the open seas documentation for training resources. The team also discussed the need for a single place for all training resources, rather than having them scattered across different sections.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Organizing OpenSees Training and Documentation</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
The team discusses the organization of training materials and documentation for OpenSees. They agree that training materials should be separate from documentation, with training focused on webinars, courses, and reusable content that evolves over time. Documentation should include user guides and how-to information. Silvia shows her work-in-progress documentation, which includes short video clips and instructions. The group decides that these elements need to be categorized as either documentation or training, and placed in the appropriate section. They also discuss the need for consistent styling and layout across all materials. The team plans to add links to training resources in the OpenSees overview section, alongside documentation and external resources.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Jupyter Books for Training Repository</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Wesley discovers commands to generate and display the Jupyter books at the specified URL, though they don't currently exist. Silvia questions the choice of Jupyter books over Markdown, and Tim explains that Scott and Krishna recommended this approach for the training repository. Hedda suggests first examining the existing content before discussing with Scott and Krishna about organization and potential integration with current systems. The team acknowledges the need to consolidate all training materials in one place, considering the varying complexity of different training sessions.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Jupiter Notebooks Integration in User Guide</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Wesley, Silvia, and Hedda discussed the integration of Jupiter notebooks into their user guide for open seas. They acknowledged the benefits of this integration, such as the ability to create interactive content and the potential for sustainability. However, they also recognized the limitations, particularly the ephemeral nature of Jupiter notebooks and the difficulty in moving the content to other platforms. They agreed on the need to define a clear line for their users to understand where to look for different things. Silvia expressed her preference for static documentation with active content, while Wesley highlighted the challenges of copying and pasting the content due to its JSON data format.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Integrating Jupyter Notebooks With Training Materials</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
The team discussed the use of Jupyter notebooks for training materials, particularly for OpenSeas and ADCIRC. Silvia expressed concerns about integrating these materials into Jupyter notebooks, as they involve teaching users about the Designsafe/Tack infrastructure and running OpenSeas in different ways. Tim clarified that the intent was to use Jupyter notebooks for training webinars and in-person events, not for all documentation. Silvia suggested creating templates for different training materials and linking them in the community folder. The team agreed to further explore the integration of Jupyter notebooks with OpenSeas and ADCIRC, and to visualize examples to better understand the commonalities and flow between different training materials.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>User Guide Creation and Indexing</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
In the meeting, Silvia discussed her process of creating a user guide, which involved spending a lot of time on a Jupyter notebook and then switching to Markdown for sustainability. The team agreed on the need for an index or map to organize their various projects and present them to users. They also discussed the possibility of housing different types of content in different spaces. The team decided to continue this discussion in the next meeting.
</td>
</tr>
<tr style="height: 32px;"></tr>
<tr>
<td colspan="2" style="font-style: italic;font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
AI-generated content may be inaccurate or misleading. Always check for accuracy.
</td>
</tr>
<tr style="height: 32px;"></tr>
<tr>
<td>
<a href="https://DesignSafe-ci.zoom.us/user/meeting/summary?meetingId=gXqWYAC6QRu1TiB5zZsrew%3D%3D&summaryId=mss_iTW0qk91T_a8LQZAdkeUqA&fileId=XDH6CHEdRum4A0vSb82RhA" style="border: 1px solid #DFE3E8; padding: 6px 16px;border-radius:6px;color:#131619;text-decoration:none;font-weight: bold;">Edit</a>
</td>
<td style="text-align: right; font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top">
<table border="0" cellpadding="0" cellspacing="0" align="center"
style="width: 100%;font-size: 13px;color: #39394d;font-family: Arial;">
<tr>
<td align="right"
style="mso-line-height-rule: exactly; line-height: 30px;text-align:right;font-size:16px;color:#39394d;font-family:Arial,Helvetica,sans-serif;vertical-align:top;">
Please rate the accuracy of this summary.
</td>
<td align="left"
style="text-align: left; font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: middle;">
<a style="text-decoration:none;display: inline-block"
href="https://DesignSafe-ci.zoom.us/meeting/summary/feedback?meetingId=gXqWYAC6QRu1TiB5zZsrew%3D%3D&email=aG9zdDEwQGRlc2lnbnNhZmUtY2kub3Jn&feedback=good"> <img height="30" width="30"
src="https://st2.zoom.us/static/6.3.33335/image/summary/feedback_good.png"
style="width: 30px; height: 30px; border-width: 0; border-style: solid;"/> </a>
<a style="text-decoration:none;display: inline-block" href="https://DesignSafe-ci.zoom.us/meeting/summary/feedback?meetingId=gXqWYAC6QRu1TiB5zZsrew%3D%3D&email=aG9zdDEwQGRlc2lnbnNhZmUtY2kub3Jn&feedback=bad"> <img
height="30" width="30" src="https://st1.zoom.us/static/6.3.33335/image/summary/feedback_bad.png"
style="width: 30px; height: 30px; border-width: 0; border-style: solid;"/> </a>
</td>
</tr>
</table>
</td>
</tr>
</tbody>
</table>
<table>
<tr>
<td style="padding-top: 32px;font-size: 16px;line-height: 20px;">
Best,
</td>
</tr>
<tr>
<td style="font-size: 16px;line-height: 20px;padding-top: 10px;">
Zoom
</td>
</tr>
</table>
</td>
</tr>
<!-- email footer -->
<tr>
<td style="padding-top: 56px;background-color: #FFFFFF;">
<table align="center" border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td>
<a href="https://twitter.com/zoom" style="text-decoration: none;display: inline-block;">
<img alt="Twitter" border="0" height="32" src="https://click.zoom.us/l/84442/2019-12-26/bfs1bv/84442/140021/Social_Twitter_2020.png"
style="width: 32px; height: 32px; border-width: 0px; border-style: solid;"
/>
</a>
</td>
<td style="padding-left:16px; padding-right: 16px;">
<a href="https://www.linkedin.com/company/zoom-video-communications/"
style="text-decoration: none;display: inline-block;">
<img alt="LinkedIn" border="0" height="32" src="https://click.zoom.us/l/84442/2019-12-26/bfs1bs/84442/140023/Social_LinkedIn_2020.png"
style="width: 32px; height: 32px; border-width: 0px; border-style: solid;"
/>
</a>
</td>
<td>
<a href="https://blog.zoom.us/" style="text-decoration: none;display: inline-block;">
<img alt="Blog" border="0" height="32" src="https://click.zoom.us/l/84442/2019-12-26/bfs1bx/84442/140025/Social_Blog_2020.png"
style="width: 32px; height: 32px; border-width: 0px; border-style: solid;"
/>
</a>
</td>
</tr>
</tbody>
</table>
<table align="center" border="0" cellpadding="0" cellspacing="0" width="100%">
<tbody>
<tr>
<td style="font-size:12px; line-height:16px; color:#6E7680; text-align:center;padding-top: 16px;">+1.888.799.9666</td>
</tr>
<tr>
<td style="font-size:12px; line-height:16px; color:#6E7680; text-align:center;padding-top: 10px;">
©2025 Zoom Communications, Inc.
</td>
</tr>
<tr>
<td align="center" style="padding: 16px 0 0;font-size:12px;line-height:16px;color:#6E7680;" valign="top">
Visit <a href= "https://zoom.com" style="color:#6E7680" target="_blank">zoom.com</a>
</td>
</tr>
<tr>
<td align="center" style="padding: 4px 0 32px;font-size:12px;line-height:16px;color:#6E7680;" valign="top">
<a href="https://www.google.com/maps/place/55+Almaden+Blvd,+San+Jose,+CA+95113/@37.3328541,-121.897097,17z/data=!3m1!4b1!4m5!3m4!1s0x808fcca40adf3cb7:0x5a2d33d3593e0a33!8m2!3d37.3328541!4d-121.8949083" style="color:#969AA1; text-decoration: none;" target="_blank">
55 Almaden Blvd<br/>San Jose, CA 95113
</a>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</body>
</html>