[Neuroimaging] Site Discussion
arokem at gmail.com
Wed Aug 26 19:44:34 CEST 2015
Sorry for checking out on the technical discussions. It's been a busy
couple of weeks!
I did not particularly mind the appearance of the old site. I was more
concerned with the content.
In particular, quoting myself from back in May (archives of that list for
that time-frame are apparently lost forever...):
"It doesn't really represent the current state of affairs, and is s source
of confusion for the unwary beginner.
One proposal, that I would be happy to lead (if no one is really aching to
do it themselves...) was to create a community portal on that page, where a
large number of projects in this space could be represented through a
(semi-) rational organization. Something with a front page that tells the
beginner that there are many paths through this particular garden, and
guides them along to what they need."
- "large number of projects" precludes any particular project from
appearing on the front page. I don't mind (and indeed have put) a link to
the nipy github organization. See message here:
- "(semi-) rational" means that the projects are organized in a directory
in a way that someone just entering the field can easily browse.
- "guides them along" would mean that we would want to add content on a
more-or-less regular basis with some tutorials, links to events, rants,
I don't mind if we use sphinx, or pelican (or anything else), but I did
choose jekyll because of its perceived advantages on the github platform
(see discussion here:
https://mail.python.org/pipermail/neuroimaging/2015-July/000174.html). I am
always happy to be proven wrong for my choices, and for others to show me
the way to the light.
On Wed, Aug 26, 2015 at 8:32 AM, Matthew Brett <matthew.brett at gmail.com>
> On Wed, Aug 26, 2015 at 4:10 PM, vanessa sochat <vsochat at stanford.edu>
> > Hi Group,
> > Ben and I are having some discussion on the higher level goals of the
> > and want to bring everyone in. In summary, we want something that is
> easy to
> > contribute content to, and has continuous integration for previewing
> > updates. I am wondering, what was wrong with the initial look of the
> > Was it that sphinx is hard to update?
> Actually, I think that sphinx is a very good option, and most other
> scientific Python sites use sphinx for their main pages.
> The particular template that we were using was a little dated and
> ugly, but I bet that could be improved.
> Most if not all developers are perfectly capable of building the
> sphinx documentation locally to preview it, but we can also do what
> other projects are doing, and build / publish the docs in some
> temporary place for each commit, using an entry in the travis-ci
> matrix of jobs.
> I think Ariel was particularly attracted to Jekyll / github pages,
> because it is very easy to get a rendered version to look at with a
> git push, and although that is generally desirable, I think building /
> reviewing locally is at least as important.
> So - if it were entirely up to me - I would prefer we go back to
> sphinx, on the basis that it is a very familiar workflow to most
> Python developers.
> Thanks very much for doing all this work by the way - it's very
> helpful, and I'm sorry that we are going round and round.
> See you,
> Neuroimaging mailing list
> Neuroimaging at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Neuroimaging