A plugin system extends an application through separately developed components, but its technical promise matters only if users adopt it. Git history can reveal when that product bet was abandoned. section 6.5
Investigate a suspected retired plugin system by:
- Finding commits that delete five or more files from one folder; bulk deletion often signals a removed feature rather than routine cleanup. section 6.5
- Reading the complete git show diff, because filenames identify the removed area while deleted code reveals its actual user-facing behavior. section 6.5
- Recording the feature as a dated graveyard entry that explains what the team built and why it chose to kill it. section 6.5
Ghost’s abandoned plugin bet
Ghost’s membership pivot added members, Stripe, and the Portal UI while removing the original plugin system and v1 subscribers feature. The full diff distinguishes a finished capability from an abandoned stub. section 6.5
Figure 6.7 A project advertises what shipped, but its git history also records what was killed. These deletions (a plugin system that never found an audience, an AMP integration Google abandoned, a replaced subscribers v1) show which bets the team walked away from.

Compare shipped features with the plugin system and other bets the project abandoned. section 6.5
