[Neuroimaging] Website Update

[vanessa sochat]

Exactly! That's how I got the frozen flask version up and running:

http://vsoch.github.io/nipy/

On Sat, Aug 22, 2015 at 11:07 AM, Ariel Rokem <arokem at gmail.com> wrote:

> Just to be clear:
>
> On Sat, Aug 22, 2015 at 11:04 AM, Ariel Rokem <arokem at gmail.com> wrote:
>
>> Hi Vanessa,
>>
>> Sorry for the delay in responding.
>>
>> On Sun, Aug 16, 2015 at 3:18 PM, vanessa sochat <vsochat at stanford.edu>
>> wrote:
>>
>>> Hi Everyone,
>>>
>>> Here is an update to the site. I've ported it into jekyll
>>> <https://github.com/vsoch/nipy-jekyll>, and tested the template on
>>> iphone and computer (seems reasonable). I've also gotten it to render the
>>> artifacts on circle.ci <https://circleci.com/gh/vsoch/nipy-jekyll/32>,
>>> so we could preview PRs (Click "artifact" and then find home.html
>>> <https://circle-artifacts.com/gh/vsoch/nipy-jekyll/32/artifacts/0/home/ubuntu/nipy-jekyll/_site/home.html>).
>>> However, I've run into a bug with regard to absolute vs. relative paths -
>>> when you click the demo link above, the "posts" not being at the base url
>>> means they will not be linked or render correctly (for example, here is
>>> a link
>>> <https://circle-artifacts.com/gh/vsoch/nipy-jekyll/32/artifacts/0/home/ubuntu/nipy-jekyll/_site/code-syntax/index.html>
>>> to a post on circle, and you won't see styling because the css/js links are
>>> broken)
>>>
>>> The site works perfectly given that we aren't serving it at a relative
>>> path, eg:
>>>
>>> jekyll serve --baseurl="/"
>>>
>>> And the challenge is finding a solution that will render locally, on
>>> github pages, and circle.ci, and what we need, I think, is some kind of
>>> liquid syntax that will detect when we are in a subfolder and render
>>> appropriately. I've been messing around with it for 7 hours today and can't
>>> figure it out, and I need to ask for help. Could someone else take a look?
>>> Likely someone with more experience than me with Jekyll could figure this
>>> out in a heartbeat (Ariel?) The plan right now, I'd like to propose, would
>>> be to figure out this bug, get it onto a (test) github pages, tweak the
>>> details of the content, make proper documentation, and then release to
>>> official github pages.
>>>
>>>
>> Why do we need CircleCI here? I am actually not sure what the issue is,
>> but here's the site rendered through gh-pages on my fork of your repo:
>>
>> http://arokem.github.io/nipy-jekyll/
>>
>>
> For this to happen, the content has to be on a branch named `gh-pages` in
> the repo. A jekyll build is triggered if and only if content is pushed to a
> branch with that exact name!
>
> Ariel
>
>
>
>> I did also add a Gemfile to the repo, and that might matter: I believe
>> Github pages serves jekyll through a call to "bundle exec jekyll serve"
>> (see here: https://help.github.com/articles/using-jekyll-with-pages/).
>>
>> One comment about the content: I would prefer to have a front page that
>> just states what this thing is, and the projects on a separate page. I
>> would like for it to be *super* easy to add projects. The whole idea is
>> that the NIPY community is not a static list of projects, but an
>> ever-evolving ecosystem.
>>
>> Cheers,
>>
>> Ariel
>>
>>
>>
>>
>>> Best,
>>>
>>> Vanessa
>>>
>>>
>>> --
>>> Vanessa Villamia Sochat
>>> Stanford University
>>> (603) 321-0676
>>>
>>> _______________________________________________
>>> Neuroimaging mailing list
>>> Neuroimaging at python.org
>>> https://mail.python.org/mailman/listinfo/neuroimaging
>>>
>>>
>>
>
> _______________________________________________
> Neuroimaging mailing list
> Neuroimaging at python.org
> https://mail.python.org/mailman/listinfo/neuroimaging
>
>


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