normalize the docs nav menus#47
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Not sure that FAQ is a next step. :) Maybe move to See also?
Contributor
Author
There was a problem hiding this comment.
It looked odd to me that this list was out of sync with the nav menu. I could not find a way to re-order the nav items - I had wanted to move FAQ to near the end of the menu.
I'll push this down the list, or move to the see also section.
Contributor
|
Thanks! Since we're taking a look at this, not sure FAQ should be the first item in the top menu. |
Contributor
Author
|
Updated! |
Contributor
Author
|
(updated FAQ position; will land) |
devoncarew
added a commit
that referenced
this pull request
Nov 5, 2015
normalize the docs nav menus
techhtml
referenced
this pull request
in flutter-korea/website
May 29, 2019
/cookbook/persistence/key-value
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.
@sethladd