Not sure I'm on board with the premise if the article. Author presents duplication of HTML elements as a commonplace exception to DRY; This is not what DRY is.

Can't agree to overturn a tried and true best practice, in favour of the opposite, as the article suggests. While easy to play around and adhere to the dogma of DRY at all costs; namely making code difficult to reason and taking ages to do it; we just call this premature optimisation - DRY done with no critical thought about priorities.

Tldr; don't optimise for DRY too early or at the cost of what's most important or expedient. Use common sense and adopt DRY only as far as necessary for your team and to help others extend and be efficient working with your code. Not a bad article but maybe just complicating what we already have a name for.