New Fluid Project site

Justin Obara obara.justin at gmail.com
Tue Dec 2 09:34:46 EST 2014


We could look at these docpad plugins for managing the redirects. 

https://www.npmjs.org/package/docpad-plugin-redirector
https://github.com/docpad/docpad-plugin-cleanurls

We should also consider what urls we actually need to maintain redirects for now and going forward.

thanks
Justin
> On Dec 1, 2014, at 1:46 PM, Antranig Basman <Antranig.Basman at colorado.edu> wrote:
> 
> The link "canonical" approach seems reasonable to me. It retains our site as static infrastructure, and I don't think we will have an unmanageable number of redirects to maintain. We should check that the user experience of this approach is reasonable, e.g. on mobile browsers.
> 
> Cheers,
> Antranig
> 
> On 01/12/2014 15:25, Jonathan Hung wrote:
>> 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.
>> 
>> 
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work



More information about the fluid-work mailing list