We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We could presumably use Jekyll to generate the table of contents to avoid title duplication. Perhaps we could generate "see also" link titles as well.
The text was updated successfully, but these errors were encountered:
@bgrainger and I discussed this and opted for the wiki because we want to encourage casual edits from consumers of the package.
However, it might be interesting/worthwhile to add a build step that validates/updates the wiki based on the code.
Sorry, something went wrong.
No branches or pull requests
We could presumably use Jekyll to generate the table of contents to avoid title duplication. Perhaps we could generate "see also" link titles as well.
The text was updated successfully, but these errors were encountered: