# Slicer training page

**URL:** <https://discourse.slicer.org/t/slicer-training-page/32513>\
**Category:** Forum and website feedback\
**Created:** [October 31, 2023, 8:14pm UTC](https://discourse.slicer.org/t/slicer-training-page/32513 "2023-10-31T20:14:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [October 31, 2023, 8:14pm UTC](https://discourse.slicer.org/t/slicer-training-page/32513/1 "2023-10-31T20:14:30Z")

</div>

The [Slicer training page](https://www.slicer.org/wiki/Documentation/Nightly/Training) has been seriously outdated in the past several years, in content (most content is very old), functionality (hard to find what is applicable to current Slicer version; users cannot edit the page), and look&feel.

Where should we move the page where all these issues can be fixed?

- Slicer source code repository: all other documentation is managed there, versioning would be automatically synchronized with the application, all the infrastructure for publishing, preview, etc. are already set up
- Separate github repository: it could be managed separately from the application development, updates would not add noise to the code repository; we could use different template/style than the main Slicer documentation
- Some other solutions… in essence, we would need to present a table (each row containing title, authors, description, keywords, creation/update date, Slicer version, thumbnail, URL) in some pretty, configurable way (e.g., sort and filter would be nice)

@spujol @pieper @jcfr @Sam_Horvath

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [October 31, 2023, 9:08pm UTC](https://discourse.slicer.org/t/slicer-training-page/32513/2 "2023-10-31T21:08:25Z")

</div>

> present a table (each row containing title, authors, description, keywords, creation/update date, Slicer version, thumbnail, URL) in some pretty, configurable way

We could add such a page to the `slicer.org`\[1\] where we would also describe our approach to training, provide some history, list past training events, …

For reference, associated Slicer issue is [#6676](https://github.com/Slicer/Slicer/issues/6676)

* * *

1. [https://github.com/slicer/slicer.org](https://github.com/slicer/slicer.org)

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [October 31, 2023, 9:11pm UTC](https://discourse.slicer.org/t/slicer-training-page/32513/3 "2023-10-31T21:11:13Z")

</div>

+1 for improving the training information.

Do people have examples of well organized training sites we could emulate?

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [November 1, 2023, 3:13am UTC](https://discourse.slicer.org/t/slicer-training-page/32513/4 "2023-11-01T03:13:14Z")

</div>

I like this style that Jc recommended: [GitHub - pyvideo/data: Python related videos and metadata powering PyVideo.](https://github.com/pyvideo/data/)