The commercial value of Web standards

Web|web Standard

Text from: adaptivepath.com Author: Jeffrey Veen is one of Adaptivepath.com's partners who specializes in web design technology, and you can learn more from his personal site veen.com. It's been a long time since I started working on web design to join groups that have been designed with web standards. I feel more and more that it is the right thing to do design with the standards recommended by the Consortium. When I was about to redesign the adaptivepath.com site, my partner agreed to build it in a standard way. But before we start, we have a discussion: It takes a lot of effort to adopt web standards, is it worth it? Of course, redesigning can build credibility among "web standards advocates," but is the standard really important for a personal business site like ours, except for the industry's accolades? Can web standards bring rewards for us? What are the economic benefits of switching to XHTML+CSS? All the answers are: Yes. Accelerate development Although the simplicity of HTML pages has greatly facilitated web development, it has also become a curse. Because they are so "tolerant" of code formats, they encourage the development of private code in the browser, which results in countless users not being able to get the best experience (see the best results of a page). Many of our customers have built multiple versions of the site to provide the most perfect design possible for more users. For our company, we only need a set of HTML pages, a stylesheet and a small amount of development, more than 95% of adaptivepath.com site users follow the standard (Standards-c ompliant) Browser, so we think, It's time to transition to Web standards. Web standards force you to do error checking. Simply declare what version of your HTML is, and the validator will check your page according to your stated criteria. The validator will rigorously check and tell you what bugs are in detail, which shortens the amount of time the developer spends on quality and keeps your site highly consistent across browsers. Even now browsers still have some bugs to show, but that's a lot better than it was five years ago. Easy to maintain and increase opportunities For years, the Web standards community has recommended the "keep visual design and content separate" advantage, which means that HTML becomes very simple (almost ridiculous), most of the xhtm L pages only have some rich semantics and tags, as well as a link to a strong CSS file. This complete separation makes your page development and maintenance easier, first of all because it enables better coordination between development teams, such as editing and designers working separately. Recently, there is a project, we use CSS technology, we are on our own development server for customers to develop CSS files. While they are preparing content on the back-end server, we can constantly modify the design, as long as we simply edit the CSS file without having to keep in touch with their release system, the work is done in parallel, and we dramatically shorten the development time. Rapid development offers competitive and cost advantages, and shorter development times not only cost-saving, but also frees up resources, thus gaining more opportunities. Expand Access Channels Clean code to bring more benefits. Browsers that do not support CSS can now simply ignore stylesheets, in other words, semantic XHTML representations can be rendered by any browser, including non-traditional clients, such as mobile phones, PDAs, voice readers and screen readers, and any device that supports these simple tags. A web-standard site can support mobile Access, Support Section 508 Ease-of-use standards, and compatible with previous versions of browsers. You can get all the benefits and be easier to develop and maintain, and even, in the process, you can save some hardware costs. Save bandwidth cost When we stripped the font, table tags, and some pictures for decoration from the page, we reduced the page size from 20.9k to 9.2k. At the moment, these reductions seem trivial, but when all the pages are gathered together a lot, the traffic on our site is overwhelmed. Our site has about thousands of page views per day, which can save 56% of the bandwidth. and large commercial sites may be within one or two minutes to achieve such a visit, popular popular sites more often a day to reach Baisu page traffic. If you save 30-40k per page, plus a cached style sheet that doesn't need to be downloaded again, you can save thousands of dollars a month for these sites. You will see those it people are excited about this design! Improve the user experience Money is easy to quantify, and compressing code also brings more hidden and additional benefits. It's no secret that a fast, active site can always bring a better, more comprehensive user experience. In the early days of the web, a huge graphical interface designed to allow dial-up users to endure slow access, a situation that has improved with the popularity of broadband. But business travelers on business may still be using the hotel's telephone dial-up to become your new user, with clean, standardized code that can help your users quickly and easily accomplish their goals on the site. The transformation proved to be worthwhile. We decided to switch to the standard, not a polite, but because the standard can bring lovely economic benefits. That's why more and more cool stations are starting to turn to Web standards. Why don't you start the transition to XHTML+CSS? The economic benefits brought about by standardization are real. Once our site has been standardized, business will realize the true promise---content free to share.