[Neuroimaging] Website Update

[Ben Cipollini]

Hi Vanessa,

Another solution is simply to send Jekyll the proper baseurl in all cases.
In my eyes, that's the simplest and intended solution. I just can't
understand why it's so hard to do easily, or at all.

The relative paths thing is another solution, but I feel that's a
workaround--Jekyll has the baseurl defined and configurable, it's clearly
part of the software design.

Hope we find an elegant solution soon :)
Ben

On Sat, Aug 22, 2015 at 10:56 AM, Vanessa <vsochat at gmail.com> wrote:

> Hi Ben,
>
> The problem is well understood - it is just about absolute vs relative
> path coding. When we specify the base url to be absolute, at the root ("/")
> this will render everything correctly locally, and if the site is hosted at
> some root, there as well, but only for pages present at the root. However,
> in the case of previewing the pages on circle, all paths must be relative
> (files rendered with a root path are not found). We need a solution that
> renders correctly in both places, for pages at all levels. So - methinks a
> good strategy would be to 1) for circle- dynamically change the paths of
> the artifacts in the test code from absolute to relative before finishing,
> and 2) for subpages use liquid syntax to detect when a path is at a level
> other than root and change appropriately. Actually, a strategy that could
> do the second would also fix the first issue with circle.
>
> I haven't even tried github pages yet because the workflow and paths for a
> repo level page is likely different from an organization one, so it would
> not be useful.
>
> I wont get a chance to work on this today bur likely tomorrow so please
> keep me in the loop!
>
> Best,
>
> Vanessa
>
> On Aug 22, 2015, at 10:32 AM, Ben Cipollini <bcipolli at ucsd.edu> wrote:
>
> I'm trying to install Jekyll now, and will see if I can reproduce the
> problem. If so, I may have a few mins today to think about a solution.
>
> Vanessa, do you have a sense of why this is happening? Is the problem
> finding a solution to a problem you understand well, or is the problem
> investigating why this is happening to start with?
>
> Thanks!
> Ben
>
> On Fri, Aug 21, 2015 at 10:01 AM, vanessa sochat <vsochat at stanford.edu>
> wrote:
>
>> Hi Matthew,
>>
>> I'm on board with Stefan's suggestion, I just stick to Poldracklab work
>> during the week and haven't done any new nipy site work. As I mentioned
>> earlier, I was hoping for some help with a more elegant solution to resolve
>> the current base url issue (please see my previous messages).  If there
>> aren't any ideas, I will likely implement a very un-elegant / harder to
>> change solution, just to get something working, and only after that does it
>> make sense to give a go at github pages deployment.
>>
>> Best,
>>
>> Vanessa
>>
>> On Fri, Aug 21, 2015 at 9:55 AM, Matthew Brett <matthew.brett at gmail.com>
>> wrote:
>>
>>> Hi Vanessa,
>>>
>>> Thanks again for doing this.
>>>
>>> Have you got a github-pages build of this somewhere?  Sorry if I
>>> missed it.  I tried building locally, but I'm not confident that I'm
>>> getting what you expect to see.
>>>
>>> It would be good to have the mission statement somewhere, if y'all agree.
>>>
>>> Do you have any thoughts on Stefan's suggestion?
>>>
>>> Cheers,
>>>
>>> Matthew
>>> _______________________________________________
>>> Neuroimaging mailing list
>>> Neuroimaging at python.org
>>> https://mail.python.org/mailman/listinfo/neuroimaging
>>>
>>
>>
>>
>> --
>> 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
>
>
> _______________________________________________
> Neuroimaging mailing list
> Neuroimaging at python.org
> https://mail.python.org/mailman/listinfo/neuroimaging
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/neuroimaging/attachments/20150823/b1a7f9f1/attachment.html>