- From: Lea Verou <lea@w3.org>
- Date: Tue, 26 Mar 2013 20:04:16 +0200
- To: Julee <julee@adobe.com>
- Cc: Denis Ah-Kang <denis@w3.org>, Ryan Lane <rlane32@gmail.com>, Doug Schepers <schepers@w3.org>, "public-webplatform@w3.org" <public-webplatform@w3.org>
Hi all, I’ve been brainstorming for ideas for the error pages. The idea I’m thinking of going with is to create big numbers in the style of the logo (with colored edges in the same style) which will form the error code at the top of the page. Underneath will be a short description of what a 404 error is, like Seb suggested. The good thing about this is that it will work for all codes, with little extra effort. My question is: Do you think the page should be more minimal, or should it have the rest of the WPD cruft around it (navigation, search, footer, etc). In the former case I will create a static page, otherwise it might be worth to add a special WPD: page (going back and forth between WPD:404 and WPD:Not_Found). Cheers, Lea Lea Verou W3C developer relations http://w3.org/people/all#lea ✿ http://lea.verou.me ✿ @leaverou On Mar 22, 2013, at 01:27, Julee wrote: > Hi, Denis: > > I think having a good 404 page is a great idea -- and maybe some other key > error pages as well. (Have you ever seen Renny Gleeson's Ted Talk on > 404s?[1]) > > I'll add it to the agenda for tomorrow's meeting and perhaps someone will > volunteer. > > Regards. > > Julee > > [1] > http://www.ted.com/talks/renny_gleeson_404_the_story_of_a_page_not_found.ht > ml > > ---------------------------- > julee@adobe.com > @adobejulee > > > > > > -----Original Message----- > From: Denis Ah-Kang <denis@w3.org> > Date: Thursday, March 21, 2013 2:39 PM > To: Ryan Lane <rlane32@gmail.com> > Cc: Lea Verou <lea@w3.org>, Doug Schepers <schepers@w3.org>, > "public-webplatform@w3.org" <public-webplatform@w3.org> > Subject: Re: URL aliases for WPD without /wiki > >> On 03/21/2013 05:15 PM, Ryan Lane wrote: >>> Let's avoid using .htaccess. It's better if these things are done >>> through the server configuration. It's easier to troubleshoot things >>> when server configuration is done in a single place, and it's easier to >>> configuration manage it. >> >> Yes, it's better to have all these things in one place. The redirects >> have been added in the Apache configuration directly. >> >> Lea, I limited the redirect to request uris starting by >> "/(beginners|css|dom|concepts|accessibility|svg|html|javascript|apis)" >> so if we add new pages under www in the future, it won't be caught by >> the rewrite rule. >> Let me know if there's any issue. >> >> Concerning the 404s, I'll be happy to configure Apache to serve a better >> page if you have one. >> >> Denis >> >> > > >
Received on Tuesday, 26 March 2013 18:04:31 UTC