<div dir="ltr">Yeah, I'm also -1 on flask. <div><br></div><div>Seems like you would have to build from scratch a static webpage generator out of a system that really isn't meant to be a static webpage generator, while never needing/using what flask is actually for. </div><div><br><div><div class="gmail_extra">My preference in order: </div><div class="gmail_extra"><br></div><div class="gmail_extra">* Jekyll - the tool built specifically for serving up github pages. That's basically the negative of the above argument against flask. In contrast to all the other options, this provides continuous integration for building the webpages. Requires zero installation to contribute. </div><div class="gmail_extra">* Pelican - also up to the job, but requires that someone build the website locally on their machine every time a change is made. Requires people learn a new system (at least those that aren't already building their own blogs with this), but hey, at least it's written in Python. </div><div class="gmail_extra">* Sphinx - has the advantage that it's already being used by all the projects in the eco-system. The advantage of familiarity is balanced by general finickiness, that we have all grown to tolerate. Also, I am not sure what we'd need to do to create a mobile-responsive website, while both Pelican and Jekyll do that out of the box. </div><div class="gmail_extra"><br></div><div class="gmail_extra">In my opinion the best solution would be a Jekyll-backed webpage with the layout and design of the page that Vanessa created. </div><div class="gmail_extra"><br></div><div class="gmail_extra">Cheers, </div><div class="gmail_extra"><br></div><div class="gmail_extra">Ariel </div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_quote">On Mon, Aug 3, 2015 at 10:14 AM, Gael Varoquaux <span dir="ltr"><<a href="mailto:gael.varoquaux@normalesup.org" target="_blank">gael.varoquaux@normalesup.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-1 on flask: it's twisting something that not been built for this<br>
purpose.<br>
<br>
My votes in order of preference (note that my opinion doesn't matter<br>
much, as I won't be doing the work):<br>
<br>
* sphinx: every package of the nipy constellation already uses it<br>
* pelican: I have a great experience with it (using purecss that's much<br>
lighter than bootstrap, check my personnal website out)<br>
* jekyll: seems reasonnably easy to use, but will require most people to<br>
learn a new development ecosystem<br>
* flask: great project to serve dynamic websites, but not designed for<br>
static.<br>
<br>
Gael<br>
<div><div><br>
On Mon, Aug 03, 2015 at 06:38:05AM -0700, vanessa sochat wrote:<br>
> My .02 on flask:<br>
<br>
> The extra step is "freezing." The workflow to push an update will always be<br>
> something along the lines of:<br>
<br>
> - checkout or clone current flask site<br>
> - do changes<br>
> - freeze<br>
> - push to gh-pages<br>
<br>
> This seems do-able to me, but I sense that others aren't happy about the extra<br>
> step, and I am open to the idea that other frameworks could do it better,<br>
> perhaps at the cost of the more "interactive" back end allowed by flask. At the<br>
> end of the day, it doesn't really matter so much as long as updating / adding<br>
> content is relatively straight forward and pain free. Looking forward to more<br>
> discussion on this.<br>
<br>
> On Mon, Aug 3, 2015 at 6:33 AM, vanessa sochat <<a href="mailto:vsochat@stanford.edu" target="_blank">vsochat@stanford.edu</a>> wrote:<br>
<br>
> This week we should perhaps vote/decide on a final framework to port the<br>
> nipy site into? I'm open to giving a go at whatever the group thinks is<br>
> best :)<br>
<br>
> On Mon, Aug 3, 2015 at 6:11 AM, Ariel Rokem <<a href="mailto:arokem@gmail.com" target="_blank">arokem@gmail.com</a>> wrote:<br>
<br>
<br>
> On Wed, Jul 29, 2015 at 8:38 PM, David Moreno-Dominguez <<br>
> <a href="mailto:d.mor.dom@gmail.com" target="_blank">d.mor.dom@gmail.com</a>> wrote:<br>
<br>
> Doesnt Dipy already do this? (be open source and compute FA images<br>
> [and much more] from any dwi dataset)<br>
<br>
<br>
> Absolutely - I was being ironic. <br>
<br>
> But I will admit that irony doesn't travel well by email. <br>
> <br>
<br>
> On Wed, Jul 29, 2015 at 8:06 PM, Ariel Rokem <<a href="mailto:arokem@gmail.com" target="_blank">arokem@gmail.com</a>><br>
> wrote:<br>
<br>
> > On Mon, Jul 27, 2015 at 10:44 AM, Gael Varoquaux<br>
> > <<a href="mailto:gael.varoquaux@normalesup.org" target="_blank">gael.varoquaux@normalesup.org</a>> wrote:<br>
<br>
> >> On Mon, Jul 27, 2015 at 08:56:08AM -0700, Ariel Rokem wrote:<br>
> >> > PS: Vanessa: Nilearn is not only for fMRI. It's for<br>
> statistical<br>
> >> > analysis<br>
> >> > of images. It is also used for anatomical images:<br>
> >> > <a href="http://nilearn.github.io/auto_examples/decoding/" rel="noreferrer" target="_blank">http://nilearn.github.io/auto_examples/decoding/</a><br>
> plot_oasis_vbm.html<br>
> >> > If we could get a preprocessed, openly downloadable set of<br>
> images of<br>
> >> > eg<br>
> >> > FA, we would do an example with diffusion too.<br>
<br>
> >> > Completely off-topic, but I can't resist: if only there was an<br>
> >> > open-source project that computed FA images from freely<br>
> available<br>
> >> > diffusion MRI data-sets!<br>
<br>
> >> Well, you're welcome to help us with preprocessing and pitching<br>
> a<br>
> >> relevant prediction problem from this data. I know nothing about<br>
> >> diffusion and nothing about the datasets you are talking about.<br>
> In my<br>
> >> experience, writing a relevant example requires understanding<br>
> the data<br>
> >> and the questions. If you, or someone else, gets us to the point<br>
> where<br>
> >> there is a set of nifti images of FA with condition A and<br>
> condition B,<br>
> >> and helps us write the story, than we have an example.<br>
<br>
<br>
> > Hmm. Interesting idea. I am looking around for something along<br>
> these lines.<br>
> > I think that there are some freely available data-sets that are<br>
> already<br>
> > preprocessed, so could be used in this way. Let me think about<br>
> how to go<br>
> > about this.<br>
<br>
<br>
> >> Gaël<br>
> >> _______________________________________________<br>
> >> Neuroimaging mailing list<br>
> >> <a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
> >> <a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br>
<br>
<br>
> > _______________________________________________<br>
> > Neuroimaging mailing list<br>
> > <a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
> > <a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br>
> _______________________________________________<br>
> Neuroimaging mailing list<br>
> <a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
> <a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br>
<br>
<br>
> _______________________________________________<br>
> Neuroimaging mailing list<br>
> <a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
> <a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
--<br>
</div></div><span><font color="#888888"> Gael Varoquaux<br>
Researcher, INRIA Parietal<br>
NeuroSpin/CEA Saclay , Bat 145, 91191 Gif-sur-Yvette France<br>
Phone: <a href="tel:%2B%2B%2033-1-69-08-79-68" value="+33169087968" target="_blank">++ 33-1-69-08-79-68</a><br>
<a href="http://gael-varoquaux.info" rel="noreferrer" target="_blank">http://gael-varoquaux.info</a> <a href="http://twitter.com/GaelVaroquaux" rel="noreferrer" target="_blank">http://twitter.com/GaelVaroquaux</a><br>
</font></span><div><div>_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
</div></div></blockquote></div><br></div></div></div></div>