Conversation
This file contains hidden or 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.
Closes #
I've struggled for quite a while now with how to organize the docs in our repo to align with our docs.openlibrary.org site.
For now, this is the solution. It's a somewhat minimal change that clarifies the purpose of these docs so that they're well aligned with our docs site.
Contributing is now about norms
Docker is more strictly about docker (points to other pages as needed)
readme.me (root) is a simple pointer to a few other resources.
After having several people tell me it wasn't clear that docs.openlibrary.org exists after looking at the repo this is going to fix that and get people to the latest and greatest info.
I need to merge now so these updates can be imported into the main docs site since I have other changes up there that are aligned. However, I would very much welcome feedback on this and suggestions to improve!
Technical
Testing
Screenshot
Stakeholders