Renewed enthusiasm: What Web refactoring is doing

The purpose of this title is simple, is to let us day after day in the code page of the Web refactoring workers, to regain the enthusiasm of the industry to face this we love; Examine the primary mistakes that are often overlooked by us in tedious work; take each page with enthusiasm and passion. It's basically what I want to say and need to reexamine, and I want to be a little guide to new people who are just starting out.

In general, to receive a new demand, with simple less page requirements as an example, the process can be simply divided into several major stages:

1. View the design draft, read the requirements document, prototype map;

2. View and analyze the design draft, in the brain to organize a rough solution;

3. Chettu and merging pictures;

4. Write HTML code, CSS code;

5. Check browser compatibility;

6. Compare the design draft, check the reduction degree;

7. The development of the joint adjustment, test solution bugs, on-line and then confirm the page without bugs.

Ideally, following the process step-by-step, it is very smooth to deal with the requirements and then perfect the line, refactoring the work done to some extent is also considered relative to the designer is not bitter force. But there are a lot of things that we have to face often, and more work involved may include:

1. Changes in requirements, including modification of the design manuscript and reconstruction of the static page directly processed;

2. Adapt to the original dynamic module HTML structure of the style rewrite;

3. Multi-platform debugging, such as PC client embedded, mobile client;

4. Various or unknown or difficult situations.

Suppose one: the demand is ambiguous, the person in charge changes several times, the design draft content is short and no prototype draft.

If it is only one of three possible, the demand is not clear to find the person responsible for confirmation, the person in charge can see the requirements of the document, the design is not all can find a designer to fill. If it happened at the same time encountered such a mess, even worse designers do not know where to go, the demand side to rush to the line, responsible people are annoyed can only hurriedly throw out the messy. It is obviously not advisable to be as irritable as they are at such times, be responsible for your project again, right, demand to you is your project no matter who he hangs the name of the end of the page was scolded to be ridiculed can you be happy to laugh together.

The most to do, first of all is to clarify what this project is a thing, what to do, what needs to be implemented, since no one can clarify this process, their own learning is also a skill of carding. Also, no longer irritable with the person in charge, a rope on the grasshopper who is not good, mutual understanding can achieve each other's gratitude and respect. Of course, appropriate to the point of the horse, you said to rush the line to you to do overtime, the demand side (the head or customers) dissatisfied with the idea of a pile of changes to toss, but also to trouble the responsible person to reflect their own neglect of the process. Finally, with peace of mind, quietly to complete the project.

Hypothetical case two: Thunderbolt look at the comment module

The comment module can be said to look at one of the important and unique data, the root of which is looking at the official website, easy to change the structure requires the background to recreate a set of templates and re-enter content, then also means that if you need to invoke comments must adhere to the original structure. This kind of situation is a little painful for the reconstruction of novelty and change, but if you think of it differently, the same structure relies on CSS to transform a colorful form, which is not one of the challenges of ability. Snow Secret Fan Official website for example, a small comment module plus the border rounded corners and the mouse after the transformation of the effect is not a lot of movement ~ Dot I watch

Assumption three: Requirements are embedded in the Thunderbolt 7 client application Plug-ins

The domestic software embedded browser on the Windows platform has not yet seen the non-ie core (if you have seen the Welcome to share), the Thunderbolt 7 embedded browser is the native browser version, but only IE6, IE7 (7 and above version are used IE7).

For the client to embed the page to consider some special circumstances, such as:

7.2 Before the Thunder version of the application plug-in, compared to the size of the full screen of the browser can be smaller, in order to achieve close to the actual display of the effect of the browser scaling is a good idea, the recommended Firefox plug-in Web Developer, the menu window size can be customized for a variety of sizes to facilitate debugging. Speaking of browser window size must be mentioned is often overlooked a compatibility point, that is, the browser is not full-screen state background is truncated, the following figure

Even if the browser scaling on your PC can be ignored, don't forget that it's a less-than-beautiful experience when you don't have to slide all the way through the screen to see the entire page.

PS: On the mobile platform is limited space for a while, I will continue to introduce in the following article:

Scenario four: Occasionally interspersed with emergency modifications and you've got three or four needs in hand, all sorts of messy inclusions

Busy daytime RTX will ring for a while this topic helps to see this problem, a meeting hall that mall need to add something ... Take care of this may be missing over there need to change the width of the small point directly thrown out, did not look over there to develop products together with the clamor to rush the online AH hair version ah ... Notes under the column under the project, delivery time, modify the main points, to be thoughtful questions such as comments appear to be very necessary, paper and pen to take on the way to practice calligraphy, save the careless many words will not write ~

Think back to what the Web refactoring is doing to this end, welcome to discuss the exchange, you can not agree with my point of view and raise objections, I would like to die for you to defend this right and is willing to come to a war.

Article Source: Thunder User Experience Design Center