Volunteering for the TCBOKThis is a project that relies entirely on our volunteers. We would be thrilled if you joined us. Why volunteer?If you are an experienced technical communicator, you you get the pleasure of sharing that your knowledge and experience and working with younger professionals. If you are new to the profession, this is your chance to learn more about it and to work with senior professionals. Your contribution will be acknowledged on our Roll of Honor (unless you prefer to remain anonymous). If you wish, we will link your entry to a web site of your choice. Adopt a TopicStarting at Summit 2010, we are asking you to 'Adopt a Topic'. Many people volunteered at Summit, but we still need more help. If you would like to Adopt a Topic, then please send an email to Volunteer4BoK@stc.org. Include your name, your email address and any other contact details, and the topic that you'd like to adopt. Want to do more than a few topics?If you would like to volunteer for even more involvement, please:
How to contributeAnyone can comment on pages:
To edit pages on the web site:
Wiki Technical
Our Wiki Technical page has tips on how to add or change pages, and how to add users. Wiki StandardsIf you are new to Wikis, or want to brush up on your Wiki etiquette, then visit the Wiki Standards section. These were developed by a group of graduate students working with Dr. Marjorie Davis. You'll see their credits on each page.You will also see references to the specifics of Dr D's classes. Let us know if you think these standards should be adopted for the ongoing TCBOK project. Wiki 'Sandbox'The 'Sandbox' area is set aside for you to experiment with. The term 'sandbox' comes from a play area that's popular with many US children, and in some other countries. It means: play, enjoy, don't worry about the consequences. We'd also like to credit Marj's group with having the idea for the Sandbox. |
Comments
I volunteered to contribute content about using wikis for user documentation. I attended the STC Summit 2010 in Dallas last week and also signed up on the bulletin board. I'm a little lost without a left-hand navigation pane on all the pages for the entire site. I set this up with the Confluence wiki, and Mindtouch does this as well. I'm going to look at EditMe's site to see if it's possible. Does anyone else feel this way?
Happy to help. I have been writing and implementing technology solutions for about 16 years now. For the time being I'd just like to offer editorial support until I get more of a feel for how the project is developing. I don't want to put an email address online. Contact me on Linked-In or Mark Clifford has my email. Thanks.
This is a greate idea and good exposure for people new to the Wiki approach.
Todd Breeding
toddb@ti.com
I took a brief look at the TC BoK outline. I can imagine a few revisions to that outline. I'm interested about which parts of the present outline are considered the most "stable." Also, I think that a Wiki approach, with proper oversight, could work as the approach for populating relatively quickly the more "stable" parts of the outline, but the word needs to get out and the rewards for participating must be promoted. niche blueprint 2.0 | click here
I would like to volunteer for a support slot. I can be a content developer, editor, researcher or reviewer. My email is andrewcornell@cableone.net. I am working on a portfolio for a masters degree in technical communications. My background is technical and the project will allow me to learn more about technical communications. I have the time to dedicate myself to the project. To review my credentials, you can view my resume on STC and LinkedIn. I have experience in product support.
I would like to volunteer. My e-mail address is davidjdick2000@yahoo.com
I, too, would like to help in some way with this activity. I am a TC with nearly 20 years of experience in technical training and instructional design, technical writing, technical editing, help development, and Web site strategy. I don't have a specific recommendation as to how I can help. I simply see the need for the BoK and hope that you can specify areas where you need assistance.
I took a brief look at the TC BoK outline. I can imagine a few revisions to that outline. I'm interested about which parts of the present outline are considered the most "stable." Also, I think that a Wiki approach, with proper oversight, could work as the approach for populating relatively quickly the more "stable" parts of the outline, but the word needs to get out and the rewards for participating must be promoted. I did not attend 2009 STC national meeting but have attended several in the past. I have >20 years of TW and TE experience, mostly authoring software product documentation for developers. I would be interested in contributing my efforts to the project.
Paul Sholar (Santa Monica, Calif., USA) sholarpk@gmail.com
I'm interested in helping to think about issues in developing a TC BOK. I'm a professor in the field, had discussed a TC BOK many times with Ken Rainey, who argued for one so eloquently, have followed closely the failures that have left the UPA Body of Knowledge project idle (stuck?) for years, and for the past eight years I've run the EServer Technical Communication Library, wrestling with issues of taxonomy and categorization within the tech comm field(s). I've also taught both graduate and undergraduate courses in a range of TC areas.
Name: Geoffrey Sauer (geoff@eserver.org)
Communities: Central Iowa and ISU Student chapters
I would be happy to help out any way I can. I've worked primarily in instructional design and software documentation (online help, etc.) over the last 15 years, so I can help with the Career Path sections on those areas. I also have an interest in scientific, environment, and medical writing, although not first-hand knowledge. Our company uses goals and metrics pretty extensively, so I may be able to help with the Value Proposition part. Happy to help out anyway I can. You can reach me at mica_wrensong@hotmail.com (personal e-mail). Thanks!
Hi Caroline and team! I would also like to help with the BOK. My e-mail address is deb_lockwood@csgsystems.com. Like Marella, I am a member of the Rocky Mountain Chapter, and belong to two SIGs: Lone Writer and CIC.
Deb Lockwood
Thanks Marella.
I have transferred your personal contact details to my computer and sent you a 'welcome to the project' message.
I would like to help with this project. I am a technical editor and would be able to edit pages. I would also like to add content, specifically in the History of Techncial Communication, as I have been a technical communicator for 27 years.
Name: Marella Colyvas
Community: Rocky Mountain