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":6977,"date":"2014-07-10T08:08:51","date_gmt":"2014-07-10T07:08:51","guid":{"rendered":"http:\/\/www.cherryleaf.com\/blog\/?p=6977"},"modified":"2014-07-10T08:08:51","modified_gmt":"2014-07-10T07:08:51","slug":"our-webinar-in-august-will-be-from-technical-communication-to-content-strategy","status":"publish","type":"post","link":"https:\/\/www.cherryleaf.com\/2014\/07\/our-webinar-in-august-will-be-from-technical-communication-to-content-strategy\/","title":{"rendered":"Our Webinar in August will be: From Technical Communication to Content Strategy"},"content":{"rendered":"

MadCap Software has asked me to present, as a webinar, one of my conference presentations from the \u00a0MadWorld 2014 conference –\u00a0Bust a Move: From Technical Communication to Content Strategy<\/a>.<\/p>\n

In this webinar, we’ll look at how technical communicators can get more involved in corporate content strategy. We’ll look at why they might want to do that, the differences between technical communication and content strategy, as well as looking at how they might re-position themselves. We’ll also look at what tools and skills technical communicators can bring across from the technical communications field.<\/p>\n

It was a popular session at the conference, standing room only in fact, with 20 minutes of questions from the audience at the end.<\/p>\n

This webinar will be held on the 12th August at 4.00pm BST\u00a0(8:00 am Pacific Time), and it’s a free event.<\/p>\n