Re: What do you call policy/process/procedure structure?

[Monique Semp <monique -dot- semp -at- earthlink -dot- net>]

   Hmm... Decades ago, when we wrote 20-page doc plans for projects, we
   included those things that you've mentioned: doc types, structure of
   them, format/header/footer requirements, reviewer rules, and much, much
   more. So I do not think of any of that as "way outside standard tech
   writing stuff." Now given today's "agile" world and the fact that we
   largely work from checklists these days, especially in docs-as-code
   environments where our "doc plans" are basically JIRA tickets, GitHub
   issues, Trello cards and the like, yeah -- that sort of thing does
   often fall through the cracks. But that doesn't mean that it's not
   regular tech writing.

   On 4/21/20 2:39 PM, Shari Punyon wrote:

Way outside standard "tech writing stuff"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives