A blog is the heartbeat of your API operations, and having some participation by each API over time is essential to API governance. It doesn’t matter if your API is internal, partner, or private, you should have some sort of blog or wiki page dedicated to communicating with stakeholders producing or consuming APIs.
Blogs haven fallen out of popularity with mainstream discussions, but they are still very much in use by platforms, and used to share information via internal channels and external social media. Add to your list of policies for new APIs to be announced via blog and consider what can be shared about use cases or when updates are made to an API.
Keep you API platform blog updated and active. Use blogs to educate and inform. Bring in guest posters, and push teams producing APIs to write. Blogs are a great way to communicate around a platform and don’t have to receive huge amounts of page views to have an impact on teams who are producing APIs, as well as consumers who are putting them to work.