3 Removed broken links.
source | link

I'm tasked with writing a style guide for a .NET application. Currently there's about six developers that just do whatever they want in terms of style. Similar buttons are in different spots, different controls are use, etc., etc. It's a mess.

I've researched some other style guides, and they often (always?) show what not to do. The lead developer mentioned that the style guide will be better received if I omit any "don't do's" and only include the "do's".

Why do style guides have what not to do listed as well?

Examples of style guides showing what not to do:

I'm tasked with writing a style guide for a .NET application. Currently there's about six developers that just do whatever they want in terms of style. Similar buttons are in different spots, different controls are use, etc., etc. It's a mess.

I've researched some other style guides, and they often (always?) show what not to do. The lead developer mentioned that the style guide will be better received if I omit any "don't do's" and only include the "do's".

Why do style guides have what not to do listed as well?

Examples of style guides showing what not to do:

I'm tasked with writing a style guide for a .NET application. Currently there's about six developers that just do whatever they want in terms of style. Similar buttons are in different spots, different controls are use, etc., etc. It's a mess.

I've researched some other style guides, and they often (always?) show what not to do. The lead developer mentioned that the style guide will be better received if I omit any "don't do's" and only include the "do's".

Why do style guides have what not to do listed as well?

2 Copy edited. Added some context. Dressed the naked links.
source | link

I'm tasked with writing a style guide for a .net.NET application. Currently there's about 6six developers that just do whatever they want in terms of style. Similar buttons are in different spots, different controls are use etc, etc., it'setc. It's a mess. I've

I've researched some other style guides, and they often (always?) show what not to do. The lead developer mentioned that the style guide will be better received if I omit any "don't do's" and only include the "do's".  

Why do style guides have what not to do listed as well?

Examples of style guides showing what not to do:

https://design.atlassian.com/2.1/product/components/buttons/

http://www.google.com/design/spec/animation/meaningful-transitions.html#

I'm tasked with writing a style guide for a .net application. Currently there's about 6 developers that just do whatever they want in terms of style. Similar buttons are in different spots, different controls are use etc etc, it's a mess. I've researched some other style guides and they often (always?) show what not to do. The lead developer mentioned that the style guide will be better received if I omit any "don't do's" and only include the "do's".  

Why do style guides have what not to do listed as well?

Examples of style guides showing what not to do:

https://design.atlassian.com/2.1/product/components/buttons/

http://www.google.com/design/spec/animation/meaningful-transitions.html#

I'm tasked with writing a style guide for a .NET application. Currently there's about six developers that just do whatever they want in terms of style. Similar buttons are in different spots, different controls are use, etc., etc. It's a mess.

I've researched some other style guides, and they often (always?) show what not to do. The lead developer mentioned that the style guide will be better received if I omit any "don't do's" and only include the "do's".

Why do style guides have what not to do listed as well?

Examples of style guides showing what not to do:

    Tweeted twitter.com/#!/StackUX/status/596755209851957248
1
source | link

Why do styles guides have what not to do?

I'm tasked with writing a style guide for a .net application. Currently there's about 6 developers that just do whatever they want in terms of style. Similar buttons are in different spots, different controls are use etc etc, it's a mess. I've researched some other style guides and they often (always?) show what not to do. The lead developer mentioned that the style guide will be better received if I omit any "don't do's" and only include the "do's".

Why do style guides have what not to do listed as well?

Examples of style guides showing what not to do:

https://design.atlassian.com/2.1/product/components/buttons/

http://www.google.com/design/spec/animation/meaningful-transitions.html#