Comments on: Web Standards http://www.clevegibbon.com/contentmanagement/2010/05/05/web-standards/ Marketing technologist, content management strategist, digital platform architect, technology evangelist. Wed, 08 Jun 2011 00:06:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Web Standard Template : Content for the Masses http://www.clevegibbon.com/contentmanagement/2010/05/05/web-standards/comment-page-1/#comment-319 Web Standard Template : Content for the Masses Tue, 11 May 2010 19:09:39 +0000 http://www.clevegibbon.com/contentmanagement/?p=213#comment-319 [...] time and the right effort into Web Standards, will surely reap the benefits. We covered this in a previous post. Today, we dive straight in with a concrete example: URL Naming Web Standard. Note, just to keep [...] [...] time and the right effort into Web Standards, will surely reap the benefits. We covered this in a previous post. Today, we dive straight in with a concrete example: URL Naming Web Standard. Note, just to keep [...]

]]> By: Greg Gigon http://www.clevegibbon.com/contentmanagement/2010/05/05/web-standards/comment-page-1/#comment-317 Greg Gigon Wed, 05 May 2010 21:10:31 +0000 http://www.clevegibbon.com/contentmanagement/?p=213#comment-317 Hi Cleve It goes both ways for me. Sometimes it is a part of the team and sometimes we for entire new team. I liked the way you put it: "I try to convey Web Standards in a language that makes sense to them." That is actually the only way of convincing. Standard means more viewers across all the browsers, this could mean more money. Standard means content makes sense to search engines, this brings more viewer, eventually more money. Deveopment team has clean, organised plate, means they work faster, means less money spent, means "on budget" (at best :), so on :) I do agree with you and I think that industry is recognising the Standards slowly and more and more people needs less convincing and more action :) Keep up the good work my man. Greg Hi Cleve
It goes both ways for me. Sometimes it is a part of the team and sometimes we for entire new team.

I liked the way you put it: “I try to convey Web Standards in a language that makes sense to them.” That is actually the only way of convincing.

Standard means more viewers across all the browsers, this could mean more money. Standard means content makes sense to search engines, this brings more viewer, eventually more money. Deveopment team has clean, organised plate, means they work faster, means less money spent, means “on budget” (at best :) , so on :)

I do agree with you and I think that industry is recognising the Standards slowly and more and more people needs less convincing and more action :)

Keep up the good work my man.
Greg

]]> By: cleve http://www.clevegibbon.com/contentmanagement/2010/05/05/web-standards/comment-page-1/#comment-316 cleve Wed, 05 May 2010 17:42:56 +0000 http://www.clevegibbon.com/contentmanagement/?p=213#comment-316 Hi Greg, thanks for your comment. I'm guessing that in your dealings with 'the organisation' you were being brought in as a the Web Team and working for the business. In which case, you should be bringing your Web Standards to the table. Sharing the knowledge. In projects where you join and/or extend the in-house Web Team, these folks definitely do care. Also, I'll get to this in another post but Web Standards also include areas such as information structure and access, editorial workflow and analytics. These type of Web Standards are very much in the business domain and something that you need to educate folks in up front. Call it on-boarding your client. But its definitely a line item in the project plan. What do I do to reach out to these organisations? I try to convey Web Standards in a language that makes sense to them. Budget, time, effort, conversions, whatever it takes. I try to frame Web Standards within the context of their Web Policies which are set at a more senior and strategic level. But again, more on this later. Greg, I've just started down this path and already its rocky. But I feel it just needs to be done... Hi Greg, thanks for your comment.

I’m guessing that in your dealings with ‘the organisation’ you were being brought in as a the Web Team and working for the business. In which case, you should be bringing your Web Standards to the table. Sharing the knowledge. In projects where you join and/or extend the in-house Web Team, these folks definitely do care.

Also, I’ll get to this in another post but Web Standards also include areas such as information structure and access, editorial workflow and analytics. These type of Web Standards are very much in the business domain and something that you need to educate folks in up front. Call it on-boarding your client. But its definitely a line item in the project plan.

What do I do to reach out to these organisations? I try to convey Web Standards in a language that makes sense to them. Budget, time, effort, conversions, whatever it takes. I try to frame Web Standards within the context of their Web Policies which are set at a more senior and strategic level. But again, more on this later.

Greg, I’ve just started down this path and already its rocky. But I feel it just needs to be done…

]]> By: Greg Gigon http://www.clevegibbon.com/contentmanagement/2010/05/05/web-standards/comment-page-1/#comment-315 Greg Gigon Wed, 05 May 2010 13:33:17 +0000 http://www.clevegibbon.com/contentmanagement/?p=213#comment-315 Hi Cleve I do agree with you that Web Standards are important and they are there to help you. Unfortunately there is a bigger problem to realise, that the organisations don't care about Web Standards. There is a minority of Gov organisations that need to make their web sites compliant to standards as they have to be accessible. But, this is only due to that single fact. All the big organizations I worked with don't care about the standards, all they need is the final result. If it was achieved one way or another it doesn't matter. What would you do and how will you try to reach out to those organisations and tell them that standards are important, and why? In places like these we were usually left with "do whatever you want as long as I get what I want" kind of environment. This left us, the devs, a possibility to do the work according to the standards. That brings out another important aspect. People who are actually producing the final result should take the responsibility for the Standards. I hope that the organisations will recognise the importance of Web Standards. Cheers, Greg Hi Cleve
I do agree with you that Web Standards are important and they are there to help you. Unfortunately there is a bigger problem to realise, that the organisations don’t care about Web Standards. There is a minority of Gov organisations that need to make their web sites compliant to standards as they have to be accessible. But, this is only due to that single fact. All the big organizations I worked with don’t care about the standards, all they need is the final result. If it was achieved one way or another it doesn’t matter.

What would you do and how will you try to reach out to those organisations and tell them that standards are important, and why?

In places like these we were usually left with “do whatever you want as long as I get what I want” kind of environment. This left us, the devs, a possibility to do the work according to the standards. That brings out another important aspect. People who are actually producing the final result should take the responsibility for the Standards.

I hope that the organisations will recognise the importance of Web Standards.

Cheers, Greg

]]>