Front-end architecture of the work flow

Front-end architecture is a series set of tools and processes .

Front-end architecture that we start a project when the need to develop a series of norms and planning .

1.0 phase, the selected front-end framework , to build a continuous integration environment , write front-end applications build script .

2.0 phase, the selected front-end frame + complete build script and build the system , teams working in parallel , standardization (oral or automated).

3.0 stage, front-end frame selected + complete build scripts and build system + process standardization , front-end development framework (security and ability to enhance the level), front-end System Design (the convenience of the user experience and developer),

It has its own front-end application framework , development tools or collaboration tools (development costs). (Focus of the work from the business to the build tool).

Project phase to evolve, and team size are closely related. In order to protect the team can successfully collaborate to develop , we need to develop a series of development processes , and create the appropriate development standards .

"The essence of socialism is to liberate and develop the productive forces, who is the dominant factor in productivity, the fundamental task of liberating the productive forces is to liberate people, the market economy is to achieve resources (including human resources) to optimize the best economic operation mechanism configuration."


TIPS:

  1. Code Organization: Open the README understand what relevant information should read, read package.json understand the system infrastructure, which uses the component library, as well as configure what build script, browse a file in your home directory, to understand some of the plug-in system configuration, enter the code to read and understand the project
  2. Code style
  3. Lint specification Code: whether the statement end with a semicolon, indented spaces, it is determined to use === types are equal, if the function braces wrap
  4. Standardized name: nomenclature (nomenclature hump, underlined nomenclature, Hungarian notation), CSS preprocessor and naming rules, naming components
  5. Specification development tools: EditorConfig, Lint plug, spelling detection completion path (Path Intelllisense), code auto completion, Emmet, plug-in, the code format
  6. Project documentation: README build guide (operational support environment, the necessary dependencies environment and how to build, project installation guide, or the last line of the example operating environment, related document links, relevant source of Information, discussion groups)
  7. Draw Chart: code generation, professional tools, tools included with the software, online tools
  8. Editable document library: WIKI software, professional collaboration tool based on Git + Markdown code management tool
  9. Record architectural decisions: lightweight architecture Record of Decision
  10. Visualization document: pay attention to the readability of the code
  11. Kanban tool: the unified management of business knowledge
  12. Submission Information: Use the Version Manager Git, SVN almost all of the industry standard
  13. Way open source projects
  14. Through the process of improving the quality of the code: Code preprocessing, the code manually review
  15. Use tools to enhance code quality
  16. Test strategy: unit testing, component testing, contract test / interface testing, E2E test

"Strategy is the encapsulation of the algorithm, is a pattern of behavior, each algorithm is encapsulated into a separate class have a common interface, so that that they can replace each other."


 

to sum up:

  1. Using the workflow is to team parallel development , it is necessary to organize product development to a certain size.

  2. The different strategies adopted two main measures, the frequency of use and cost-effective. Adopt specific strategies depending on the circumstances.

  Note: If the code organization, standardize naming, submitting information (Git, SVN), Kanban tools to improve code quality through processes, test strategies (unit testing) using a higher frequency in the industry.

  3. workflow, is a collection of tools and processes is a kind of nature, tools and processes of policy .

Guess you like

Origin www.cnblogs.com/bearRunning/p/12237450.html