Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sites/cherryleaf.com/public_html/wp-includes/functions.php on line 6114
Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":11792,"date":"2017-02-23T15:32:44","date_gmt":"2017-02-23T14:32:44","guid":{"rendered":"https:\/\/www.cherryleaf.com\/blog\/?p=9842"},"modified":"2017-02-23T15:32:44","modified_gmt":"2017-02-23T14:32:44","slug":"documentation-dirty-word","status":"publish","type":"post","link":"https:\/\/www.cherryleaf.com\/2017\/02\/documentation-dirty-word\/","title":{"rendered":"Is documentation a dirty word?"},"content":{"rendered":"
Daryl Colquhoun has written an article in tcWorld about the international standard ISO\/IEC\/IEEE 26512. He explained\u00a0the standard is going to be revised and renamed: from \u201cSystems and software engineering – Requirements for managers of user documentation<\/em>\u201d to\u00a0\u201cSystems and software engineering – Requirements for managers of information for users<\/em>\u201d.<\/p>\n
The reason for this, he states, is because, in many parts of the world, the term “documentation” is associated with a printed manual only. The neutral term “information for users” refers to all types of content: Online help, audio, video, and Augmented Reality.<\/p>\n
The problem with “information” is it can mean many things. Information for users could mean the weather forecast. We may well need to move away from the word documentation, but I’m not sure we’ve yet come up with a suitable alternative.<\/p>\n