I’m part of a team that is using Stoplight in a hands-off, automated way (not using the Stoplight UI nearly at all), to construct and publish documentation after pulling in data from various repositories and sources in our project. We’re in the process of trying to close remaining gaps of migrating to Stoplight Next to do a similar workflow there.
Taylor has already showed me how to push our docs directly to the Stoplight Next git repo, and our script for doing this already works beautifully.
The only remaining gap we have is being able to trigger an update to the published documentation to point to the information from the latest commit in the git repo that we pushed to.
As such, closing this gap would be my highest priority feedback for Stoplight Next, so that we can publish programmatically, ferret out any remaining QA issues with our build scripts and data sources, then complete the migration.