Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Web Developer Checklist

webdevchecklist.com

Post reply on HN
Print view View original

51–60 of 77 posts

Re: Web Developer Checklist

#51

Post by franze »

sorry but that

   Remove 'www' subdomain
is just harmful. force 'www.' instead. why? shitty URL parsers, marketing people and DDOS attacks, that's why.

let's imagine you write a

  - blog post
  - blog comment
  - press release (distributed via free and paid press release services)
  - mail
  - word
  - forum post
  - ...
  - ...
if you have a non-www URL it's a game of chance, your in text "whatever.tld" domain will get transformed into a clickable link. yes, a lot of modern URL parses will transform whatever.com into a clickable link, some will even transform whatever.in into a useable link, but a lot of old, shitty, idiotic, strange URL parsers won't. and well, a big part of the web, i would say most of it, is not up to date. so using non WWW will lead to a loss of inlinks and to a poor user experience of users who want to reach your site, but can't click on the in-text-domain (they need to copy/paste instead)

and the situation will get worse with the new commercial TLDs to come.

yes, you can - in most cases - force a domain to link conversion in most CMS if you write http:// in front of it. but well, in a promo text most marketing/pr people will not write "and http://whatever.tld has a new feature to give people endless bliss" they will write "whatever.tld has a new ....".

oh, and by the way. whenever a journalist will write a piece about you, in print or online, they will always (or at least in a lot of cases) write www in front of your domain anyway. yeah, that's not an issue if you have redirects in place, just annoying if you have an non-www webproperty.

plus

having a subdomain is another layer of defenses agains DDOS attacks. see this discussion on hacker news from may 18 2011 (my birthday by the way) http://news.ycombinator.com/item?id=2575266

go for www.

Re: Web Developer Checklist

#53

Post by halfninety »

tokenadult wrote: post #39

I see that Jakob Nielsen's venerable "Top 10 Mistakes in Web Design" checklist http://www.nngroup.com/articles/top-10-mistakes-web-design/ just got new styling the other day, as I work on updating my seventeen-year-old personal website. There are still a LOT of websites that make several of those top ten mistakes. They are higher priority than many of the other issues mentioned on the checklist kindly submitted here.…

Nice list, but I think it can be condensed into one:

Use your own site and make sure you don't hate it yourself.

Re: Web Developer Checklist

#55

Post by jacobwyke »

I have a template project in Basecamp that contains a similar kind of list of tasks that I use to launch all projects.

Just have to create a new project with the template for each launch and then work your way down.

Re: Web Developer Checklist

#56

Post by bwblabs »

A no-www domain might not be the best solution if you ever want a 'Cookie-free Domain' (static.) for images etc. which speeds up your site. If you start with a no-www domain you have to setup a different domain (no subdomain) for it: like sstatic.net for SO, ytimg.com for YT and yimg.com for Yahoo.

When the browser makes a request for a static image and sends cookies together with the request, the server doesn't have any use for those cookies. So they only create network traffic for no good reason. You should make sure static components are requested with cookie-free requests. Create a subdomain and host all your static components there.

If your domain is www.example.org, you can host your static components on static.example.org. However, if you've already set cookies on the top-level domain example.org as opposed to www.example.org, then all the requests to static.example.org will include those cookies. In this case, you can buy a whole new domain, host your static components there, and keep this domain cookie-free.

http://developer.yahoo.com/performance/rules.html#cookie_fre...

Re: Web Developer Checklist

#57

Post by Joeri »

zxcdw wrote: post #33

It's sad how "Security" there's only one very generalizing item. "Implement best practices". Right. Is the author just ignorant, or am I a fool thinking that if anything it should be "Security" which has the most elaborate items?

Security checklist: https://www.owasp.org/index.php/Category:OWASP_Application_S...

Lowest level 1a has 22 things to verify, highest level 4 has 121 things to verify. That's a lot of checkboxes.

Re: Web Developer Checklist

#58

Post by retube »

bwblabs wrote: post #56

A no-www domain might not be the best solution if you ever want a 'Cookie-free Domain' (static.) for images etc. which speeds up your site. If you start with a no-www domain you have to setup a different domain (no subdomain) for it: like sstatic.net for SO, ytimg.com for YT and yimg.com for Yahoo. When the browser makes a request for a static image and sends cookies together with the request, the server doesn't have…

I never considered this before. A great tip, thanks

Re: Web Developer Checklist

#59

Post by ralph »

bwblabs wrote: post #56

A no-www domain might not be the best solution if you ever want a 'Cookie-free Domain' (static.) for images etc. which speeds up your site. If you start with a no-www domain you have to setup a different domain (no subdomain) for it: like sstatic.net for SO, ytimg.com for YT and yimg.com for Yahoo. When the browser makes a request for a static image and sends cookies together with the request, the server doesn't have…

I'm not sure that works well with SPDY; it would prefer the same domain?
Post reply on HN