Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I guess this is a quite opinionated thing to do, so please feel free to close if you don't like it.
Merging this would add automatic publishing of a generated API reference to GitHub pages. To properly work it would additionally require some GitHub pages setup, e.g. adding a custom domain (having a custom domain is not required though).
I personally think having this kind of API reference available would be helpful to get a quick overview of what SharpIppNext has to offer and how it works. What you get is similar to what can be achieved using Visual Studio's Object Browser or IntelliSense.
To get a first impression how this would look like, you can take a look at a similar docs page I create for one of my projects: https://fastberttokenizer.gjung.com/
Alternatively you could locally execute from repo root of this PR's branch:
But I'd also understand if you don't want to take the additional maintenance burden. Thanks for creating a modern printing solution for the .NET ecosystem!