Skip to content

Comments

Remove video archive from website#2482

Open
ericholscher wants to merge 4 commits intomainfrom
codex/remove-videos-and-link-to-youtube-channel-imvb5k
Open

Remove video archive from website#2482
ericholscher wants to merge 4 commits intomainfrom
codex/remove-videos-and-link-to-youtube-channel-imvb5k

Conversation

@ericholscher
Copy link
Member

@ericholscher ericholscher commented Nov 25, 2025

Summary

  • replace the video archive page with a pointer to the Write the Docs YouTube channel
  • update site copy, conference info, and resource listings to send users to YouTube instead of on-site video URLs
  • remove the legacy video Sphinx extension and its directive registration
  • exclude the old video pages from the Sphinx build and drop unused video helpers

Codex Task


📚 Documentation preview 📚: https://writethedocs-www--2482.org.readthedocs.build/

@ericholscher
Copy link
Member Author

I tried to get the AI to link the specific video links, but gave up. Should be mostly ready to merge tho.

@ericholscher ericholscher changed the title Remove remaining video extension logic Remove video archive from website Nov 25, 2025
@plaindocs
Copy link
Contributor

oh damn, you beat me to it.

Are we going to do anything about existing video URLs? Maybe catch them with a redirect?

@plaindocs
Copy link
Contributor

I'll take a look at this after the end of the week.

@plaindocs
Copy link
Contributor

@ericholscher finally took a look at this.

We really should also be deleting _ext/videos.y and all of videos/* except for the index right? The problem is that breaks the topic page. :-/ So maybe that's why you left the pages in?

To address that'd need to parse out

topics.rst
514:- |:movie_camera:| `Two years of Markdoc: what we’ve learned about balancing developer and author experience </videos/prague/2022/two-years-of-markdoc-what-we-ve-learned-about-balancing-developer-and-author-ex-ryan-paul/>`__

grab the conf + year + author, and use the info in

...
- title: 'Two years of Markdoc: what we’ve learned about balancing developer and author
    experience'
  slug: two-years-of-markdoc-what-we-ve-learned-about-balancing-developer-and-author-ex-ryan-paul
  series: Write the Docs Prague
  series_slug: prague
  year: 2022
  youtubeId: Js8ZK-eiwAg
...

Should be fairly doable

@plaindocs
Copy link
Contributor

plaindocs commented Jan 11, 2026

OK, I've noodled a bit further on this.

If you grab the conference context from the following files

'au' '2017'
'australia' '2020'
'eu' '2015'
'eu' '2016'
'eu' '2017'
'na' '2015'
'na' '2016'
'na' '2017'
'portland' '2018'
'portland' '2019'
'portland' '2020'
'portland' '2021'
'portland' '2022'
'prague' '2018'
'prague' '2019'
'prague' '2020'
'prague' '2021'
'prague' '2022'

You could do a search topics.rst with the following regex, use Group 3 to grab the youtube URL from the conference context

with open('../topics.rst', 'r') as file:
    for line in file:
        m = re.search("</videos/([a-z]*)/([0-9]{4})/([a-z-]*)/>", line)

And then do another pass to search replace the string to point directly to the youtube video.

But I've run out of steam to push this over the line for now.

@plaindocs
Copy link
Contributor

Incidentally, we don't have any videos from 2023-2025 in the topic index, which would make a nice writing day project if someone fancies running it CC @rosewms @djwfyi

@plaindocs
Copy link
Contributor

I just pushed up a couple of commits to https://github.com/writethedocs/www/tree/codex/remove-videos-and-link-to-youtube-channel removing the files, not quite sure what happened there

@plaindocs
Copy link
Contributor

plaindocs commented Jan 11, 2026

Oh, and a dump of the data from topics.rst in case you wanna point a bot at it :-p

'prague', '2018', 'don-t-say-simply-jim-fisher'
'eu', '2017', 'aw-snap-the-docs-they-are-a-changin-with-apologies-to-bob-dylan-kate-wilcox'
'eu', '2016', 'information-micro-architecture-grammar-syntax-and-cognitive-rhetoric-rory-tanner'
'eu', '2016', 'writing-as-a-non-native-speaker-istvan-zoltan-szabo'
'na', '2016', 'writing-so-your-words-are-read-tracy-osborn'
'na', '2017', 'even-naming-this-talk-is-hard-ruthie-bendor'
'eu', '2015', 'whatchamacallit-controlled-vocabularies-for-technical-writers-eboillat'
'portland', '2020', 'creating-quality-sample-code-jessica-garson'
'prague', '2020', 'need-examples-write-your-own-joe-malin'
'portland', '2018', 'making-your-code-examples-shine-larry-ullman'
'eu', '2015', 'visual-documentation-language-sheinen'
'portland', '2018', 'graphic-content-warning-the-pros-cons-and-alternatives-to-screenshots-steve-stegelin'
'eu', '2016', 'when-bad-screenshots-happen-to-good-writers-swapnil-ogale'
'portland', '2020', 'set-your-data-free-with-model-based-architecture-diagramming-avi-flax'
'portland', '2019', 'draw-the-docs-alicja-raszkowska'
'prague', '2018', 'so-you-want-to-make-videos-sarah-ley-hamilton'
'eu', '2017', 'documentation-beyond-words-chris-ward'
'eu', '2015', 'how-to-write-an-email-ecaine'
'eu', '2016', 'checklist-the-docs-daniel-beck'
'na', '2015', 'how-to-write-documentation-for-people-that-don-t-read-kburke'
'na', '2017', 'start-with-the-tasks-not-the-endpoints-sarah-hersh'
'na', '2015', 'let-s-tell-a-story-scenario-based-documentation-mness'
'na', '2015', 'user-story-driven-docs-jfernandes'
'portland', '2021', 'shuffle-ball-change-sashay-your-way-to-clearer-api-documentation-rachael-stavchansky'
'prague', '2019', 'write-the-api-docs-before-the-api-exists-ben-ahmady'
'na', '2016', 'so-you-need-to-document-an-api-allison-reinheimer-moore'
'eu', '2017', 'hi-my-name-is-readme-raphael-pierzina'
'na', '2016', 'write-the-readable-readme-daniel-beck'
'prague', '2022', 'improve-customer-adoption-with-ui-help-prashant-mathapathi'
'prague', '2020', 'bake-a-little-documentation-love-into-your-product-matt-reiner'
'portland', '2019', 'tutorials-tooltips-and-popupsoh-my-how-to-ease-yourself-and-your-users-into-in-app-messaging-meghan-mahar'
'prague', '2018', 'learning-to-love-release-notes-anne-edwards'
'prague', '2021', 'how-to-write-a-book-for-and-with-an-open-source-community-felicity-brand'
'prague', '2021', 'so-you-need-to-give-bad-news-to-users-ryan-macklin-he-they'
'portland', '2021', 'writing-a-perfect-technical-tutorial-jessica-garson'
'prague', '2020', 'emulating-the-teacher-s-approving-nod-in-teaching-material-tanks-transfeld'
'australia', '2020', 'how-and-why-to-make-awesome-video-tutorials-sayraphim-lothian'
'australia', '2020', 'microcontent-designing-developing-reusable-content-scott-deloach'
'portland', '2020', 'writing-backwards-documenting-the-end-of-life-of-a-product-anni-bond'
'portland', '2020', 'why-sdk-docs-matter-and-what-i-m-doing-about-it-shavindri-dissanayake-shavi'
'portland', '2019', 'sdk-reference-manuals-a-flow-based-approach-chris-bush'
'prague', '2018', 'it-s-a-feature-documenting-known-issues-and-product-shortcomings-ivana-devcic'
'portland', '2018', 'writing-the-next-great-tech-book-brian-macdonald'
'portland', '2018', 'the-facts-about-faqs-ashleigh-rentz'
'portland', '2018', 'not-the-docs-content-and-voice-on-a-developer-blog-havi-hoffman'
'eu', '2017', 'you-never-get-a-second-chance-to-make-a-first-impression-writing-great-getting-started-documentation-tim-rogers'
'na', '2017', 'do-you-know-a-runbook-from-a-flip-book-how-sysadmins-use-documentation-andrea-longo'
'na', '2016', 'code-the-docs-interactive-document-environments-tim-nugent-paris-buttfield-addison'
'na', '2015', 'keynote-the-federated-wiki-ward-cunningham'
'na', '2015', 'designing-information-for-growth-mdevoto'
'prague', '2020', 'when-wishing-still-helped-what-folklore-can-teach-us-about-technical-writing-ingrid-k-towey'
'australia', '2020', 'storytelling-for-technical-products-what-we-can-learn-from-lego-and-pixar-akshay-iyer'
'prague', '2019', 'wild-geeks-poetry-in-the-digital-age-ellie-farrier'
'eu', '2017', 'telling-a-great-story-on-github-lauri-apple'
'na', '2016', 'what-writing-fiction-teaches-you-about-writing-documentation-thursday-bram'
'eu', '2015', 'documenting-your-story-crafting-a-good-presentation-cward'
'na', '2015', 'elevating-the-hedgehog-creativity-in-tech-writing-tfranko'
'na', '2015', 'let-s-tell-a-story-scenario-based-documentation-mness'
'portland', '2022', 'don-t-shoot-yourself-in-the-foot-with-content-reuse-anna-gasparyan'
'prague', '2019', 'how-to-launch-your-startup-with-good-docs-brian-lemke'
'au', '2017', 'delivering-documents-for-all-three-use-cases-margaret-fero'
'eu', '2017', 'the-four-kinds-of-documentation-and-why-you-need-to-understand-what-they-are-daniele-procida'
'prague', '2021', 'more-than-words-reviewing-and-updating-your-information-architecture-lana-brindley-she-her'
'eu', '2016', 'information-micro-architecture-grammar-syntax-and-cognitive-rhetoric-rory-tanner'
'prague', '2020', 'organizing-a-confluence-hoard-or-does-this-page-spark-joy-abigail-sutherland'
'australia', '2020', 'legacy-content-from-various-perspectives-marcelina-haftka'
'australia', '2020', 'when-agile-fails-working-on-large-documentation-projects-lana-brindley'
'prague', '2018', 'how-to-tear-down-existing-documentation-and-rewrite-docs-that-actually-work-alexandra-white'
'portland', '2018', 'where-do-i-start-the-art-and-practice-of-documentation-triage-neal-kaplan'
'portland', '2018', 'rewrite-the-docs-field-notes-from-the-radical-it-department-camille-acey'
'eu', '2017', 'deprecate-and-destroy-documenting-your-software-s-last-days-daniel-d-beck'
'eu', '2015', 'macgyvering-your-docs-proeland'
'na', '2015', 'what-can-brownfield-do-for-you-mnishiyama'
'prague', '2022', 'maintaining-documentation-make-it-easy-emilia-juda-zbay'
'portland', '2020', 'finding-the-line-balancing-business-continuity-and-documentation-debt-luca-janssens'
'prague', '2020', 'future-proofing-your-support-visuals-jen-weaver'
'prague', '2021', 'hustling-for-fun-and-profit-as-a-technical-writer-a-freelancing-starter-kit-karen-sawrey'
'prague', '2019', 'fostering-technical-writing-in-developing-nations-prerana-pradhan'
'portland', '2018', 'starting-from-scratch-finding-and-hiring-junior-writers-sarah-day'
'na', '2017', 'interviewing-and-hiring-technical-writers-the-siberian-way-sam-faktorovich'
'portland', '2018', 'document-yourself-practical-tips-for-a-low-er-stress-portfolio-erin-grace'
'portland', '2021', 'is-tech-writer-a-tester-and-vice-versa-is-tester-a-tech-writer-ines-stefanovic'
'portland', '2018', 'what-writing-dictionaries-taught-me-about-writing-documentation-and-what-i-had-to-unlearn-erin-mckean'
'na', '2017', 'caring-systems-documentation-as-care-amelia-abreu'
'eu', '2016', 'operations-technical-writing-for-data-centers-joan-wendt'
'eu', '2016', 'beyond-software-learning-from-other-technical-writers-chris-ward'
'na', '2016', 'oops-i-became-an-engineer-tara-scherner-de-la-fuente'
'portland', '2022', 'beating-the-virginia-blues-thru-hiking-strategies-to-help-you-survive-your-next-kate-mueller'
'prague', '2021', 'docs-leadership-how-to-become-a-stronger-leader-for-your-team-jenn-leaver'
'prague', '2021', 'from-travel-content-to-technical-content-my-journey-kate-santo'
'prague', '2020', 'from-graffiti-writer-to-technical-writer-kruno-golubi'
'australia', '2020', 'overcoming-the-plight-of-lone-writers-ankita-tripathi'
'prague', '2019', 'fostering-talent-mentorship-peer-reviews-and-going-beyond-your-job-description-arran-southall'
'portland', '2019', 'writer-editor-teacher-kathleen-juell'
'portland', '2019', 'harvest-past-experience-to-be-a-great-tech-writer-mark-f-iverson'
'eu', '2017', 'an-alien-looking-from-the-outside-in-main-takeaways-after-one-year-in-documentation-meike-chabowski'
'na', '2016', 'we-re-not-in-kansas-anymore-how-to-find-courage-while-following-the-technical-doc-road-christy-lutz'
'eu', '2015', 'imposter-no-more-how-tech-writers-can-shed-self-doubt-embrace-uncertainty-and-surf-the-upcoming-swerve-in-technical-documentation-rmacnamara'
'prague', '2022', 'how-i-convinced-my-boss-to-build-our-docs-team-karissa-van-baulen'
'portland', '2022', 'from-me-to-us-building-a-docs-team-from-the-ground-up-lana-brindley-she-her'
'portland', '2021', 'level-up-onboarding-that-enables-writers-to-thrive-nicola-yap'
'australia', '2020', 'onboard-yourself-how-to-get-set-up-for-success-in-a-new-role-michael-belton'
'prague', '2022', 'the-art-of-asking-questions-jeff-smith'
'portland', '2020', 'read-the-rules-what-technical-writers-can-learn-from-board-game-design-matthew-baldwin'
'prague', '2022', 'adhd-and-its-impact-on-the-creative-process-for-writers-tyler-smith'
'portland', '2021', 'writing-documentation-with-neurodivergent-open-source-contributors-in-mind-rin-oliver'
'prague', '2019', 'inclusive-environments-are-better-science-says-so-ilona-koren-deutsch'
'eu', '2017', 'sticks-stones-microaggressions-inclusive-language-at-work-cory-williamson-cardneau'
'na', '2016', 'accessible-math-on-the-web-a-server-client-solution-tim-arnold'
'eu', '2015', 'inclusive-tech-docs-techcomm-meets-accessibility-rmatic'
'prague', '2022', 'creating-documentation-for-the-african-audience-benny-ifeanyi-iheagwara'
'prague', '2022', 'toward-the-broader-globalization-of-open-source-documenting-your-localisation-j-melissa-black'
'prague', '2021', 'how-i-use-applied-linguistics-to-be-a-better-technical-writer-kat-stoica-ostenfeld'
'australia', '2020', 'influence-your-customer-outreach-with-best-practices-for-internationalization-vikram-mulay'
'portland', '2020', 'globalise-the-docs-lucy-carey'
'prague', '2019', 'found-in-translation-lessons-from-a-year-of-open-source-localization-zachary-sarah-corleissen'
'portland', '2019', 'localize-the-docs-paul-wallace'
'prague', '2021', 'when-documenting-is-designing-how-to-assist-api-design-as-a-technical-writer-fabrizio-ferri-benedetti'
'prague', '2019', 'surprise-you-re-a-designer-now-kelly-obrien'
'au', '2017', 'peanuts-and-minimalism-and-technical-writing-brice-fallon'
'eu', '2015', 'writing-for-what-matters-writing-for-thinking-znemec'
'na', '2015', 'keynote-we-are-all-abbott-and-costello-maria-riefer-johnston'
'na', '2015', 'designing-information-for-growth-mdevoto'
'portland', '2021', 'invisible-influence-the-documentation-behind-ux-copy-katherine-karaus'
'australia', '2020', 'little-words-big-ideas-how-to-write-microcopy-that-works-yael-ben-david'
'au', '2017', 'conversational-uis-for-writers-chris-ward'
'na', '2017', 'error-messages-being-humble-human-and-helpful-will-make-users-happy-kate-voss'
'eu', '2016', 'using-meaningful-names-to-improve-api-documentation-jan-christian-krause'
'eu', '2016', 'watch-that-tone-creating-an-information-experience-in-the-atlassian-voice-sarah-karp'
'na', '2016', 'copy-that-helping-your-users-succeed-with-effective-product-copy-sarah-day'
'na', '2016', 'atlassian-my-information-experience-adventure-daniel-stevens'
'eu', '2015', 'before-the-docs-writing-for-user-interfaces-baitman'
'na', '2015', 'keep-em-playing-tpodmajersky'
'australia', '2020', 'a-treasure-map-for-the-doc-exploring-the-discoverability-of-documentation-marika-vertzonis'
'prague', '2019', 'disagree-with-i-agree-enforcing-better-data-privacy-through-the-language-of-documentation-karen-sawrey'
'na', '2016', 'code-the-docs-interactive-document-environments-tim-nugent-paris-buttfield-addison'
'prague', '2020', 'the-baseline-or-technical-writing-for-non-technical-readers-paul-brown'
'prague', '2019', 'seeing-your-docs-through-different-eyes-mapping-doc-users-experiences-aaron-collier'
'prague', '2019', 'documenting-known-unknowns-alison-macneil'
'eu', '2017', 'requirements-that-you-didn-t-know-were-there-lesia-zasadna'
'eu', '2016', 'pretty-hurts-why-better-trumps-best-riona-macnamara'
'eu', '2016', 'api-documentation-exploring-the-information-needs-of-software-developers-michael-meng'
'na', '2016', 'documentation-with-human-connection-hannah-gilberg'
'na', '2015', 'user-story-driven-docs-jfernandes'
'prague', '2022', 'two-years-of-markdoc-what-we-ve-learned-about-balancing-developer-and-author-ex-ryan-paul'
'portland', '2021', 'putting-the-tech-in-technical-writer-swapnil-ogale'
'portland', '2020', 'documentation-as-an-application-enabling-interactive-content-that-is-tailored-to-the-user-ryan-paul'
'portland', '2020', 'model-view-docs-taming-large-scale-documentation-projects-using-structured-data-luc-perkins'
'prague', '2020', 'the-rocky-road-to-docops-chris-noonan'
'portland', '2020', 'don-t-fear-migration-how-to-successfully-move-docs-to-a-new-tool-brooke-wayne'
'portland', '2020', 'where-documentation-cloud-hosted-interactive-tutorials-and-continuous-integration-testing-intersect-dan-gunter'
'portland', '2019', 'how-i-learned-to-stop-worrying-and-love-the-command-line-mike-jang'
'prague', '2018', 'choosing-a-tool-and-choosing-your-moment-val-grimm'
'au', '2017', 'writing-extensions-in-sphinx-supercharge-your-docs-nicola-nye'
'eu', '2017', 'finally-trustworthy-and-sensible-api-documentation-with-graphql-garen-torikian'
'na', '2016', 'embed-the-docs-kristof-van-tomme'
'portland', '2022', 'one-aws-team-s-move-to-docs-as-code-what-worked-what-didn-t-what-s-next-marcia-riefer-johnston'
'prague', '2019', 'the-uk-government-meets-docs-as-code-jen-lambourne'
'na', '2017', 'treating-documentation-like-code-a-practical-account-jodie-putrino'
'eu', '2016', 'docs-as-code-the-missing-manual-margaret-eker-jennifer-rondeau'
'na', '2015', 'a-developers-approach-to-documentation-from-passive-to-dynamic-gkoberger'
'na', '2015', 'how-github-uses-github-to-document-github-gtorikian'
'portland', '2022', 'unit-test-the-docs-why-you-should-test-your-code-examples-ben-perlmutter'
'prague', '2022', 'beyond-spell-checking-what-else-can-we-check-automatically-tibs'
'prague', '2018', 'run-your-docs-predrag-mandic'
'na', '2017', 'testing-it-s-not-just-for-code-anymore-lyzi-diamond'
'na', '2015', 'tech-writing-in-a-continuous-deployment-world-cburwinkle'
'eu', '2015', 'tested-and-correct-how-to-make-sure-your-documentation-keeps-working-adangoor'
'eu', '2015', 'generating-docs-from-apis-jhannaford'
'portland', '2020', 'the-search-for-search-paul-logan'
'prague', '2020', 'making-documentation-discoverable-in-search-engines-myriam-jessier'
'portland', '2022', 'don-t-trust-the-numbers-kumar-dhanagopal'
'prague', '2020', 'the-importance-of-using-analytics-and-feedback-for-your-documentation-karissa-van-baulen'
'portland', '2020', 'walking-backwards-tracing-the-new-customer-journey-from-finish-to-start-to-help-shape-content-sally-stumbo'
'portland', '2018', 'research-like-you-re-wrong-lessons-from-user-research-gone-rogue-jen-lambourne'
'portland', '2018', 'building-empathy-driven-developer-documentation-kat-king'
'eu', '2016', 'api-documentation-exploring-the-information-needs-of-software-developers-michael-meng'
'na', '2015', 'keynote-we-are-all-abbott-and-costello-maria-riefer-johnston'
'na', '2015', 'how-to-write-documentation-for-people-that-don-t-read-kburke'
'prague', '2021', 'customer-feedback-is-the-fuel-in-our-engine-kevin-hwang'
'na', '2016', 'csat-what-s-that-betsy-roseberg'
'portland', '2022', 'measuring-documentation-success-in-open-source-findings-from-google-s-season-of-kassandra-dhillon'
'prague', '2018', 'measuring-the-impact-of-your-documentation-liam-keegan'
'portland', '2021', 'a-guide-to-getting-started-in-open-source-abigail-mccarthy'
'prague', '2018', 'a-year-in-the-life-of-the-better-docs-project-rowan-cota'
'na', '2016', 'technical-writing-as-public-service-working-on-open-source-in-government-britta-gustafson'
'prague', '2021', 'adventures-in-setting-up-a-knowledge-system-for-a-research-group-victor-sluiter'
'portland', '2021', 'almost-none-to-some-driving-disqo-s-doc-culture-as-a-solo-documentarian-falon-darville'
'prague', '2020', 'how-to-be-an-avante-garde-guinea-pig-building-better-content-through-experimentation-community-building-and-loud-squeaks-jessica-valasek-estenssoro'
'portland', '2019', 'documenting-for-open-source-shannon-crabill'
'portland', '2019', 'defying-the-status-quo-how-a-grassroots-effort-can-transform-an-organization-jodie-putrino'
'portland', '2019', 'documentation-for-good-riona-macnamara'
'portland', '2018', 'who-writes-the-docs-beth-aitman'
'na', '2016', 'move-fast-and-document-things-hard-won-lessons-in-building-documentation-culture-in-startups-ruthie-bendor'
'eu', '2015', 'all-roads-might-not-lead-to-docs-celmore'
'eu', '2015', 'free-your-mind-and-your-docs-will-follow-pkeegan'
'na', '2015', 'documentation-disrupted-how-two-technical-writers-changed-google-engineering-culture-built-a-team-made-powerful-friends-and-got-their-mojo-back-rmacnamara'
'na', '2015', 'entry-points-and-guide-posts-helping-new-contributors-find-their-way-jswisher'
'na', '2015', 'the-making-of-writing-black-belts-how-martial-arts-philosophy-forged-an-ad-hoc-writing-team-that-writes-great-docs-gwalli'
'portland', '2022', 'peer-writing-and-beyond-an-experimental-approach-to-a-sustainable-open-source-chris-ganta'
'portland', '2022', 'all-together-now-turning-technologists-into-documentarians-liani-lye-she-her'
'portland', '2021', 'documentation-communities-sound-strategy-or-documentarian-s-gambit-laura-novich'
'prague', '2020', 'helping-your-community-contribute-to-developer-documentation-diana-lakatos'
'portland', '2019', 'any-friend-of-the-docs-is-a-friend-of-mine-cultivating-a-community-of-documentation-advocates-heather-stenson'
'eu', '2017', 'a-content-manager-s-guide-to-crowdsourcing-the-docs-becky-todd'
'na', '2017', 'the-wisdom-of-crowds-crowdsourcing-minimalism-in-an-open-organization-ingrid-towey'
'eu', '2016', 'feedback-handling-community-wrangling-panhandling-chris-mills'
'eu', '2016', 'documentoring-growing-a-love-the-docs-community-david-oliver'
'na', '2016', 'how-to-publish-wild-caught-articles-sharon-campbell'
'eu', '2015', 'gardening-open-docs-florian-scholz-jean-yves-perrier'
'na', '2015', 'start-your-own-write-the-docs-meetup-group-mjang'
'portland', '2021', 'building-a-style-guide-from-the-ground-up-lessons-learned-from-a-lone-writer-deanna-thompson'
'portland', '2018', 'what-they-don-t-tell-you-about-creating-new-style-guides-thursday-bram'
'eu', '2016', 'watch-that-tone-creating-an-information-experience-in-the-atlassian-voice-sarah-karp'
'eu', '2015', 'whatchamacallit-controlled-vocabularies-for-technical-writers-eboillat'
'prague', '2022', 'cultivating-a-stakeholder-network-for-our-docs-how-building-relationships-impro-taylor-cole'
'portland', '2022', 'code-cowpokes-and-word-wranglers-from-mutual-admiration-to-solidarity-erin-dees'
'australia', '2020', 'the-pains-of-composition-how-to-write-your-best-documentation-in-a-collaborative-world-matt-reiner'
'portland', '2019', 'how-to-edit-other-peoples-content-without-pissing-them-off-ingrid-towey'
'na', '2017', 'you-have-already-succeeded-design-critique-guidelines-make-feedback-easier-christy-lutz'
'na', '2015', 'how-github-uses-github-to-document-github-gtorikian'
'na', '2017', 'only-interesting-conversations-the-symbiotic-relationship-between-docs-and-support-matthew-buttler'
'eu', '2016', 'documentarians-and-support-work-better-together-sarah-chambers'
'na', '2016', 'two-great-teams-that-work-better-together-bridging-the-gap-between-documentation-and-customer-support-neal-kaplan'
'prague', '2018', 'teaching-geeks-to-fish-tales-of-a-contagious-documentarian-abigail-sutherland'
'prague', '2022', 'documentation-as-marketing-from-conflict-to-collaboration-mano-toth'
'portland', '2020', 'collaborating-with-teams-on-content-strategy-planning-pitfalls-and-best-practices-kateryna-osadchenko'
'australia', '2020', 'an-introduction-to-developer-experience-and-the-role-of-a-documentarian-chris-ward'
'na', '2016', 'crossing-the-streams-enabling-collaboration-between-products-and-upstreams-shaun-mccance'
'na', '2015', 'writer-meet-tester-jbleyle-alouie-arthur-louie'
'prague', '2021', 'alchemy-in-adversity-how-to-become-better-and-more-resilient-tech-writers-in-a-turbulent-work-environment-anna-korinna-n-meth-szab'
'prague', '2019', 'the-super-effective-writing-process-of-grammy-winning-artists-kayla-lee'
'portland', '2019', 'just-add-data-make-it-easier-to-prioritize-your-documentation-sarah-moir'
'prague', '2018', 'document-what-matters-lean-best-practice-for-process-documentation-gillian-von-runte'
'portland', '2018', 'where-do-i-start-the-art-and-practice-of-documentation-triage-neal-kaplan'
'prague', '2020', 'documenting-the-ancient-history-of-your-project-natali-vlatko'
'portland', '2020', 'building-a-content-focused-scientific-document-authoring-workflow-for-data-scientists-and-engineers-alike-colin-dean'
'portland', '2019', 'lessons-learned-in-a-year-of-docs-driven-development-jessica-parsons'
'eu', '2016', 'postulating-the-backlog-laxative-paul-adams'
'eu', '2015', 'judas-priest-ate-my-scrum-master-padams'
'eu', '2016', 'delivering-high-velocity-docs-that-keep-pace-with-rapid-release-cycles-rachel-whitton'
'na', '2016', 'continuous-annoyment-bringing-more-zen-to-a-hectic-writing-environment-tana-franko'
'na', '2016', 'just-in-time-documentation-employing-agile-methodology-to-create-living-documentation-brianne-hillmer'
'portland', '2022', 'lessons-learned-from-cloud-ops-writing-docs-for-high-stakes-situations-alastair-dallas'
'portland', '2021', 'always-complete-never-finished-daniele-procida'
'portland', '2021', 'beyond-metrics-using-maturity-models-to-develop-a-docs-strategy-sarah-r-rodlund'
'australia', '2020', 'content-strategy-in-practice-a-case-study-sam-irons'
'portland', '2019', 'show-me-the-money-how-to-get-your-docs-the-love-and-support-they-deserve-matt-reiner'
'portland', '2019', 'product-documentation-strategy-what-is-it-and-why-do-we-need-it-kay-miles'
'prague', '2018', 'choosing-a-tool-and-choosing-your-moment-val-grimm'
'portland', '2018', 'audience-market-product-tips-for-strategic-api-documentation-planning-bob-watson'
'na', '2017', 'bootstrapping-docs-at-a-startup-jesse-seldess'
'na', '2015', 'designing-information-for-growth-mdevoto'
'eu', '2016', 'pretty-hurts-why-better-trumps-best-riona-macnamara'
'na', '2015', 'success-is-more-than-not-failing-hwaterhouse'
'prague', '2021', 'cognitive-ergonomics-in-technical-writing-lessons-from-the-field-anita-diamond'
'au', '2017', 'peanuts-and-minimalism-and-technical-writing-brice-fallon'
'eu', '2016', 'poll-the-docs-kata-nagygyorgy'
'portland', '2021', 'the-secret-history-of-libraries-paris-buttfield-addison'
'prague', '2020', 'a-journey-to-pattern-languages-andrew-haynes'
'prague', '2018', 'a-brief-history-of-text-markup-languages-tony-ibbs'
'eu', '2017', 'tech-writers-without-borders-making-the-world-a-better-place-one-numbered-step-at-a-time-stuart-culshaw'
'na', '2016', 'accessible-math-on-the-web-a-server-client-solution-tim-arnold'
'eu', '2015', 'the-quest-for-scientific-credit-for-software-documentation-ajaruga'
'eu', '2015', 'back-to-the-future-what-can-documentarians-learn-from-the-past-jrondeau'
'na', '2015', 'a-brief-history-of-math-writing-symbol-structure-and-proof-ehoffmann-aroman-alfonso-roman'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants