New Fluid Project site

[Jonathan Hung]

I've been investigating how to set up redirects for the new Fluid website
on github pages.

The published method of performing a redirect on gh-pages is to use a
plugin with Jekyll (see this document
<https://help.github.com/articles/redirects-on-github-pages/>). However, we
are using Docpad, not Jekyll - so this approach to redirects will not work
for us.

One alternative is to use Javascript to handle redirects, but this
technique may not be desirable as it does not provide a HTTP 301 -
Permanently Moved error code.

Another approach is to use a meta "refresh" + link "canonical" as
documented in this blog post
<http://konradpodgorski.com/blog/2013/10/21/how-i-migrated-my-blog-from-wordpress-to-octopress/#redirect-301-on-github-pages>.
This provides a 301 error which search engines like, but requires
individual HTML files for each redirect we want. This may be acceptable if
the number of redirects is not too large.

Finally, we can consider hosting our website on our own web server. This
makes redirects a lot easier to manage, but requires resources for server
maintenance and requires an extra step of deploying from github to the
webserver whenever content needs updating.

Anyone else have thoughts?

- Jon.


On Mon, Nov 24, 2014 at 10:34 AM, Jonathan Hung <jhung at ocadu.ca> wrote:

> The 404 error is the easiest but the least useful. I would like to see a
> proper redirect to an equivalent page but this will require a little
> investigation - I can spend a little time today investigating this.
>
> Also confirmed, promote Infusion to its own spot in the navigation.
>
> Thanks Colin.
>
> On Fri, Nov 21, 2014 at 3:41 PM, Colin Clark <colinbdclark at gmail.com>
> wrote:
>
>>
>> On Nov 20, 2014, at 8:46 AM, Jonathan Hung <jhung at ocadu.ca> wrote:
>>
>> 1. I have filed a Jira for the 404 page an redirects (
>> http://issues.fluidproject.org/browse/FLUID-5565,
>> http://issues.fluidproject.org/browse/FLUID-5566)
>>
>>
>> Thanks. Any idea when we'll implement this, and which strategy we'll use?
>>
>> 2. Do you have any URLs / pages of old Fluid Project website pages that
>> you know should be reproduced? We can crawl through the wiki, but it helps
>> to know which pages are priority.
>>
>>
>> We should probably do a survey of prominently linked URLs, but ideally
>> we'd make sure all the old URLs continue to work and redirect to somewhere
>> sensible.
>>
>> 3. Moving Infusion above the fold would be tricky because this would push
>> the 3 coloured project boxes down below the fold, or we would have to
>> consider using a sidebar. We have some new design minds at the IDRC, so
>> maybe we can figure something out. A separate page for Infusion may make
>> sense since it's a "product". What do others think?
>>
>>
>> I think it makes a lot of sense to give Infusion its own page and link in
>> the overall navigation.
>>
>> I can also help to rewrite the "about" page so that it reflects our
>> approach to inclusion and and designing for diversity.
>>
>> Colin
>>
>
>
>
> --
>
> *JONATHAN HUNG*
>
> INCLUSIVE DESIGNER, IDRC
>
>
>
> *T:* 416 977 6000 x3951
>
> *F:* 416 977 9844
>
> *E:* jhung at ocadu.ca
>
>
>
> *OCAD UNIVERSITY*
>
> Inclusive Design Research Centre
>
> 205 Richmond Street W, Toronto, ON, M5V 1V3
>
>
>
> www.ocadu.ca
>
> www.idrc.ocad.ca
>



-- 

*JONATHAN HUNG*

INCLUSIVE DESIGNER, IDRC



*T:* 416 977 6000 x3951

*F:* 416 977 9844

*E:* jhung at ocadu.ca



*OCAD UNIVERSITY*

Inclusive Design Research Centre

205 Richmond Street W, Toronto, ON, M5V 1V3



www.ocadu.ca

www.idrc.ocad.ca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20141201/ed0c361e/attachment.html>