Habit 2: Adhering to a structure
Once you have original material, how do you write them into a pattern (FORM)?
Ok, first, don't assume that there is only one form of form. No form is suitable for everyone. Some people like to be more universal (Prosey) style like Alexander. Other well-grained methods like "Fine-grained) methods used in << Design Mode >>. There are also some use of completely different structures. The features shared by these structures are only their structure.
If there is a famous term, it will be Alexandriancan: a model is "A Solutionto a Problem IN a Context). Now I am very bold to modify this definition: a pattern is a clear detained detail explanation for a specific solution to a particular environment. The mode has a part of the recognizable, which guides their applications and comparisons. These parts include a name, a statement, environment and solution amendments, and solution itself. This is basically the structure of the Alexander mode. Our model further breaks these basic elements into more centralized processing, such as "applicability", "participant", and "effect" section. The 1994 Mode Language Programming (PLOP) process meeting included a surprising change of these topics.
Therefore, the first step of writing mode written on paper is to determine its structure. The more information on your pattern, the more important your structure is. The consistent structure makes the pattern uniform, making people more easily compare them. The structure also helps people search information. Less structures mean more common (pro), which may be more suitable for leisure reading, but may not be accepted for comparison and reference destination.
Once you have determined a structure, make sure you will consistently abide by it. You don't have to be afraid to change the structure, but you have to change it in each mode, and this will become more cost-effective after your pattern matures.
