[Axure Notes] 9. About naming conventions: pages, components and groups.

Open Axure, click summary in the upper left corner, and see if there are a bunch of "(shapes)" (combinations) "(rectangles)" (pictures) "Lorem ipsum"? If it's just a few pages of simple prototypes, it's harmless to use the default naming, but once we start to make high-fidelity prototypes, the importance of standardized naming is self-evident, because there are often many identical or similar components we need when writing interactions, and if the naming is incorrect and unclear, it's easy to get confused and lead to logical errors (and in the existing Axure debugging method, it's very troublesome to give this logical error caused by choosing the wrong component to others for viewing and debugging). In other words, Internet giants have their own detailed specifications to follow when making prototypes. Not only should the product documents made by different product managers be as readable as possible and easy to develop, but also when the same product document is taken over by multiple product managers, communication costs will be reduced and work efficiency will be improved.

The following are my own views on naming:

1.？ The naming of pages is best described by actual function+page, and different functions under the same page are suggested to be divided and marked with "-". For example, we can name LoginPage loginpage, and the SMS verification code page included in the login page can be named LoginPage-SMS, which is clear and clear. Why not use a simpler way of writing login-SMS? Although the Page name in Axure may only be used when opening a page and calling a function, in order to avoid overlapping with the component name, it is recommended that all pages be marked with the word page for easy identification.

2.？ It is not recommended to use Chinese for all components and page names. If English is really difficult, you can try phonetic notation. Although Axure is very supportive of Chinese variable names in my opinion, it is still not recommended to use Chinese anywhere involving logic to avoid some unknown mistakes.

3.？ Component names can be written in the form of big hump (Pascal nomenclature) or Hungarian nomenclature. Personally, I am used to Pascal's nomenclature (that is, the first letter of each word is capitalized). Although Hungary's nomenclature is intuitive and easy to classify, Pascal's nomenclature is simple and easy to type, which suits me better.

4.？ When naming components, it is suggested to name them in the way of "function+attribute", such as BackButton, DeleteButton, dynamic panel with friend list, AvatarReapter, main unit of friend list, etc. In this way, when we are looking for the corresponding components for logical writing, we can quickly and accurately find the components we need through the search function or name of the search box, avoiding flipping through the list over and over again.

5.？ For naming global variables, it is suggested to use an easy-to-understand "function description". For example, when using this variable, the name of the page where the record jumps to the album can be called "WhoCalledAlbumPage" intuitively, which is better than Var 1, v11,and global Var65438.

6.？ If there are many pages and components, please use the grouping function to group them. The shortcut key is simple. Select the corresponding pages and components, and then press cmd+g .. The grouping of pages is generally determined by functional division. For example, the unified grouping of pages BeforeLogin is "Befo Relogin" and the unified grouping of Chat pages is "Chat". However, the grouping of components is more flexible. Because of the use of the component library, it can often be grouped together. This is harmless. I often use buttons, panels, functions and logic to determine grouping. The specific situation needs specific analysis, so I won't go into details here.

Through reasonable naming and grouping, we can save a lot of time in looking for components when making prototypes, and at the same time greatly improve the utilization rate of this component for others. Please pay more attention to naming grouping in your daily work and study, and develop good naming habits.

——————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

Chapter 1

Preparation before starting

1.？ It is written in the front. Why should I open pit Axure?

2.？ It is hooliganism to learn directly from a product without a complete idea.

3.？ Think twice before you act: high fidelity or low fidelity?

4. We still need to know a little about the relevant specifications of the mobile terminal.

Chapter? 2

Here we go, beginner's stupid question:

5.？ Standing on the shoulders of giants: first install a component library.

6.？ More skills are not heavy, but more components are really heavy.

7. Text boxes and text fields: How to get the input text?

8. How to use URLs and variables to link pages and jump?

9.？ About naming conventions: pages, components, groups.

10. When should I use the dynamic panel?

1 1.？ When should I use a repeater?

12. Interaction, variables and functions. How should I start studying?

13. The last line of defense in interactive situations

chapter three

Practical courses to be continued. ...