Disable Antora support for files ignored by Antora

Why the new feature should be added

1. According to Antora documentation Antora ignores any files stored in hierarchy that begin with a dot (.). If there is a file that starts with a dot, it will be ignored by Antora and won’t be published.

2. Antora has nav files that have the following structure:

   .Nav title
   * xref:Annotation.adoc[Annotation]
   * xref:Introduction.adoc[Introduction]
   ** xref:Scope.adoc[Scope]
   

3. I’ve made a copy of a nav file with the following structure:

   .Nav title
   * include::pages/Annotation.adoc[Annotation]
   * include::pages/Introduction.adoc[Introduction]
   ** include::pages/Scope.adoc[Scope]
   

4. I gave the copied and altered nav file a name starting with a dot so it will be ignored by Antora.

5. Opened the project with IntelliJ, it is displayed like this:

6. If I copy the module folder where this file is located and put it separately from Antora, then open it with IntelliJ, it will open as desired:

How the new feature should work

It appears that some of the Antora settings interfere with the AsciiDoc document’s settings. Is it possible to (automatically or manually) disable Antora support for files that should be ignored by Antora i.e. starting with a dot?

[ahus1]

I created a follow-up issue for this to take care of soft-set attributes in the Antora component descriptor: #798

[Grolribasi]

You’re probably right. I didn’t think of the other side of the case when someone actually wants it to work this way. And it is not recommended to use == for headings and amend it with :leveloffset: anyway. I will close the issue then.