OSE Instructional Guidelines: Difference between revisions
Jump to navigation
Jump to search
(Created page with "The key principle for OSE instructionals is: #Create instructionals at the module level, not at the machine level. This way, we can document builds by reusing module instruct...") |
No edit summary |
||
| Line 1: | Line 1: | ||
The key principle for OSE instructionals is: | The key principle for OSE instructionals is: | ||
'''Create instructionals at the module level, not at the machine level. This way, we can document builds by reusing module instructionals. ''' | |||
OSE already does it in some way, and the need for this emerges clearly as the number of products that we document grows. We can reuse an entire instructional - and then make a small modification to it - to create a new instructional. | OSE already does it in some way, and the need for this emerges clearly as the number of products that we document grows. We can reuse an entire instructional - and then make a small modification to it - to create a new instructional. | ||
Revision as of 18:37, 27 August 2020
The key principle for OSE instructionals is:
Create instructionals at the module level, not at the machine level. This way, we can document builds by reusing module instructionals.
OSE already does it in some way, and the need for this emerges clearly as the number of products that we document grows. We can reuse an entire instructional - and then make a small modification to it - to create a new instructional.