Add presentations docs section + previous and upcoming materials

[d33bs]

Description

This PR adds a presentations docs section + previous and upcoming materials. Along with this I'm seeking feedback on the upcoming talk slides for ParslFest 2025. Thanks for any input!

What is the nature of your change?

• Bug fix (fixes an issue).
• Enhancement (adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• This change requires a documentation update.

Checklist

Please ensure that all boxes are checked before indicating that a pull request is ready for review.

• I have read the CONTRIBUTING.md guidelines.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• New and existing unit tests pass locally with my changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have deleted all non-relevant text in this pull request template.

[gwaybio]

Great idea to get this section started!

[gwaybio]

oh, one additional question is if this should belong in the docs/ folder? Is it rendered in the RTD and that is the primary point for viewers? An alternative is to put it in a media/ folder, which may not necessarily get built in the RTD. I'm happy either way; just wanting to hear your thought process.

[d33bs]

oh, one additional question is if this should belong in the docs/ folder? Is it rendered in the RTD and that is the primary point for viewers? An alternative is to put it in a media/ folder, which may not necessarily get built in the RTD. I'm happy either way; just wanting to hear your thought process.

Thanks - great question on this! The docs/source/presentation folder doesn't get ported during the sphinx-build process and we needed to move this to _static for it to be properly used within the docs. In order for the presentation materials to display properly within an iframe they have to come from the same domain, so my feeling is that we should keep this under the docs for now until there's a reason to exclude it. It does add a little bloat to that branch, but not too much. Ideally in the future it'd be great to explore how to render dynamic frames from Zenodo directly (or perhaps an intermediary) so we don't need to duplicate the artifacts. Mostly I like the idea of seeing things in one spot to help tell our story and help users access things quickly.

[d33bs]

Thanks again @gwaybio ! Merging this in for now (will follow up with video link once available).