Discussion on the standard of website production

Specification  

Once for some companies have formulated norms, there are some experience, I hope to discuss with you:

1. General company production on-line norms, should consider the website as an extension of enterprise CIS, is the spirit of the enterprise, the appearance and activities of the most direct embodiment, so some basic CIS elements should be published in the Web site is more stringent embodiment. In the formulation of norms on the corporate identity of the Web site specifications to make norms, that is, to make the standard identification and minimum identification samples, according to the Enterprise Identification Pengtong value standard network identification RGB color value and ASCII color value, and set up a Web site color system, according to the environment to determine whether the site to use a Make a sample that violates the specification. Only the identity of a complete grasp, in order to establish a Web site style, color, and establish a variety of effect methods.

2. When making specifications for the company, to consider the overall object of the site, for different objects to develop different standards of norms, the application of technology in particular, such as for overseas sites to fully consider the 13% Netscape users, in the use of CSS, JS and other technologies to strictly standardize, and the low version of the browser as the object, Based on the principle of using common technology.

3. The arrangement of the catalogue can follow the 8.3 principle as far as possible, but at present many foreign company website convention is to establish a assets folder, will all the external resources such as pattern, script, dynamic resources, multimedia resources and so on to classify the placement, more advantageous to the management, The name of the folder must be a comment on the category of data in the clip.

4. The norms developed should be of a strictly directive nature, single should take into account the development of network technology, should be clear norms of timeliness, in the limitation period, the norms must be followed the law, should avoid the use of "in principle," "as far as possible," such as the inability to quantify the language, resulting in the collective production of ambiguity.

5. The programmer who does the upstairs specification seems to overemphasize the "purity" of the code, prohibit the use of size to interfere with the image of the practice, and that this can be "as much as possible to play the browser itself," but this is actually an error, the browser based on the label properties can be faster to determine the size of the submitted surface, Publish the related pictures quickly, and when the properties are not specified, browser will be repeated through the comparison for the figure to determine a size, the inevitable impact of browsing speed, and in order to show the production "often need repeated changes" of the diagram is so standardized, as if the page style is not accurate enough to say that this standard itself is not enough norms.

6. In non-Mandarin pages, especially in the corporate category, the public-facing page should use <font> tags as much as possible to standardize the font, as the default browser is Netscape, which is used by a large number of people in the non-Chinese language department. And in the domestic manufacturers of the Web site should also be targeted at the lower version of the browser to standardize.

7. Some of the content belonging to the skill class, such as link path: <a href= "aboutus/index.htm" > and <a href= "aboutus/" >
Should not be specified in the specification. And some of the server's default page is not index.htm, if you update the server, and then make changes outweigh the gains. You should do less of this type of ellipsis when linking.

8. The production of the template should produce a relatively universal interface, then according to different browsing environment such as different resolution, different browser environment to make a more comprehensive and easy to call several sets of templates, and in a variety of environments to do rigorous testing.

9. Page size should be based on user analysis of the results confirmed, such as design-class site users relative to the browsing environment is relatively good, you can use more rich results, and the programmer-oriented site should be strictly streamlined, including all Dreamweaver and other production tools additional redundant code. Currently acceptable corporate home page should be controlled below 130K, content page should be controlled below 70K.

10. News categories such as the need to update daily or by the server automatically submitted pages suggest the date + order to do the naming convention.

11. In the specification should also take into account the application of the plug-in constraints, and submit can be public plug-ins for downloading.

12. Network specifications should generally be produced in PDF files for other production units to download.

13. Should the page copyright notice to make the specification, should be respectively in English and other text, clear text format, color, should not be mixed in English, neither fish nor fowl.