Skip to content

break extension conventions into two reference pages#1529

Merged
bashbaug merged 1 commit intoKhronosGroup:mainfrom
bashbaug:extension-conventions-refpages
Mar 3, 2026
Merged

break extension conventions into two reference pages#1529
bashbaug merged 1 commit intoKhronosGroup:mainfrom
bashbaug:extension-conventions-refpages

Conversation

@bashbaug
Copy link
Contributor

Apparently the reference page markup cannot span multiple sections without generating asciidoctor rendering issues. So, break the "extension conventions" reference page into two pages - one for "naming conventions", and another for "header conventions", where each page consists of a single section.

Copy link
Contributor

@kpet kpet left a comment

Choose a reason for hiding this comment

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

As discussed, not ideal, but still better than the broken document we currently have.

@bashbaug
Copy link
Contributor Author

bashbaug commented Mar 3, 2026

Merging as discussed in the March 3rd teleconference.

@bashbaug bashbaug merged commit f2f5da5 into KhronosGroup:main Mar 3, 2026
2 checks passed
@bashbaug bashbaug deleted the extension-conventions-refpages branch March 3, 2026 17:23
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.

2 participants