Correctly drafted technical specifications (TS ) is not only the key to success, but also a way to avoid possible misunderstandings in the process. What is a technical specification? This is a certified document that contains a detailed description of the work involved in developing a website.

There are no specific rules for writing a technical specification. It can be drawn up in any form and at the request of the project manager or developer. There are only general recommendations and advice from employees based on their personal experience. A conversation with the customer is held right before the work on the description begins. It's important to find out more details and describe everything as thoroughly as possible. First of all, we need to provide general information - the purpose of the project, its functional destination. The size of the technical specification can be very different in size, because it all depends on the product you want to create - a business card site, a landing page, or an online store.

The description of the site structure, i.e. the display of its external and internal details, is quite important, because we indicate and describe the structure of pages and chapters, form a list of future components. 

Structuring can be of different types: random, linear, hierarchical.

A website with the first type of structure looks disorganized. You can get to a particular page in different ways. A linear structure implies a step-by-step transition from one page to another along a clearly defined path. When you visit a website with a hierarchical structure, you can get to the second-level pages from the home page, and from the second-level pages to the third-level pages, and so on.

Each website is unique, but many of them have a similar outwardly standardized structure. At the top of the home page is the header, which is displayed when you navigate to other pages. The header contains a menu with hyperlinks to the main sections of the site - it can be either text or graphic elements. At the bottom of the page is the footer, or the basement of the website, where the menu is also replicated. Of course, there should also be a dedicated area for content.

Also, if necessary, the terms of reference provide a list of technologies that will be used to realize the required functionality.

For better understanding, the terms of reference may provide specific examples of implementation - links to other sites, screenshots. It is also possible to provide a list of browsers in which the site should be displayed correctly.

Prototypes can be drawn for individual pages. This is a preliminary diagram that contains certain components - navigation, menus, forms, etc. The prototype will be useful for both the designer and the developer. It will be easier and faster for the software developer to evaluate the work.

To sum up, before developing a product, you first need to have an oral conversation with the customer. After that, we formulate the document in detail, and then submit it to the customer for approval. We make corrections, if necessary, determine the deadlines, sign it, and start working.

It should be understood that the terms of reference cannot be perfect, as new ideas and additions appear during the development process, and this is normal. It is important to fulfill your obligations within the agreed framework. This is the only way for the two sides to reach mutual understanding.