Earlier quoted context omitted.
DigitalOcean’s strategy with evergreen technical content was to duplicate Linode’s strategy with evergreen technical content wholesale , down to individual articles. Linode Library, including a complete custom CMS and community engagement strategy to pay Linode users to help generate evergreen, was in place and driving conversions long before DigitalOcean was founded. They cribbed just about everything substantive fr…
You're right that the Linode library existed prior to DigitalOcean's founding but DigitalOcean did innovate: they understood the value of technical writing as a conversion tool, and paid for it. Linode did not pay for articles until more recently, and so the Linode library was comparatively weak for a long, long time. The Linode library was helpful for customers, certainly, but it was never comparable to what Digital…
Of course Linode eventually copied DO back. That was the terms of the relationship established by DO. We were too busy dreaming of copying AWS at the time to see the threat. We ruled out $10 and lower Linodes again before DO was founded due to our support resources. DO forced that hand later (I assume, that was after I left).
I am obviously biased having worked there (worth noting I left on awful terms), and I am aware of that, but some of what I’m saying is purely objective and, again, probably provable with study of IA. If you’re going to refute my first hand, lived experience and call it revisionism, you’ve proven my point of making this comment at all.