Clearly Delineate What Constitutes an API
It would be great if developers could tell precisely what parts of our applications constitute a "public API". Concretely, this should allow them to look at the semantic version of any given release and be confident that their relying systems (or configuration changes) are safe or not.
For example, CSS class names of elements on the Data Explorer front page would not be considered a "public API" and thus are subject to change without warning. However, the Data Explorer settings file should be considered part of a "public API" and thus anything short of a major version bump should never break somebody's configuration.
One edge-case I can think of is the config service itself. Given that it's potentially possible to access it from non-DotStatSuite applications, one might be tempted to put one's own configurations or assets in there. However, do we consider it to be a "public API", or do we reserve the right to alter it without warning?