Change landing page to repositories #190
Open
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
Currently the landing page is the home page but that requires the user to make one mouse click to navigate to the repositories page which is where the action is. This change set just updates the default landing route from Home to repositories (with a default page of 20). The Home page still exists but is not the default location the user lands on when going to the site. This fixes issues kwk#34
bvanderlaan
force-pushed
the
default-to-repositories
branch
from
39f44dd
to
4419f2a
Compare
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.
Currently the landing page is the home page but that requires the user to make
one mouse click to navigate to the repositories page which is where the action
is. This change set just updates the default landing route from Home to
repositories (with a default page of 20). The Home page still exists but is not
the default location the user lands on when going to the site.
This fixes issues #34