Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up a redirect directly to a pattern library if project and aspect <2 #16

Open
CSergienko opened this issue Jan 18, 2017 · 2 comments

Comments

@CSergienko
Copy link
Contributor

If there is < 2 items in a step in the navigation from project to aspect to patterns, Mote should simplify the user's life by automatically redirecting to the next step which has >2 items.

To illustrate, assuming the following file tree:

.
└── mote
    └── projects
        └── my-project
            ├── website

We have only one project (my-project), and one aspect (website). Right now, when a user browses to myproject.com/mote they are greeted with a navigation that forces them to navigate manually through to the pattern library, despite there being only one possible path to navigate.

What I am proposing is that in the event of there being, for example, one 'project' and one 'aspect', that /mote automatically redirects to the pattern library - myproject.com/mote/project/my-project/website/.

If there is one project and two aspects, it would then redirect to the aspects view - myproject.com/mote/project/my-project/.

If there are two projects and one aspect each, it would allow the user to select the project and it would navigate directly to the pattern library, skipping the 'aspect' part.

Finally, if there is only one project, one aspect, and one category of pattern (e.g Atoms), it would redirect directly to Atoms.

@CSergienko
Copy link
Contributor Author

@hedleyroos @Pringels The existing Mote explorer could still benefit from this IMO, but is it worth considering this feature in your eyes?

@Pringels
Copy link

The deeply nested navigation is quite cumbersome, so I think it's a useful feature to add.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants