[Neuroimaging] Nipy.org new website needs a complete remake

[vanessa sochat]

Hi everyone,

A quick update. I have never used github pages before, but was able to work
through the bugs of the freeze, and deploy the site to pages:

https://vsoch.github.io/nipy

A few other updates / notes:


   - All content / links must be https. This means it's best to serve most
   of our own css/js files, and embedded content that is not https will not
   render (for example, click on the embedded nbviewer post
   <https://vsoch.github.io/nipy/pages/7-28-2015-embed-ipython/>, and then
   inspect the browser to see the error)
   - The above would be an issue for any github pages. To address this, I
   figured out how to get syntax highlighting
   <https://vsoch.github.io/nipy/pages/7-28-2015-embed-code/> so we can
   code right in the markdown.
   - I styled the blog roll. I'm sure with more posts we would want some
   kind of pagination.
   - I added a few posts showing how to embed other content type.
   - The freezing process didn't grab the custom pages for some reason, and
   it worked when I did this
   <https://github.com/vsoch/nipy/blob/master/code/views.py#L46>.  This
   would mean that adding a project, it would be required to have a template
   for it. That comes down to copying a file and renaming it to the project
   name.

The process to update the pages is to basically:


   1. Add a new .md file in the code/pages folder
   2. python freeze.py
   3. Push to the gh-pages branch


Best,

Vanessa


On Tue, Jul 28, 2015 at 10:36 AM, vanessa sochat <vsochat at stanford.edu>
wrote:

> Hi Bob,
>
> I think we are moving toward a solution that will make it very easy to
> contribute content. Regardless of if we use jekyll, flask, or something
> else, right now contributing a new package just means adding a row to a tab
> separated file, and adding a new blog entry means adding a new file to a
> folder (with very minimal formatting). I think regardless of the solution
> that we will choose, we are optimizing with this goal in mind, so you
> should not worry.
>
> Best,
>
> Vanessa
>
> On Tue, Jul 28, 2015 at 9:55 AM, Bob Dougherty <bobd at stanford.edu> wrote:
>
>> I have to agree with Ariel on this. I think that any additional barrier
>> (no matter how small) will deter contributors. Like Ariel, I'm not a web
>> designer. For my limited forays into web design I use docpad, because when
>> I'm in web-design mode I like to think in javascript, so a js-based tool
>> seemed to make sense. I don't have any desire to learn (no matter how
>> trivial) yet another tool. If all I want to do is contribute content, I
>> just want to edit some markdown and be done with it. Ariel has laid out
>> some very good reasons to use jekyll. I haven't seen any similarly
>> compelling reasons not to use it. Is there any practical advantage to the
>> alternatives?
>>
>>
>>
>> _______________________________________________
>> Neuroimaging mailing list
>> Neuroimaging at python.org
>> https://mail.python.org/mailman/listinfo/neuroimaging
>>
>
>
>
> --
> Vanessa Villamia Sochat
> Stanford University
> (603) 321-0676
>



-- 
Vanessa Villamia Sochat
Stanford University
(603) 321-0676
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/neuroimaging/attachments/20150728/b06fd93b/attachment-0001.html>