I’ve worked on more than half-a-dozen AsciiDoc-based docs-suites. And every one of them has also been an Antora project. And exactly none of the companies that I’ve worked with on these AsciiDoc-based docs is interested in switching away from an Antora-based build chain.
Which makes adoc-studio a non-starter for their technical writers.
By support I don’t automatically mean full-blown Antora playbook support. But the ability to parse an AsciiDoc project that will be built by Antora and present said project for editing and previewing within adoc-studio.
That is for adoc-studio to
  1. understand the Antora-specific directory structure, <https://docs.antora.org/antora/latest/organize-content-files/>;
  2. understand Antora’s notions of components and modules; and
  3. be able to preview not just individual pages, but the project.