Home  >  Article  >  Web Front-end  >  Rules for registration form design_HTML/Xhtml_Web page production

Rules for registration form design_HTML/Xhtml_Web page production

WBOY
WBOYOriginal
2016-05-16 16:46:011309browse
"Patterns for Sign Up &Ramp Up"I finished reading it very early. The reason why I am writing my review today is that after reading it carefully, I found that it is closer to a community building guide that attracts registrations and increases activity. A good resource for research on community active membership.
Since I agreed to write my thoughts after reading it, let me talk about something related to registration from my perspective. I will first decompose the skeleton of the entire material, and then talk about my current feelings based on the viewpoints.
Registration is actually a bit boring task. The point mentioned in "Patterns for Sign Up &Ramp Up" is:
Give the user good reasons to join
At first glance it seems a bit like marketing. The essence of things remains unchanged, but people’s emotions can be reversed - give users good reasons to join register;
Make the sign-up process feel effortless
Changing the boring and boring feeling is what we need to do: make the form or the entire registration process easy and effortless;
Don't leave new users hanging
The significance of this point of view in the entire material focuses on ways to increase activity - users do not complete the mission after completing the registration, understand the community Something new has just begun;
Accelerate initial connection-making
If activity kicks off from the previous point, then here is how to enable users to start living in the community and establish connections, such as through the information they have previously posted. Come and connect with your friends, and truly experience the feeling of having close friends across the sea, and feeling like you are neighbors across the world.
The skeleton structure of the entire article is a step-by-step behavioral guidance. It provides detailed annotations and guidance for the initial guidance of introducing members to Facebook and maintaining an active community. You can refer to the manual. After reading, focus on the summary of the work and sort out a few rules for the registration form:
    When the form structure requires multiple steps, it is important to provide clear navigation Use a progress ruler to tell users their current position and overall steps Emphasize the logical connections among several steps, such as marking: step1, step2, step3 Explain the steps with meaningful pictures or ICONs or even titles Use simple language or the second person to describe actions Logical steps are best limited to 3 steps Prompts for user registration behavior
      Tips should appear where help is needed or where there is a connection between actions. Encouragement to users should be reflected in the process, such as prompting a tick icon for each completed input item. Try to avoid pop-up warning reminders ICON's error message avoids using warning expressions to make users feel frustrated. Simple and easy-to-recognize ICONs to mark prompts, success, and error styles If there is an error when submitting the form, it is best to display an error reminder at the head of the entire form to guide the user to make corrections.
    About copywriting Quality is more important than quantity. Point out the highlights rather than list them flatly. Try to avoid copywriting with special meanings. If there are exclusive nouns, please explain them clearly to avoid user confusion. Try to think about the highlights of the copywriting surface and what is most attractive to users. Sometimes the words "latest" may not necessarily be what users are most interested in. In our previous projects, multiple data and practices have highlighted that copywriting is really important. Layout of the form Try to use aligned fields, equal-length input boxes, and consistent visual styles to reduce visual clutter. Try to limit the number of fields and input boxes to 3-6 on one screen (mostly used in multi-step situations) If there are optional and required fields, indicate the difference. Classify information about different concepts and separate optional and required fields as much as possible

These general rules for form design are also covered in the full explanation of forms by LukeW from Yahoo in the United States. They are the most commonly used. I will summarize them for students’ reference. There are still many guides on activity that can be explored in depth. point. It is not listed here and will be left for subsequent decomposition.
Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn