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

Stay more user-friendly than autogenerated forms #35

Open
janbrohl opened this issue Jun 2, 2016 · 3 comments
Open

Stay more user-friendly than autogenerated forms #35

janbrohl opened this issue Jun 2, 2016 · 3 comments

Comments

@janbrohl
Copy link
Collaborator

janbrohl commented Jun 2, 2016

Via autogenerated editors users can make schema-valid ckan files and someday when there is a netkan-schema, netkan files, too.

These editors do not seem to provide a user-friendly workflow - this webtool should stay better.

One example for a generated form is at https://gist.github.com/janbrohl/0c9aa1c8d026b7b5e4e4cd3c869e42f5

@janbrohl
Copy link
Collaborator Author

janbrohl commented Jun 2, 2016

I think a more natural-dialog-like workflow would be friendlier than the quite formal approach i took until now.

I imagine the users to start at a small page with info about NetKAN and stuff with some basic questions.
From there they are taken to further question-forms, taking a route based on their answers.
They would end on a page where a simple view of all data to be put in the netkan-file with short explanation what it means to make sure everything is OK. On that page there would be buttons to submit, download a dump or re-edit parts that are not right.

Example for dialogification like I imagine:

instead of form:

KSP Version [_____]

More natural statements:

This mod was made for KSP []
[ ] but should work with about any version
[ ] but is known to work with versions from [
] up to [____]
[ ] and I am quite sure it only works with exactly that

@politas
Copy link
Member

politas commented Jun 2, 2016

As long as the hand-holding doesn't force users into a strict pathway, and previous selections are retained if a user goes back and forth, then sure. Would generally be better to use divisions on a single page as you have been, though perhaps with a tabbed interface, rather than entire separate pages, I think.

@janbrohl
Copy link
Collaborator Author

janbrohl commented Jun 3, 2016

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