Mini Project Practice (a): Master & Default

In the previous article, we analyzed the structure of the UI layer and the Pagebase class, and today we shifted our attention to the page. The following diagram is the final effect of our system:

This is certainly not what I do, I can not do it: but I would like to outline the production process of the page and some experience skills:

The requirements analyst analyzes and determines which pages are required. Sometimes (most of the time) only consider the home page, because the home page can determine the style of the system. Set up the first page of other pages basically have to fall.

The requirements analyst and the customer discuss the style and hue of the page. The style of the system is usually some adjectives, such as simplicity, sprightly and so on. Good way is to prepare a lot of pictures (web Template better) to the user to see, let him choose, so that you can be very intuitive to understand the user needs what style of the page. And this image or template can be used as the basis for the art production page.

The requirements analyst and the user discuss and determine what is included in the page. For example, the latest article list, the list of hot articles, the login box, and so on, if the user lacks experience in this area, we want to guide users, such as providing a list of possible content, let the user to choose.

The user's request and the art staff to coordinate, of course, if you can get the art to participate in 1-3 steps, this step is saved, and the effect is better.

Art production PSD effect map, and users to further exchange, modify, until customer satisfaction. Here is a problem, is that users of the page you come up with the design is usually very dissatisfied, or even disappointed, and the art staff of the customer's opinion is very easy to conflict, demand staff (you) sandwiched between the two, difficult to deal with. The solution is to let the art staff in the first design when the 3-5 layout, each layout out of 2-3 colors, this to a skilled art should not be difficult things. And then discuss these more than 10 scenarios with the user, this has the following advantages: First, users feel that you are very serious and responsible for your impression is very good, and then affect his impression of the page design, really, things are sometimes so incredible; second, let the user choose between multiple pages to meet the desire of his decision, There is little change of opinion; third, for the art, the total amount of work (or even less), but feel better; four, unnecessary pages will not be wasted, the future of the project can be changed.

Cut PSD, out of HTML, CSS, and JavaScript. This step is no problem, the question is who to do this step? The artist is familiar with PS, also understand HTML and CSS, JavaScript is not necessarily. More importantly, the general art of writing the HTML does not consider the code to fill, so that the programmer is very embarrassed, and programmers understand HTML, Css,javascript is not alone, but the PSD is a bit reluctant. The solution is: Art and programmer pairing.