Research/Software page is old and overlaps with Software section

[jcohenadad]

here: https://neuro.polymtl.ca/research/image-processing-software/README.html

it lists some features of SCT which are pretty old-- also, SCT is now listed in primary section software

i'm wondering if we should just get rid of this content at all...

pros to keep it:

• nice looking images-- inviting to the prospective student

cons:

• old material
• needs maintenance

[kousu]

Could we move the images from https://neuro.polymtl.ca/research/image-processing-software/template-of-the-spinal-cord.html to https://spinalcordtoolbox.com/overview/concepts/pam50.html, and the others into https://spinalcordtoolbox.com/overview/studies.html? Or is https://github.com/neuropoly/template/blob/master/README.md a more appropriate landing zone for those demo images?

We could also add a "Features" page to SCT where these images could live and link it prominently from the Software page:

---

https://neuro.polymtl.ca/research/data-scripts.html also overlaps with both of https://neuro.polymtl.ca/software.html and https://neuro.polymtl.ca/research/image-processing-software/README.html!

Let's split off "Data" to its own top-level page with a table matching Software, (and make sure it links to intranet and spine-generic?

[jcohenadad]

Could we move the images from https://neuro.polymtl.ca/research/image-processing-software/template-of-the-spinal-cord.html to https://spinalcordtoolbox.com/overview/concepts/pam50.html, and the others into https://spinalcordtoolbox.com/overview/studies.html? Or is https://github.com/neuropoly/template/blob/master/README.md a more appropriate landing zone for those demo images?

i'm not so sure about this... i don't want to necessarily add too much material (esp. if it's old/obsolete one). we need a proper brainstorming on this (not only me taking the decision)

Let's split off "Data" to its own top-level page with a table matching Software, (and make sure it links to intranet and spine-generic?

right... that sounds good i think. We also need to ensure that the git internal data management documentation is also accessible via the intranet