docs: installation and proposed doit interactions #66
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 was thinking through how to make the feedback tool useful and have pretty much decideddoitwill be the easiest, but I wanted to think through the subcommands we would need and how they would interact first, so I took at a spin at putting together the documentation focused on how the feedback tool would fit into the process. I think this approach should work, but I'm open to better approaches! Hopefully this doesn't duplicate any work you've started on the onboarding docs, but this didn't take too long to put togetherUpdate: I meant to submit this PR to our fork where we are working on a game to teach software design best practices as part of a graduate course. We forked community-rpg initially so that we could put together an MVP and focus on the user experience and feedback tooling. We wanted to build on top of arcade and will need to make a lot of changes or write a new game for our use case, but I hope you don't mind that we've started by incorporating this game into our prototype in the first iteration?