GET /api/v2/video/?page=2
HTTP 200 OK Vary: Accept Content-Type: text/html; charset=utf-8 Allow: GET, POST, HEAD, OPTIONS
{ "count": 83, "next": "http://videos.writethedocs.org/api/v2/video/?page=3", "previous": "http://videos.writethedocs.org/api/v2/video/?page=1", "results": [ { "category": "NA 2015", "language": "English", "slug": "user-story-driven-docs", "speakers": [ "Joao Fernandes" ], "tags": [], "id": 87, "state": 1, "title": "User-Story Driven Docs", "summary": "", "description": "At OutSystems we make an awesome development platform, but our documentation wasn&#39;t that awesome. We focused on describing each button available on the user interface, and not the user intentions and goals.\r\nA clear example of this, was that we had a full documentation page for the find text feature (CTRL+F). It described in excruciating detail every option available on the UI, but didn&#39;t told our users how they could actually find what they needed!\r\nFor us it was a nightmare to maintain the docs. Our development environment was constantly changing and we couldn&#39;t keep up with the changes.\r\nMore importantly, we weren&#39;t meeting the user needs. And that was clear from pages with a single-digit page view, and from the feedback we got from our customers.\r\nDue to this approach, we also ended up having page titles that were feature-oriented, which is not the best for SEO. For instance, the doc page for the find text feature was called &quot;Find Tool&quot;. Who in their right mind would search for that on Google?\r\nIn this talk I&#39;ll tell you the story of how we stopped trying to document the UI, and started creating user-story driven docs. We now focus on what the user wants to achieve and how to achieve it, independently of how many windows or buttons they need to go through.\r\nI&#39;ll cover:\r\nHow you can check if you&#39;re documenting the UI, and why you should avoid doing it\r\nWhy users stories work better for our users\r\nHow focusing on user stories changed the culture of our team and allowed us to work on what really matters.\r\nI&#39;ll also share some unexpected outcomes, like how this lead us to work closer than ever with the development teams. Now our users get twice the cake: better features and better docs!", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/UKY3scPIMd8?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/UKY3scPIMd8?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i.ytimg.com/vi/UKY3scPIMd8/hqdefault.jpg", "duration": 993, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": "http://64966d3674e0a64d8f4a-47c94b14ef8e1f83d5390cdb0629c6ed.r53.cf2.rackcdn.com/wtd-2013/UserStory_Driven_Docs.mp4", "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/MRnZFVCirQM", "whiteboard": "", "recorded": "2015-05-18", "added": "2015-05-20T21:31:38.936", "updated": "2015-05-20T21:52:00.901" }, { "category": "NA 2015", "language": "English", "slug": "writer-meet-tester", "speakers": [ "Arthur Louie", "Jody Bleyle" ], "tags": [], "id": 80, "state": 1, "title": "Writer, Meet Tester", "summary": "", "description": "A software tester can be a tech writer\u2019s best friend, and vice versa. Jody (writer) and Arthur (tester) work together on APIs at Salesforce.com, and we\u2019ll talk about the tools and techniques we use to improve the quality of both our software and our documentation at the same time.\r\nWhile our APIs are still in development, we gather feedback internally. We established an API design review board to approve every API change -- this made a huge difference in ensuring that we offer a consistent, easy-to-consume programmatic interface to our users. We also conduct regular \u201cdogfooding\u201d sessions in which users are provided with draft documentation and asked to find both doc and product bugs.\r\nOur testers created an automated mechanism to alert us of any API changes in case anything slipped past the review board. It\u2019s proven to be invaluable for both doc and testing to keep up with the various teams who are building functionality into the API.\r\nOnce our APIs are publicly available, we take pride in listening to our users in help forums, on Twitter, and through pilot programs. We\u2019ve clarified our documentation and added test cases numerous times based on customer pain points.", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/UKY3scPIMd8?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/UKY3scPIMd8?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i.ytimg.com/vi/UKY3scPIMd8/hqdefault.jpg", "duration": 1692, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": "http://64966d3674e0a64d8f4a-47c94b14ef8e1f83d5390cdb0629c6ed.r53.cf2.rackcdn.com/wtd-2013/Writer_Meet_Tester.mp4", "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://www.youtube.com/watch?v=UKY3scPIMd8", "whiteboard": "", "recorded": "2015-05-18", "added": "2015-05-20T21:31:25.289", "updated": "2015-05-20T21:51:52.082" }, { "category": "NA 2014", "language": "English", "slug": "ditch-your-cms-with-git-and-static-site-generator", "speakers": [ "Patrick Arlt" ], "tags": [], "id": 74, "state": 1, "title": "Ditch Your CMS With Git and Static Site Generators", "summary": "The command line can be your best friend! Git is an amazing tool that helps developers collaborate, review and manage code, but these same tool also work for writing and managing documentation.\r\n\r\nLearn how we use tools like Git, Middleman and Markdown in building and managing the ArcGIS for Developers website (https://developers.arcgis.com). I'll share some Git basics and give some insight into how we do things like create, collaborate and version our documentation all the way up to how the final website is built and deployed.", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/U4qWN3d4_Js?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/U4qWN3d4_Js?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/U4qWN3d4_Js/hqdefault.jpg", "duration": 40, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/U4qWN3d4_Js", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:58:09.982", "updated": "2014-05-25T15:55:17.297" }, { "category": "NA 2014", "language": "English", "slug": "documentation-as-a-product", "speakers": [ "Mark Tattersall" ], "tags": [], "id": 75, "state": 1, "title": "Documentation as a Product", "summary": "\"Write the Docs\" is so often a line item found at the end of a project plan. But documentation deserves so much more attention and thought as good documentation does more than just describe how to use or implement a new feature, particularly in the case of API documentation. It is both the shop window and instruction manual. The tone of the documentation represents your product, and the complexity, simplicity or \u2018magic' needs to shine through.\r\n\r\nMy talk will focus on two objectives:\r\n\r\n1) Why does Documentation deserve product planning on its own?\r\n\r\n2) What do you mean Documentation as a Product?", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/lP5d-O0UySU?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/lP5d-O0UySU?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/lP5d-O0UySU/hqdefault.jpg", "duration": 40, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/lP5d-O0UySU", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:58:11.287", "updated": "2014-05-12T09:08:22.647" }, { "category": "NA 2014", "language": "English", "slug": "dont-write-documentation", "speakers": [ "James Pearson" ], "tags": [], "id": 61, "state": 1, "title": "Don't Write Documentation", "summary": "We can all agree the world is under-documented. However, some of the documentation that currently exists, shouldn't, and it trains users to ignore the other docs we've spent so much time crafting.\r\n\r\nWe'll talk about common documentation traps, including autogenerated text and poka-yoke replacements, and how to recognize and purge them in your own projects to create a better user experience.", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/xUUoG0_0_6Q?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/xUUoG0_0_6Q?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/xUUoG0_0_6Q/hqdefault.jpg", "duration": 20, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/xUUoG0_0_6Q", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:57:52.846", "updated": "2014-05-25T15:55:07.784" }, { "category": "NA 2014", "language": "English", "slug": "instrumentation-as-living-documentation-teaching", "speakers": [ "Brian L. Troutwine" ], "tags": [], "id": 64, "state": 1, "title": "Instrumentation as Living Documentation: Teaching Humans About Complex Systems", "summary": "Human intuition about complex systems is pretty abysmal: we have neither the scope of imagination or the experiences necessary to predict the varied behaviors of our creations. Humans operating these systems--in stable and disaster situations--must rely on a combination of faulty intuition, information coming out of the system and static documentation created by the designers of the system to guide them in their actions. In this talk I will focus on the interaction of instrumentation and static documentation on human operators. In particular, I will contend that by insisting on rich instrumentation system designers will gain a deeper intuition of their work, generating better static documentation and more contextual information for use by operators. I will further contend that this environment is conducive to smooth functioning of the system and creates a culture of constant improvement among the operators and the engineers. \r\n\r\nI will use historical examples and my professional experience to argue this position. \r\n", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/jr7AUb0_bto?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/jr7AUb0_bto?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/jr7AUb0_bto/hqdefault.jpg", "duration": 40, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/jr7AUb0_bto", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:57:56.762", "updated": "2014-05-09T00:29:29.198" }, { "category": "NA 2014", "language": "English", "slug": "make-music-not-noise", "speakers": [ "Christopher Kelleher" ], "tags": [], "id": 62, "state": 1, "title": "Make Music Not Noise", "summary": "Can the values of music guide us to create better documentation? We\u2019ll look at examples of noisy documentation and consider how we can use the noise vs. music distinction to improve the world by documenting it better.\r\n\r\nsound without structure = noise\r\nsound + satisfying structure = music\r\ninformation + satisfying structure = successful documentation\r\n\r\nFirst we\u2019ll examine cases of intentional noise \u2013 documents that are designed to be hard to follow. Think convoluted cable bills or droning usage agreements. This is noise with a purpose: if we give up on following along, the document has done its job because the original goal was to make us surrender, not understand. We\u2019ll talk about how to isolate the noise and demand higher standards.\r\n\r\nAnd then there are documents that mean well but perform badly \u2014 the audience can discern a melody, but it\u2019s either buried or gratingly inconsistent. Examples include tediously detailed consent forms, haphazard project documents, or reports that drift through random facts and jargon. This is the dissonance of badly structured information \u2014 making sound without making sense. Applying a musicality standard can guide authors out of the muck.\r\n", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/37p0dfjGj-w?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/37p0dfjGj-w?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/37p0dfjGj-w/hqdefault.jpg", "duration": 20, "video_ogv_length": null, "video_ogv_url": "", "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": "", "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/37p0dfjGj-w", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:57:54.150", "updated": "2014-05-09T13:59:55.190" }, { "category": "NA 2014", "language": "English", "slug": "more-than-a-reference-better-apis-through-empath", "speakers": [ "Zach Corleissen" ], "tags": [], "id": 72, "state": 1, "title": "More Than a Reference: Better APIs Through Empathy", "summary": "You've probably seen (and maybe even written) API documentation so reference-complete, it puts the OED to shame. Useful API docs cover every endpoint, parameter and variable--but not all API methods deserve equal prominence. \r\n\r\nThis talk is about creating better API documentation through empathy. We'll talk about delighting readers by knowing your audience, showing them where to begin, and explaining why your API matters in the first place.\r\n", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/-z2wlNIAWOQ?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/-z2wlNIAWOQ?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/-z2wlNIAWOQ/hqdefault.jpg", "duration": 20, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/-z2wlNIAWOQ", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:58:07.377", "updated": "2014-05-25T15:55:15.487" }, { "category": "NA 2014", "language": "English", "slug": "putting-the-docs-cart-before-the-standards-horse", "speakers": [ "Drew Jaynes" ], "tags": [], "id": 59, "state": 1, "title": "Putting the (Docs) Cart Before the (Standards) Horse", "summary": "When people think of documentation standards, I'd wager the first thing that comes to mind is probably something like \"uniformity\", or \"best practice\", or \"one voice\". And in consideration of that, most people probably also view standards as the de facto \"starting place\" for all the things to come after.\r\n\r\nSo what happens when you turn that idea on its head, that is to say, 'write the documentation first, and develop standards later'?\r\n\r\nIn the WordPress open source project, we did that. We developed an inline documentation standard using 10 years of contributions as a starting place.\r\n\r\nThis talk will cover some of the challenges we overcame to develop a new standard using legacy documentation.\r\nAlso: \r\n\r\n* Tools we used to assess our existing documentation \"style\".\r\n* How our new standards have been applied in practice.\r\n* How having a standard has allowed the docs team to rise to equal footing.\r\n", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/NiDhWvO6m5Q?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/NiDhWvO6m5Q?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/NiDhWvO6m5Q/hqdefault.jpg", "duration": 20, "video_ogv_length": null, "video_ogv_url": "", "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": "", "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": "", "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": "", "video_flv_download_only": false, "source_url": "http://youtu.be/NiDhWvO6m5Q", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:57:50.214", "updated": "2014-05-25T15:55:05.324" }, { "category": "NA 2014", "language": "English", "slug": "the-new-sheriff-in-town-bringing-documentation-o", "speakers": [ "L.S. Cook" ], "tags": [], "id": 70, "state": 1, "title": "Scale for Support Without Losing Personality", "summary": "It is rarely that a documentarian is brought in at the beginning of a company or project. More commonly, we are called in sometime just before or sometimes slightly after a project is released. We need to hit the ground running, maximize our value, and deliver something before the product is rejected for being undocumented.\r\n\r\nJoin me for a discussion of my techniques and stress-tested questions for how to get minimum viable documentation out of a motley collection of gists, outdated specs, and time-crunched developers. See some immediately-applicable techniques for getting good-enough documentation out the door.\r\n\r\nMy specialty as a technical writer is establishing a minimum viable documentation set, establishing tools and procedures, and training in a less battle-hardened writer to take over. ", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/4vgJvNuhhTc?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/4vgJvNuhhTc?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/4vgJvNuhhTc/hqdefault.jpg", "duration": 15, "video_ogv_length": null, "video_ogv_url": "", "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": "", "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/4vgJvNuhhTc", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:58:04.682", "updated": "2014-05-25T15:55:13.660" }, { "category": "NA 2014", "language": "English", "slug": "strategies-to-fight-documentation-inertia", "speakers": [ "Britta Gustafson" ], "tags": [], "id": 67, "state": 1, "title": "Strategies to Fight Documentation Inertia", "summary": "I'm a non-developer working with a community including a bunch of mostly-volunteer developers, and for years our developer documentation wiki was quiet and mostly static. I didn't touch it, since I don't know enough to work on developer resources, right? Wait, no! I realized that even if I can't update it all myself, I can help the developers with it, including a bit of persuading them.\r\n\r\nI'll explain some of my strategies for making working on documentation more appealing and rewarding for developers, including by lending it some aspects of the quick feedback that people get when writing code.\r\n\r\nThis includes things like: Ways to make the wiki feel active and alive, since nobody likes to hang out in a ghost town. Good questions to ask that encourage people to write things down. How to make first edits easy with bite-sized tasks and prominent \"todos\" that entice people to click that edit button. Finding people who prefer to ask permission first before making changes, and being there to give them permission! And the best \"trick\": advice for effective ways to thank people a lot, publicly and specifically.", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/4EIj2-n6raA?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/4EIj2-n6raA?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/4EIj2-n6raA/hqdefault.jpg", "duration": 20, "video_ogv_length": null, "video_ogv_url": "", "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": "", "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": "", "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": "", "video_flv_download_only": false, "source_url": "http://youtu.be/4EIj2-n6raA", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:58:00.730", "updated": "2014-07-20T10:36:07.432" }, { "category": "NA 2014", "language": "English", "slug": "the-getting-stopped-experience-improving-your-co", "speakers": [ "Jared Bhatti" ], "tags": [], "id": 71, "state": 1, "title": "The Getting Stopped Experience: Improving Your Content\u2019s First Impression", "summary": "The \u201cGetting Started\u201d page of your product is the most important page for bringing new people onto your product. In the best case, it introduces readers to your product and convinces them to use it. Too often, though, it becomes the \u201cGetting Stopped\u201d experience, with readers getting repeatedly frustrated. Poor documentation, from the Getting Started page on, causes many developers to leave your content and product behind. Outdated information, rude warnings, bad metrics, and poor content strategy all contribute to the \u201cGetting Stopped\u201d experience. \r\n\r\nThis talk examines several practical solutions that tech writers can use to engage readers and create a better first impression. Drawing on examples from Google\u2019s Cloud developer documentation, I focus on how users can define solid metrics for success and encourage reader participation. With these simple but robust solutions, you too can bring more people to your product, getting them started and keeping them around. \r\n", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/_ztGH16XELo?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/_ztGH16XELo?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/_ztGH16XELo/hqdefault.jpg", "duration": 40, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/_ztGH16XELo", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:58:06.003", "updated": "2014-05-09T03:23:47.049" }, { "category": "NA 2014", "language": "English", "slug": "tuesday-lightning-talks", "speakers": [], "tags": [], "id": 69, "state": 1, "title": "Tuesday Lightning Talks", "summary": "(00:00)\r\n(0:00:12)\r\n(0:04:43)\r\n(0:10:26)\r\n(0:13:48)\r\n(0:14:44)\r\n(0:19:09)\r\n(0:19:35)\r\n(0:25:05)\r\n(0:30:23)\r\n(0:31:10)\r\nMaxwell Hoffmann\r\n@maxwellhoffmann\r\nInk Is in PDX\u2019s DNA\r\n", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/iWKirh7bBKM?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/iWKirh7bBKM?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/iWKirh7bBKM/hqdefault.jpg", "duration": 30, "video_ogv_length": null, "video_ogv_url": "", "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": "", "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://www.youtube.com/watch?v=iWKirh7bBKM", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:58:03.380", "updated": "2014-05-25T15:55:11.625" }, { "category": "NA 2014", "language": "English", "slug": "wabi-sabi-writing", "speakers": [ "Scot Marvin" ], "tags": [], "id": 66, "state": 1, "title": "Wabi-Sabi Writing", "summary": "Agile development environments bring increased versions, more due dates, and the accompanying headaches that go with publishing more frequently. And yet, writers must still maintain an emphasis on helping readers with the best documentation we can produce. So, how do we focus on producing documentation that is perfect, permanent, and complete? \r\n\r\nWe don't.\r\n\r\nThe Japanese concept of wabi-sabi refers to an appreciation of the beauty in the imperfect, impermanent, and incomplete. These are qualities of Agile documentation. And they're beautiful. No, really. They are. This talk will detail my journey to let go (meh, for the most part) of the need for technical communication perfection. I will also offer tips for my fellow control freaks.\r\n", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/DTjqqv8Q7cg?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/DTjqqv8Q7cg?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/DTjqqv8Q7cg/hqdefault.jpg", "duration": 20, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": "", "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": "", "video_flv_download_only": false, "source_url": "http://youtu.be/DTjqqv8Q7cg", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:57:59.403", "updated": "2014-05-09T00:28:26.970" }, { "category": "NA 2014", "language": "English", "slug": "we-strongly-recommend-you-write-best-practices", "speakers": [ "Lauren Rother" ], "tags": [], "id": 65, "state": 1, "title": "We Strongly Recommend You Write Best Practices", "summary": "Writing best practices documentation is definitely an art, but that doesn't mean a little science can't help us along. Through some trial and error, I've uncovered some tenets of writing engaging, readable best practices docs. I'll walk through a bit of my path to discovery as I highlight and give examples of successful and (enthusiastic) reader-approved best practices documents. \r\n\r\n", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/tKssFJJw6h0?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/tKssFJJw6h0?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/tKssFJJw6h0/hqdefault.jpg", "duration": 20, "video_ogv_length": null, "video_ogv_url": "", "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": "", "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/tKssFJJw6h0", "whiteboard": "", "recorded": "2014-05-06", "added": "2014-04-28T22:57:58.087", "updated": "2014-05-25T15:55:09.699" }, { "category": "NA 2014", "language": "English", "slug": "communities-are-awesome", "speakers": [ "Ali Spivak" ], "tags": [], "id": 36, "state": 1, "title": "Communities are Awesome", "summary": "The Mozilla Developer Network is an open-source documentation wiki for web developers, which is written by really passionate, smart, and inspiring people. Most are not paid employees of Mozilla. All of them are helping make the web a better place by writing, editing, and reviewing articles. How do you support a diverse community, acknowledge many different voices and perspectives, be open and inclusive, and still get things done (especially when you can't force anyone to do anything)? In this session, I\u2019ll share what I\u2019ve learned (and keep learning) by working with, in, and for volunteer communities; including how to be more transparent, create opportunity, and broadly share ownership. \r\n", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/jhXlKEnTwS4?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/jhXlKEnTwS4?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/jhXlKEnTwS4/hqdefault.jpg", "duration": 20, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/jhXlKEnTwS4", "whiteboard": "", "recorded": "2014-05-05", "added": "2014-04-28T22:57:19.880", "updated": "2014-05-06T17:31:26.420" }, { "category": "NA 2014", "language": "English", "slug": "data-documentation-and-memory", "speakers": [ "Amelia Abreu" ], "tags": [], "id": 52, "state": 1, "title": "Data, Documentation and Memory", "summary": "In this presentation, I explore the role of documentation and technical writing in shaping larger recordkeeping and memory practices. How does documentation shape institutional memory? How does it validate and enforce definitions and boundaries? What roles do documentarians play in the larger ecosystem of development?\r\n\r\nDrawing on my experiences as a UX Researcher and an academic HCI background, I introduce concepts from archival and critical theory. Examining both data and metadata structures, I argue for an infrastructural understanding of documentation, one that acknowledges documentation practice as crucial scaffolding for the development process. In conclusion, I present recommendations for maximizing the value of archival documentation and improving data retention and retrieval.\r\n", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/wu5vqr8U1fU?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/wu5vqr8U1fU?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/wu5vqr8U1fU/hqdefault.jpg", "duration": 20, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/wu5vqr8U1fU", "whiteboard": "", "recorded": "2014-05-05", "added": "2014-04-28T22:57:40.978", "updated": "2014-05-25T15:55:03.453" }, { "category": "NA 2014", "language": "English", "slug": "death-by-documentation", "speakers": [ "Christina Elmore" ], "tags": [], "id": 53, "state": 1, "title": "Death by Documentation", "summary": "The urge to document is at the root of many bad presentation habits.\r\n\r\nDespite a renaissance in the\r\n art of presentation - think TED Talks, Nancy Duarte, Prezi, and Ignite \u2013\r\n we still experience more bad presentations than any lifetime deserves. \r\nEven with compelling content and conquered nerves, a presenter\u2019s visual \r\nmaterials can totally tank a talk. And documentation is often to blame. \r\n\r\nThe real culprit is a conflation of documentation and presentation. Many slide collections end up being an awkward mash-up of the two, and documents suffer when we force them into the mental model of a presentation. (NASA and the military offer striking examples of these failures.) Why have the\r\n differences between documentation and presentation been lost? How can \r\nwe make better sense of these two forms to create more engaging \r\npresentations and better documents?", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/7tncfRqKnXU?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/7tncfRqKnXU?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/7tncfRqKnXU/hqdefault.jpg", "duration": 20, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/7tncfRqKnXU", "whiteboard": "", "recorded": "2014-05-05", "added": "2014-04-28T22:57:42.320", "updated": "2014-05-08T09:37:35.562" }, { "category": "NA 2014", "language": "English", "slug": "did-it-in-minutes-the-art-of-documenting-meeting", "speakers": [ "Mo Nishiyama" ], "tags": [], "id": 40, "state": 1, "title": "Did It In Minutes: The Art of Documenting Meeting Notes", "summary": "If elegant technical help pages are the shiny, sleek roadsters of the documentation world, the plebeian meeting minutes are the dump trucks. Despite being regarded as an unglamorous business tool, minutes serve an important function for communicating effectively with colleagues.\r\n\r\nMeeting minutes document changes to business operations, chronicle the decisions that were made, capture the essential gist of discussions, and serve as handy references for those colleagues who were unable to attend the meeting--or for those who indulged in siestas during the gathering. Minutes can even justify whether a meeting was necessary in the first place.\r\n\r\nEffective minutes can save companies labor costs: well-written meeting notes can prevent both meeting organizers and absent team members valuable time that would otherwise be spent trying to bring absentees up to speed. Accurate meeting notes can clearly define policies and expectations in a workgroup.\r\n\r\nIn this presentation, we will discuss best practices for documenting and curating meeting notes. Using meeting templates, de-mystifying technical jargons, breaking free of the chronological reporting, adhering to the WTF (Write The Facts) approach, carving time for editing notes, charting follow-up tasks, and judiciously spicing up otherwise-mundane topics are \u00a0examples of these best practices. Special emphasis will be placed on writing with clarity and empathy in mind for team members, whether they were present at the meeting or not.\r\n", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/q-ghGzIAuhw?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/q-ghGzIAuhw?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/q-ghGzIAuhw/hqdefault.jpg", "duration": 20, "video_ogv_length": null, "video_ogv_url": "", "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": "", "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "https://www.youtube.com/watch?v=q-ghGzIAuhw", "whiteboard": "", "recorded": "2014-05-05", "added": "2014-04-28T22:57:25.200", "updated": "2014-05-06T17:19:30.379" }, { "category": "NA 2014", "language": "English", "slug": "documentation-at-scale", "speakers": [ "Kenneth Reitz" ], "tags": [], "id": 48, "state": 1, "title": "Documentation at Scale", "summary": "Information is powerful \u2014 every day we see it transform the world around us.\r\n\r\nDocumentation doesn't always have to be about a software workflow or open source project \u2014 it can be used to develop and convey ideas much larger than yourself. Information architecture is a powerful tool for developing ideas over time. It enables us to evolve and distill information at a much larger scale than a single person or team could ever achieve on their own. \r\n\r\nTake these concepts, and apply open source workflow tools like GitHub's Pull Requests and Write the Docs, and the distributed evolution of ideas and information has never been more accessible.\r\n\r\nWe'll explore these concepts, learn how to foster a community of distributed contributors, encourage contributions early on, and more.\r\n\r\nPython-Guide.org will be used as an example, a Python-specific knowledge base written by 168 people and accessed by over 50,000 people every month. \r\n", "description": "", "quality_notes": "", "copyright_text": "", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\"http://youtube.com/v/zhZOGST52ds?version=3&amp;hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\"http://youtube.com/v/zhZOGST52ds?version=3&amp;hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "http://i1.ytimg.com/vi/zhZOGST52ds/hqdefault.jpg", "duration": 20, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "http://youtu.be/zhZOGST52ds", "whiteboard": "", "recorded": "2014-05-05", "added": "2014-04-28T22:57:35.682", "updated": "2014-05-08T09:31:06.301" } ] }