@amardesich, I’m adding you to this conversation because I really think this is a good example of the challenges that we’re going to need to tackle with regards to comms & announcements. There are three posts on three different places regarding the content state:
The community post to announce the feature to the Atlassian end-users
The Content API in the change logs
Obviously, the community post does not include API documentation for developer. The change logs do not refer to the actual feature announcement, but only to the API documentation, and the announcement on CDAC only refers to the change logs.
For the developer community, this means that we need to get information from three sources and ask a forum question here on CDAC to get more insights into what feature has been released.
In order for us to truly benefit from the features Atlassian develops & releases, and to expand upon those features in our products to help unleash the potential of every team, we need a unified approach to announcements.