Add a docs directory and move the third-party add-ons page here. #1438
+147
−0
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
|
As we do per language docs, should they go here or should each language also do a docs directory? |
|
I think putting all docs in a single directory tree is more manageable and is also easier for users to navigate. I suggest we add language subdirectories to this docs directory. Sounds reasonable? |
|
Works for me. |
|
LGTM |
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.
Ideally we should migrate everything from the developer guide to g3doc and keep it sync with this docs directory. Even if we can't get to that point, adding a docs directory to host opensource only docs (like this third-party add-ons page) still makes sense.
@pherl to review