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
docs.rs doesn't provide documentation for main; which can lag behind the latest release.
This also makes it hard to show off new merged documentation improvements.
Host the latest nightly docs on bevyengine.org, rebuilt after every merged PR.
Clone the bevy repo and use cargo doc. This can't be linked, goes stale, takes a while to build and is harder for beginners.
Discussed in #1721 and on Discord.
The text was updated successfully, but these errors were encountered:
Why not host on GitHub pages for this repo ? That would be the simplest
Sorry, something went wrong.
I like this actually. It also makes it less discoverable for beginners, which is a benefit in this case.
Seems like this is resolved by #3535 and followup PRs. Closing this.
No branches or pull requests
What problem does this solve or what need does it fill?
docs.rs doesn't provide documentation for main; which can lag behind the latest release.
This also makes it hard to show off new merged documentation improvements.
What solution would you like?
Host the latest nightly docs on bevyengine.org, rebuilt after every merged PR.
What alternative(s) have you considered?
Clone the bevy repo and use cargo doc. This can't be linked, goes stale, takes a while to build and is harder for beginners.
Additional context
Discussed in #1721 and on Discord.
The text was updated successfully, but these errors were encountered: