【Front-end】#001 Coding specification_html/css_WEB-ITnose

WBOY
Release: 2016-06-24 11:41:53
Original
868 people have browsed it

HTML coding style:

Document type: HTML5 type

<!doctype html>
Copy after login
Copy after login

<strong> 编码:</strong> 使用 meta 设置编码类型 UTF-8
Copy after login

<!doctype html>
Copy after login
Copy after login
<html>
Copy after login
  <head>
Copy after login
     <metacharset="utf-8">
Copy after login
  </head>
Copy after login
  <body>
Copy after login
  </body>
Copy after login
</html>
Copy after login

<strong>大小写:</strong>除了 Text  CDATA元素,其他都使用小写
Copy after login
 
Copy after login
Copy after login
Copy after login
Copy after login
<strong>缩进:</strong>整个文件要统一(具体看情况使用 2、4空格)
Copy after login
 
Copy after login
Copy after login
Copy after login
Copy after login
换行:出现块级元素(div、p),列表元素(ul,ol),表格元素(table) 换行,行内元素大于80换行
Copy after login
 
Copy after login
Copy after login
Copy after login
Copy after login
<strong>编程风格</strong>
Copy after login
  1. Strictly use closing tags to avoid nesting errors
  2. Do not mix JS, CSS, and HTML (extract CSS and JS)
  3. img, object Tags should use alt attributes
  4. button, input and other form tags. Remember to add the title attribute
  5. to simplify statements that reference CSS and JS

<!-- 不推荐 ?>
Copy after login
Copy after login
<linkrel="stylesheet"href="//www.google.com/css/maia.css"type="text/css">
Copy after login
<!-- 推荐 ?>
Copy after login
Copy after login
<linkrel="stylesheet"href="//www.google.com/css/maia.css">
Copy after login
<!-- 不推荐 ?>
Copy after login
Copy after login
<scriptsrc="//www.google.com/js/gweb/analytics/autotrack.js"type="text/javascript"></script>
Copy after login
<!-- 推荐 ?>
Copy after login
Copy after login
<scriptsrc="//www.google.com/js/gweb/analytics/autotrack.js"></script>
Copy after login

6. Prioritize the use of button tags instead of

7. The html tag must set the title attribute

CSS development specifications

  1. Encoded character set: UTF-8 (no BOM), saved as CSS file
  2. Must be written in lowercase letters
  3. Use meaningful short words for naming (or team norms)
  4. Add a space after the colon
  5. The selector and each attribute occupy one line each (selectors and curly braces do not need to be on a new line)
  6. Indentation: Fixed use 2 / 4 spaces, do not use the tab key
  7. A blank line between the selector name and the selector name (a blank line between the two style selectors)
  8. Each style needs to end with a semicolon Separate

/* 不推荐 */h3{  font-weight:bold;}
Copy after login
/* 推荐 */h3 {  font-weight: bold;}
Copy after login

/* 不推荐 */a:focus, a:active { position: relative; top: 1px; }/* 推荐 */h1,h2,h3 {  font-weight: normal;  line-height: 1.2;}
Copy after login

 
Copy after login
Copy after login
Copy after login
Copy after login

Writing order

css It should be written in the following order. The principle is positioning and layout first, details second

  1. display mode display
  2. positioning or floating mode position, float, clear
  3. Up, down, left and right positioning offsets left, top, right, bottom
  4. Height and width dimensions height, width
  5. Inner and outer padding margin, padding
  6. Border border
  7. Background
  8. Color color
  9. Font text font
  10. Text line-height, text-align
  11. Other miscellaneous

Z-index usage specifications

In principle, module css must comply with the following specifications when using absolute positioning, but it is not enforced. During the development process, use less absolute positioning layout and more use the layout manager to manage the layout.

  1. Map: The index range used is from 0-99, including tile maps, custom layers, legends, layer management, etc.
  2. Interface business Module: The used index ranges from 100-199, real-time water conditions list, etc.
  3. Footer: The used index range is from 700-799, including copyright, filing, Technical support, etc.
  4. Navigation: The index range used is from 800-899, including logo, system name, navigation bar, etc.
  5. Pop-up box: The index range used is from 900-999, including settings panel, prompt box, etc.

Related labels:
source:php.cn
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template