�ݺ�ߣshows by User: maryfconnor

�ݺ�ߣshows by User: maryfconnor / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: maryfconnor / Thu, 02 Feb 2017 02:10:42 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: maryfconnor Structuring for Content Reuse with MadCap Doc-To-Help /maryfconnor/structuring-for-content-reuse-with-madcap-doctohelp 2017structuringforcontentreusewithd2h-170202021042
MadCap Doc-To-Help scales Microsoft® Word to enterprise class, making it easy to reuse content across documentation and training deliverables. It takes serious standardizing and structuring of content, however, to get there, with strategic considerations and choices. This presentation walks you all the way from migrating non-Doc-To-Help source file types through structuring files for topic-based assembly. Learn the skills, tricks, and trade-offs that will let your nimble Doc-To-Help platform help you thrive in an under-resourced, just-in-time production environment. http://www.doctohelp.com/resources/recorded-webinars.aspx]]>
MadCap Doc-To-Help scales Microsoft® Word to enterprise class, making it easy to reuse content across documentation and training deliverables. It takes serious standardizing and structuring of content, however, to get there, with strategic considerations and choices. This presentation walks you all the way from migrating non-Doc-To-Help source file types through structuring files for topic-based assembly. Learn the skills, tricks, and trade-offs that will let your nimble Doc-To-Help platform help you thrive in an under-resourced, just-in-time production environment. http://www.doctohelp.com/resources/recorded-webinars.aspx]]> Thu, 02 Feb 2017 02:10:42 GMT /maryfconnor/structuring-for-content-reuse-with-madcap-doctohelp maryfconnor@slideshare.net(maryfconnor) Structuring for Content Reuse with MadCap Doc-To-Help maryfconnor MadCap Doc-To-Help scales Microsoft® Word to enterprise class, making it easy to reuse content across documentation and training deliverables. It takes serious standardizing and structuring of content, however, to get there, with strategic considerations and choices. This presentation walks you all the way from migrating non-Doc-To-Help source file types through structuring files for topic-based assembly. Learn the skills, tricks, and trade-offs that will let your nimble Doc-To-Help platform help you thrive in an under-resourced, just-in-time production environment. http://www.doctohelp.com/resources/recorded-webinars.aspx <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2017structuringforcontentreusewithd2h-170202021042-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> MadCap Doc-To-Help scales Microsoft® Word to enterprise class, making it easy to reuse content across documentation and training deliverables. It takes serious standardizing and structuring of content, however, to get there, with strategic considerations and choices. This presentation walks you all the way from migrating non-Doc-To-Help source file types through structuring files for topic-based assembly. Learn the skills, tricks, and trade-offs that will let your nimble Doc-To-Help platform help you thrive in an under-resourced, just-in-time production environment. http://www.doctohelp.com/resources/recorded-webinars.aspx

Structuring for Content Reuse with MadCap Doc-To-Help from Mary Connor

]]> 495 6 https://cdn.slidesharecdn.com/ss_thumbnails/2017structuringforcontentreusewithd2h-170202021042-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 DocOps: Documentation at the Speed of Agile /slideshow/docops-documentation-at-the-speed-of-agile/62483545 docops-160528004946
Presented at Keep Austin Agile 2016: How to we make documentation "Agile", given the Agile Manifesto? How do you get into the Definition of Done? What does "DocOps" mean, in the simplest and broadest terms? What should your requirements be for a DocOps transformation, and how do you find a tool stack that fits them? Where do you start, and how do you escape a waterfall reengineering of your legacy docs?]]>
Presented at Keep Austin Agile 2016: How to we make documentation "Agile", given the Agile Manifesto? How do you get into the Definition of Done? What does "DocOps" mean, in the simplest and broadest terms? What should your requirements be for a DocOps transformation, and how do you find a tool stack that fits them? Where do you start, and how do you escape a waterfall reengineering of your legacy docs?]]> Sat, 28 May 2016 00:49:46 GMT /slideshow/docops-documentation-at-the-speed-of-agile/62483545 maryfconnor@slideshare.net(maryfconnor) DocOps: Documentation at the Speed of Agile maryfconnor Presented at Keep Austin Agile 2016: How to we make documentation "Agile", given the Agile Manifesto? How do you get into the Definition of Done? What does "DocOps" mean, in the simplest and broadest terms? What should your requirements be for a DocOps transformation, and how do you find a tool stack that fits them? Where do you start, and how do you escape a waterfall reengineering of your legacy docs? <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/docops-160528004946-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> Presented at Keep Austin Agile 2016: How to we make documentation "Agile", given the Agile Manifesto? How do you get into the Definition of Done? What does "DocOps" mean, in the simplest and broadest terms? What should your requirements be for a DocOps transformation, and how do you find a tool stack that fits them? Where do you start, and how do you escape a waterfall reengineering of your legacy docs?

DocOps: Documentation at the Speed of Agile from Mary Connor

]]> 2918 9 https://cdn.slidesharecdn.com/ss_thumbnails/docops-160528004946-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 2015 WritersUA Sourcing Graphics /slideshow/2015-writersua-sourcing-graphics/43303958 2015-01writersuasourcing-graphics-150107212223-conversion-gate01
For the January 2015 Software User Assistance Conference, this session covers single-sourcing and cloud-sourcing tips, as well as techniques for maximizing graphical appeal and automating graphic generation.]]>
For the January 2015 Software User Assistance Conference, this session covers single-sourcing and cloud-sourcing tips, as well as techniques for maximizing graphical appeal and automating graphic generation.]]> Wed, 07 Jan 2015 21:22:23 GMT /slideshow/2015-writersua-sourcing-graphics/43303958 maryfconnor@slideshare.net(maryfconnor) 2015 WritersUA Sourcing Graphics maryfconnor For the January 2015 Software User Assistance Conference, this session covers single-sourcing and cloud-sourcing tips, as well as techniques for maximizing graphical appeal and automating graphic generation. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2015-01writersuasourcing-graphics-150107212223-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> For the January 2015 Software User Assistance Conference, this session covers single-sourcing and cloud-sourcing tips, as well as techniques for maximizing graphical appeal and automating graphic generation.

2015 WritersUA Sourcing Graphics from Mary Connor

]]> 557 1 https://cdn.slidesharecdn.com/ss_thumbnails/2015-01writersuasourcing-graphics-150107212223-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 LavaCon 2011: Double Trouble! Adding Developer Docs to Your Deliverables /maryfconnor/2011-lava-conconnorbleiel 2011-lavaconconnor-bleiel-111104215624-phpapp02
Speakers: Mary Connor and Nicky Bleiel Here is how one team added new developer documentation to its already long list of end-user deliverables, with no additional headcount, tools, or resources. Our next-generation product combines web controls with web services, and the API for those web services has to be documented for both internal and third-party developers. Having just migrated our legacy user documentation to Doc-To-Help to solve Agile authoring problems, we were able to leverage its API-generation feature to automate builds of the references we needed. Doc-To-Help lets us share authorship of developer documentation in easy, familiar formats and reuse that content among user docs, context-sensitive Help files, training materials, and websites.]]>
Speakers: Mary Connor and Nicky Bleiel Here is how one team added new developer documentation to its already long list of end-user deliverables, with no additional headcount, tools, or resources. Our next-generation product combines web controls with web services, and the API for those web services has to be documented for both internal and third-party developers. Having just migrated our legacy user documentation to Doc-To-Help to solve Agile authoring problems, we were able to leverage its API-generation feature to automate builds of the references we needed. Doc-To-Help lets us share authorship of developer documentation in easy, familiar formats and reuse that content among user docs, context-sensitive Help files, training materials, and websites.]]> Fri, 04 Nov 2011 21:56:21 GMT /maryfconnor/2011-lava-conconnorbleiel maryfconnor@slideshare.net(maryfconnor) LavaCon 2011: Double Trouble! Adding Developer Docs to Your Deliverables maryfconnor Speakers: Mary Connor and Nicky Bleiel Here is how one team added new developer documentation to its already long list of end-user deliverables, with no additional headcount, tools, or resources. Our next-generation product combines web controls with web services, and the API for those web services has to be documented for both internal and third-party developers. Having just migrated our legacy user documentation to Doc-To-Help to solve Agile authoring problems, we were able to leverage its API-generation feature to automate builds of the references we needed. Doc-To-Help lets us share authorship of developer documentation in easy, familiar formats and reuse that content among user docs, context-sensitive Help files, training materials, and websites. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2011-lavaconconnor-bleiel-111104215624-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> Speakers: Mary Connor and Nicky Bleiel Here is how one team added new developer documentation to its already long list of end-user deliverables, with no additional headcount, tools, or resources. Our next-generation product combines web controls with web services, and the API for those web services has to be documented for both internal and third-party developers. Having just migrated our legacy user documentation to Doc-To-Help to solve Agile authoring problems, we were able to leverage its API-generation feature to automate builds of the references we needed. Doc-To-Help lets us share authorship of developer documentation in easy, familiar formats and reuse that content among user docs, context-sensitive Help files, training materials, and websites.

LavaCon 2011: Double Trouble! Adding Developer Docs to Your Deliverables from Mary Connor

]]> 2416 10 https://cdn.slidesharecdn.com/ss_thumbnails/2011-lavaconconnor-bleiel-111104215624-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-maryfconnor-48x48.jpg?cb=1689274193 Since bailing on her Ph.D. in English and a life grading papers 20 years ago, Mary has been designing technical documentation in high tech, focusing on Agile documentation since 2008. Currently writing for Caringo (object storage technology), she has created developer documentation for cloud-based API services at Telogis and several generations of web service products at Advanced Solutions. She works to build authoring environments that free Agile teams to write and diagram information as easily as they code. www.cleverhamster.com https://cdn.slidesharecdn.com/ss_thumbnails/2017structuringforcontentreusewithd2h-170202021042-thumbnail.jpg?width=320&height=320&fit=bounds maryfconnor/structuring-for-content-reuse-with-madcap-doctohelp Structuring for Conten... https://cdn.slidesharecdn.com/ss_thumbnails/docops-160528004946-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/docops-documentation-at-the-speed-of-agile/62483545 DocOps: Documentation ... https://cdn.slidesharecdn.com/ss_thumbnails/2015-01writersuasourcing-graphics-150107212223-conversion-gate01-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/2015-writersua-sourcing-graphics/43303958 2015 WritersUA Sourcin...