-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
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
doc: update README #4994
doc: update README #4994
Conversation
Seems fine :-) After @keturn brought it up I figure it may make more sense to just remove the build status rather than worry about fixing it. Little badges/shields were cool and neat a while ago for just being present, still kinda are, but more novelty than important. |
README.md
Outdated
### Requirements | ||
|
||
Technical Requirements: | ||
- Java SE Development Kit (JDK) 11. It may be possible to use a later version of the JDK for local development, but the CI will verify against this baseline version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would either omit the latter part of "It may be possible to use a later version of the JDK [...]" as it is kind of an advanced topic you won't need for general setup, and it is definitely not recommended to start that way, or link to #3976 for further details.
We should probably keep "[T]he CI will verify against this baseline version."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay the way I changed it?
@keturn asked some of our (currently many) newcomers how they found us. Many of them mentioned that they found us via GitHub, so I thought it might be time to update and improve our README a bit.
The improvements include a bit more structure, more references to resources we typically manually hand out to people on Discord. I hope that we can improve the onboarding experience for new contributors and reduce the manual effort related to having to answer the same questions over and over. If our engine github repo indeed is the entrypoint, then hopefully this works better than the previous attempt of linking the adventure site on our website or pinning responses to frequently asked questions in discord channels.
How to review
Preview of the overhauled readme
To see the bigger changes in comparison to the old readme, look at the diff of the second commit.
The third commit changes the file extension so github doesn't recognize it as the same file anymore.
The commits afterwards are minor fixes and improvements that can be reviewed after having reviewed the bigger changes as mentioned above.
TODO before merging
OR