Describe the tools and requirements for hosting
Posted: Sun Feb 02, 2025 6:21 am
Let's say you've been working on a website for a couple of months and you've got a fantastic result. You've coordinated every step with the customer, and they're happy. And then you hand over the project, and the client is angry because they wanted a WordPress admin panel, not MODx.
To avoid an unpleasant situation, inform him in advance about what engines, libraries and tools you usually use. Explain to him what the hosting requirements are. After all, it may turn out that the client's server is hosted on .NET, and you make a site on PHP.
List the requirements for the site to work
The web resource must function using any journalist email list browser and any device. Of course, both the customer and the contractor know about this. However, it is better to include this point in the technical specifications for the development of the site so that the client can protect himself from poor quality work. Example:
The finished website must meet the following technological requirements :
1.1 It should be displayed equally in Chrome1+, IE9+, Safari4+, Opera10+ browsers.
1.2. It should adapt to the most popular device sizes:
computer monitor - 1600 x 992 px;
laptop - 1280 x 802 px;
tablet - 768 x 1024 px;
phone - 320 x 480 px.
Thus, work on the site necessarily involves the creation of a mobile version.
Here you also need to specify what the site loading speed should be, what the maximum load on the site should be, as well as the requirements for protection from hackers.
Specify the structure of the site
Before you outline the design and do the layout, agree on the structure of the web resource with the customer.
Find out what he wants. Consult with developers, SEO specialists, marketers and editors and determine what pages the project needs. Decide how you will link them together.
The structure of the site can be presented in the form of a diagram, or you can simply make a list of sections.
Web resource structure
The structure of a web resource is its foundation. If you work it out poorly, you will get an unsuccessful site.
Explain what will be on each page.
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 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:
To avoid an unpleasant situation, inform him in advance about what engines, libraries and tools you usually use. Explain to him what the hosting requirements are. After all, it may turn out that the client's server is hosted on .NET, and you make a site on PHP.
List the requirements for the site to work
The web resource must function using any journalist email list browser and any device. Of course, both the customer and the contractor know about this. However, it is better to include this point in the technical specifications for the development of the site so that the client can protect himself from poor quality work. Example:
The finished website must meet the following technological requirements :
1.1 It should be displayed equally in Chrome1+, IE9+, Safari4+, Opera10+ browsers.
1.2. It should adapt to the most popular device sizes:
computer monitor - 1600 x 992 px;
laptop - 1280 x 802 px;
tablet - 768 x 1024 px;
phone - 320 x 480 px.
Thus, work on the site necessarily involves the creation of a mobile version.
Here you also need to specify what the site loading speed should be, what the maximum load on the site should be, as well as the requirements for protection from hackers.
Specify the structure of the site
Before you outline the design and do the layout, agree on the structure of the web resource with the customer.
Find out what he wants. Consult with developers, SEO specialists, marketers and editors and determine what pages the project needs. Decide how you will link them together.
The structure of the site can be presented in the form of a diagram, or you can simply make a list of sections.
Web resource structure
The structure of a web resource is its foundation. If you work it out poorly, you will get an unsuccessful site.
Explain what will be on each page.
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 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: