Based on recent and past discussions, it seems that CASS-organized and CASS-publicized events will be an important part of our web content. If we add key artifacts from the events, they can also serve as archives for the events.
Behind the scenes, some IDEAS event content has been used to automatically generate content to advertise events (particularly for the HPC Best Practices webinars) in other venues, as well as automatically formatting content for the BSSw.io site. Better Scientific Software tutorial events also do dual service, driving the website that archives the tutorial series (https://bssw-tutorial.github.io/). To the extent that individual SSOs might also use similar mechanisms (e.g., Jekyll) to build their websites, we can probably manage other reuse of event content across CASS members.
Based on recent and past discussions, it seems that CASS-organized and CASS-publicized events will be an important part of our web content. If we add key artifacts from the events, they can also serve as archives for the events.
The https://ideas-productivity.org/ website has a rich event capability (https://ideas-productivity.org/resources/events/), which I believe will largely address CASS's needs too, and can be easily adapted. Events are a a Jekyll collection (https://github.com/ideas-productivity/ideas-productivity.github.io/tree/main/_events) which with a structure that has already been used to represent a wide range of event types. A Jelyll layout (https://github.com/ideas-productivity/ideas-productivity.github.io/blob/main/_layouts/event.html) renders event pages, and several includes generate lists of events in various contexts (https://github.com/ideas-productivity/ideas-productivity.github.io/tree/main/_includes/_events). There are details that are specific to the styling used on the IDEAS website, but adaptation should not be hard.
Behind the scenes, some IDEAS event content has been used to automatically generate content to advertise events (particularly for the HPC Best Practices webinars) in other venues, as well as automatically formatting content for the BSSw.io site. Better Scientific Software tutorial events also do dual service, driving the website that archives the tutorial series (https://bssw-tutorial.github.io/). To the extent that individual SSOs might also use similar mechanisms (e.g., Jekyll) to build their websites, we can probably manage other reuse of event content across CASS members.