Skip to content

101 add antora file structure requirements#102

Open
Bill Traynor (wmat) wants to merge 3 commits into
mainfrom
101-add-antora-file-structure-requirements
Open

101 add antora file structure requirements#102
Bill Traynor (wmat) wants to merge 3 commits into
mainfrom
101-add-antora-file-structure-requirements

Conversation

@wmat

Copy link
Copy Markdown
Collaborator

Updates for Antora

Signed-off-by: Bill Traynor wmat@riscv.org
Signed-off-by: Bill Traynor wmat@riscv.org
Signed-off-by: Bill Traynor wmat@riscv.org
number = {6},
pages = {1688-1698},
month = {December}
}

@kersten1 Kersten Richter (kersten1) Jun 10, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should add the @ misc example and info about using it rather than @ electric

@@ -0,0 +1,2 @@
[index]
== Index

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add the rest of the page, including the riscv image, title, and then what to put on the front page.

@@ -0,0 +1,78 @@
= RISC-V Example Specification Document (Zexmpl)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don't use this in antora? do we need both? Is this just to build the PDF? and if so, does this mean that we aren't going to use the antora pdf generator?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if this file is there and isn't included in the nav file, antora kicks up an error about orphan files.

====

[preface]
== Copyright and license information

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Split this out into a new page for antora. All the rest are set up like this

Comment thread modules/ROOT/nav.adoc
// https://docs.antora.org/antora/latest/navigation/
//
// Update this file to reflect your specification's chapter structure.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this needs a title - the nav title which is sometimes shorter than the full spec title.

.title

Comment thread modules/ROOT/nav.adoc
// Update this file to reflect your specification's chapter structure.

* xref:spec-sample.adoc[RISC-V Example Specification]
** xref:intro.adoc[Introduction]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

most of the nav files use a flat structure? So they are all just a single *

Comment thread antora-playbook.yml

ui:
bundle:
url: https://gitlab.com/antora/antora-ui-default/-/jobs/artifacts/HEAD/raw/build/ui-bundle.zip

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Antora file structure requirements.

2 participants