Difference between revisions of "Complexity"
Jump to navigation
Jump to search
Line 26: | Line 26: | ||
If you want to contribute, click [http://mailto:info@lehmannmax.de here] to get in touch. | If you want to contribute, click [http://mailto:info@lehmannmax.de here] to get in touch. | ||
− | ==[[Complexity_References|Reference Collections for | + | ==[[Complexity_References|Reference Collections for Complexity]]== |
===[[Compatibility_References#General|General]]=== | ===[[Compatibility_References#General|General]]=== | ||
===[[Compatibility_References#Dividing_Processes|Dividing Processes]]=== | ===[[Compatibility_References#Dividing_Processes|Dividing Processes]]=== |
Revision as of 11:20, 5 April 2021
headline | Complexity |
---|---|
headline coordinates | 32.980, 290.903, 0.000 |
image | img/img.link |
image coordinates | 0, 0, 0 |
simple introduction |
|
simple introduction coordinates | 0, 0, 0 |
testimonial | It seems that there is no testimonial for this topic yet. If you want to contribute, click here to get in touch. |
testimonial coordinates | 0, 0, 0 |
links to | |
belongs to | attention |
contains | Complexity_References |
simple introduction
- This part is about handling complex content or processes
- Extensive or complex content can be better understood if it is broken down into seperate parts.
- Long processes that require user input should, if possible, be divided into multiple simpler processes.
- If that is not possible, it is recommended to offer a saving function that allows users to pause a process and resume it later without losses.
testimonial
It seems that there is no testimonial for this topic yet.
If you want to contribute, click here to get in touch.