Legacy content from various perspectives

on YouTube ↗32m

" summary

Three concrete paths appear: destroy and rebuild when budget allows; review and update but account for translation costs because small source edits trigger full retranslation; and the Strangler fig pattern of incrementally replacing docs alongside releases. Practical tools and checks include CAT tools and xbench style QA to diff versions and spot costly changes. Watch for variables and localization traps — a country-name variable causes Polish declension issues that cost a week to resolve.

AI-written summary · about

" chapters (12)

1. 0:00Intro
2. 0:18Luna
3. 1:15Create new documentation
4. 2:34Review correct update
5. 8:04Audit
6. 10:43Internal Process
7. 16:57Why legacy documentation
8. 19:31Contact me
9. 19:53Audit tools
10. 25:53Common mistakes
11. 26:13Two mistakes
12. 27:23Content context

" related talks

• 01h 06mRewriting Legacy CodeAnna Filina · phpday 2021
• 48mContinuous Localization in Enterprise Web ProjectsAnte Tomić · Build Stuff 2022
• 46mModernizing legacy through thousands of contextual tools … per systemTudor Girba · Craft Conference 2025
• 35mUpgrading Legacy Projects: Lessons LearnedMatt Braymer-Hayes, Erin Haswell · PyData Seattle 2017
• 29mLessons from a LibrarianZac Sweers, James Barr · Chicago Roboto 2020
• 57mLiving the Best Life on a Legacy ProjectJames Titcumb · PHP UK Conference 2023
• 41mLong-term Documentation MaintenanceKenzie Woodbridge · Craft Conference 2021
• 37mTaking a step back: Analysing your documentationLana Brindley · linux.conf.au 2021