Don't shoot yourself in the foot with content reuse
summary
JetBrains documentation teams explain reuse across a dozen IntelliJ-based IDEs, with about 20 technical writers sharing source and exposing four reuse problems: abuse of reuse, source-code reduction, misuse of reuse, and traffic cannibalization. Examples show nested includes, UI string IDs, SEO losing to earlier-indexed pages, and the cost of tiny conditional snippets. Solutions include an in-house style guide, automated checks, a Slinter MVP, editor UX that renders includes in-context, templates/completions, metadata and publishing cadence to avoid cannibalization.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:58Overview
- 3:50What is single sourcing
- 4:57Definitions
- 5:45Example
- 9:29Abuse of reuse
- 13:15Strategies to avoid abuse
- 14:42Source code reduction
- 21:42Misuse of reuse
- 27:16Monster traffic cannibalization
- 28:03Search query example
- 28:33Traffic cannibalization
- 29:43What can we do
- 32:15Summary
related talks
50mReading code
44mIntelliJ IDEA-based IDEs Tips & Tricks
59mTechniques for writing high-quality code
31mStrengthen Our Developer eXperience to Face Obsolescence and View...
01h 03mWhy Do Developers Love IntelliJ IDEA?
51mIntelliJ IDEA-Based IDE Tips & Tricks
45mHow to Design an IDE-Friendly Language
52mIntelliJ IDEA Tips and Tricks