Hi David, On Fri, Sep 10, 2021 at 7:36 PM David Jencks <david.a.jen...@gmail.com> wrote: ...snip... > I certainly agree build speed is important. However, I also think that we > should make it difficult for people to edit the docs and not look at the > results: this is analogous to changing the java code and not checking whether > it compiles. The idea behind Dan’s site-manifest idea is that a site build > can produce a json file listing the files or resources in the Antora catalog > and then another site build can read that in to the catalog to resolve xrefs > etc. In the case of a component or similar project, the idea would be to > build just the single doc page for that component, but have the xrefs > resolved to the main site. Since we’d only be building one page, it should > be very quick. > > This is definitely not a solution available out-of-the-box now but perhaps > something to think about and aim for for the future. Among other things we’d > have to make the UI bundle accessible and the main site site-manifest > accessible. > > If we can get this to work then the question opens of whether validating the > .adoc files is better done in javascript as part of the (1-page, here) site > build or in a maven plugin.
Oh, that seems really neat, so let's watch out for the site manifests and try to get them working when it's shipped in Antora. With ASF policy on how websites are built/distributed I'm not sure if we can leverage distributed website build, but that might be something we can look into. zoran -- Zoran Regvart
