# Its all about transitions! Lets talk about Slicer's landing page

**URL:** <https://discourse.slicer.org/t/its-all-about-transitions-lets-talk-about-slicers-landing-page/113>\
**Category:** Development\
**Created:** [April 13, 2017, 8:03pm UTC](https://discourse.slicer.org/t/its-all-about-transitions-lets-talk-about-slicers-landing-page/113 "2017-04-13T20:03:19Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![bpaniagua](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/bpaniagua/32/20_2.png) [@bpaniagua](https://discourse.slicer.org/u/bpaniagua)\
**Post date:** [September 18, 2017, 8:29pm UTC](https://discourse.slicer.org/t/its-all-about-transitions-lets-talk-about-slicers-landing-page/113/28 "2017-09-18T20:29:42Z")

</div>

I believe we discussed this over [Project Week](https://na-mic.org/wiki/2017_Winter_Project_Week/Organizations) thinking it is not really about the dissemination mechanism (custom packages vs extensions), but about having a start-to-end software solution that serves a very specific research community. These communities can be either methodological (i.e. salt, dmri) or clinical (i.e. IGT, CIP).

The problem here is that we might be getting a bit tangled on the syntax/branding of what we are trying to provide more presence to. Maybe “SlicerDistributions” refers too much to the dissemination vehicle. I believe it will benefit everybody to present these specialized solutions within Slicer to our user-base 1) because it might attract specialized researchers to the Slicer community 2) because it showcases the real power of Slicer to be customized to a number of different applications.

@ljod @rkikinis @jcfr anything to add to this opinion?

---

_[View the full topic](https://discourse.slicer.org/t/its-all-about-transitions-lets-talk-about-slicers-landing-page/113)._