Functional structure and page structure design

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

Once there is no understanding of web design Friends asked me: Design a site in the end how many live, a common site specific need to design how many pages?

I replied: Generally there will not be more than 30 pages; in fact, all the design work is just to design the less than 30 pages, which are almost all of the entire site.

I did not lie to him.

For these 30 pages, we need to make it clear before designing: What kind of people are these pages for? What kind of characteristics do they have? What do we need to give these people the feeling of the page thing? (The above is basically user research, product and data analysis, conceptual design to solve things, we have just written in the previous installments).

Then we need to start the concrete design ...

First, to resolve:

1, for the role of product services, the entire product needs those functional points.

2. What is the relationship between function and function, this is called product structure. Menutree.

3, each function point will eventually be the image of a page;

4, this page should have what content? (a page will include n function points), this page is mainly for that or those role services 5, the content of this page to be placed.

Then, to resolve: what is the relationship between the page and the page, how to interact, how the details behave ...

In this article we only say "first thing to solve", which is what we normally do in the "Information architecture design" phase.

Functional Structure Design:

1, for the role of product services, the entire product needs those function point 2, function and function of the relationship between what is called the product structure. Menutree. In general, I suggest that designers design this menutree according to possible product navigation ideas, and that the output of functional structure can be directly converted to product navigation. Because doing so helps to make the design work more predictable later, it also makes the product's functional structure closer to the performance layer structure that the user sees.

We may be able to do this in a card way, such as the following:

or use Word, Excel, for example:

Here's what to note:

1, the product needs those function point must from the role angle to ponder

2, can take care of the background of the data structure and logic, but not limited by the data structure to design functional structure

3, users do not know what the bottom of the product looks like, they only see the performance layer. So the higher the performance layer and the bottom line, the better the architecture of the product. That is to say, "The structure of the function tree is best equal to the structure of the navigation menu."

4, the product needs a certain accumulation period, at first not all can think of the function all want a brain to do all, do fine, but must think of the function upgrade when the ductility.

5, we do not need to do very meticulous, only need to frame a good overall framework can be.

Page structure Design:

4, this page should have what content? (a page will include n function points), this page is mainly for that or those role services

5, the content of this page to be placed.

The content information of the page needs to refer to the information of Menutree, how each page is placed is the main content of the page structure design.

When working with experienced designers, we draw simple prototypes on a piece of paper and then decide where to put them through repeated discussions.

Usually when working with a designer who is not very skilled, we will use PPT or PS to step by step implementation of these content, first the contents are listed, and then consider where they put, and then consider how much space they occupy, and finally concrete implementation to the main module of the specific way to show.

For example, the following figure:

Here's what to note:

1, generally recommended not to design the first page to design a level two or three page, from inside to outside the design will be more targeted.

Most of the time level two page content will be all of its three level of refinement, the content of the home page will be all level two content of the extraction. The user is from outside to look inside, but we should design from inside to outside ...

2, as little as possible or not to consider the interaction between the page and how to jump. Just follow the functional structure to design the structure of each page.

3, in addition to a lot of pages need a common module and the main module of the page, you need to consider the specific way of showing, but also need not think "Finally must follow this display to do", other pages are not too much depth to the details.

This article is relatively shallow, a general description of my experience in the design of the information architecture design phase of the main content of the work, the specific principles of work have been thinking about the content, and welcome to focus on the topic of other authors of the article.