Explain what will be on each page

[subornaakter24]

To show your client what each page will look like, use one of the techniques.

A prototype is a sketch of all the pages of nursing homes email list a website, which is attached to the technical specifications. This way, the customer gets a clear idea of ​​what their project will end up being. Looking at the drawings, they can immediately say what needs to be changed.

What should be specified in the technical specifications for website development

Source: TippaPatt/ shutterstock.com

You can use the list of elements if you are too lazy to make a prototype. List what sections and blocks will be on the page and what they are for.

Blog (main section)

Top level heading.

The list of posts is in this format: picture - article title - one paragraph as an announcement.

Buttons for moving between pages. One page contains no more than 10 posts.

Blog (side column)

List of blog sections.

Subscribe to newsletter button.

Social network icons for going to the company page on VKontakte, Facebook, YouTube.

This description gives you an idea of ​​what the blog will be like.

Describe the scenarios for using the site

If a non-traditional interface is expected, it is not enough to simply demonstrate the structure and templates of the pages. It is important that all participants in the development and the customer himself understand how users will interact with the site. For this purpose, scenarios need to be created. The scheme of such a scenario looks simple:

Visitor action.

Reaction from the site.

…

Summary.

Example script.

Place an order:

The visitor clicks on “Order”.

An application form appears.

The user fills out an application, and the site responds by sending a notification that the order has been accepted.

The manager receives an email with the client’s contact information.

There is no need to write scripts in the technical specifications for developing a one-page website or a business card website. However, if some kind of interaction is assumed, it is better to indicate them.

Determine who is responsible for the content

Some developers can not only create a website, but also fill it with content. There are also those who are ready to write texts, but for a separate fee. Decide on this issue before you start the process. Specify in the TOR what content you need.

Identify all the performers who will be involved in this or that content.

Example: The performer must write the texts and place them together with the images on the site. He must also add Title headings and Description meta tags for:

home page;

About Us pages;

all pages in the section "Our Services";

privacy policies.

It is difficult to define criteria that would give an objective assessment of texts. There is no need to specify that articles should be interesting and exciting: such characteristics are too abstract.

It's better to write that you need only unique texts. This will once again protect you from performers who don't care about their work.

Describe the design (if you can)

What should be specified in the technical specifications for website development

Source: wee design/ shutterstock.com

Design, like texts, is difficult to evaluate. If you discussed the color scheme with the client, you can indicate it in the technical task for the development of the site. If there is a brand book and fonts are specified, then include this information in the task.

Just don't write that the design should be stylish and modern. This is vague information that doesn't make sense for the technical specifications.

What might be the requirements for the design and content of a web resource? Here is an example.

Content:

All pages contain unique text that has never been published anywhere before.

Design:

White is used as a background.

Green is the corporate color.

Option for describing the design in the technical specifications for website development
Give the developer the name of your web resource, send him a logo and a brand book on the use of the corporate style. If there is no logo or corporate style guide, the contractor can suggest something to you himself. In extreme cases, he will recommend specialists. As for the design of the project, you should at least tell him what the style of the project should be. It is not necessary to describe it in all details, but in order for the process to go faster, the developer should understand what you want.

For example, you can say that you need a laconic site in pastel colors, the headings and other details should be highlighted in blue to emphasize them. Let the designer decide what the buttons, links and navigation will be.

Read also!

"Choosing a domain for a website: how to avoid a fatal mistake"
Read more
Explain to the contractor what needs to be done exactly according to the technical specifications, and in what aspects you leave him creative freedom. This way, he will understand what your reaction will be to certain decisions on his part. Keep in mind that, most likely, what you included in the technical specifications for website development will not look very harmonious as a result. However, if you work with a professional developer, he will definitely point out inconsistencies at the sketch stage, and then suggest the best course of action.

The ideal option is if you describe in as much detail as possible how you see the design of your web resource. In addition, you can list in the technical specifications sites that match your topic. Give a brief description for each example.

Don't give the designer too much information. An experienced specialist can see the future website right away. Avoid frequently introducing new wishes into the project during the work, otherwise you will not only get confused yourself, but you will also interfere with the designer and thus waste a lot of time. Rely on the recommendations we gave above. This will allow the developer not only to demonstrate his potential as a professional, but also to obtain a result that best meets the customer's requirements.