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

Overall structure of Source Academy UX #81

Closed
martin-henz opened this issue Jun 4, 2018 · 10 comments
Closed

Overall structure of Source Academy UX #81

martin-henz opened this issue Jun 4, 2018 · 10 comments
Assignees
Labels
proposal Tentative suggestion inviting discussion
Projects

Comments

@martin-henz
Copy link
Member

martin-henz commented Jun 4, 2018

Current structure

Cadet | DEVICE </> PLAYGROUND

Under "DEVICE":
Missions | Side Quests | Paths | Contests Announcements | Materials | Profile

Proposal

Source Academy | News | Material | Playground <USER_ICON> Thomas Tan

Under "Source Academy":
Missions | Side Quests | Paths | Contests

Notes:

  • "Materials" renamed to "Material" (that's grammatically better, see https://english.stackexchange.com/questions/247497/material-vs-materials-which-is-correct)
  • "Cadet" renamed to "Source Academy"
  • "Announcements" renamed to "News"
  • The <USER_ICON> could come from the IVLE student picture.
  • Clicking <USER_ICON> or "Thomas Tan" will take the users to their Profile
  • Before the first login, there would be "Login" instead of "<USER_ICON> Thomas Tan"
  • I'm assuming that we treat News, Material and Playground as public information; anyone can see this without login.
  • Before the first login, the clicking of "Source Academy" is disabled, and no Missions etc are displayed.
@martin-henz martin-henz added the proposal Tentative suggestion inviting discussion label Jun 4, 2018
@martin-henz
Copy link
Member Author

The toplevel could also consist of pictograms:
Source Academy | News | Material | Playground <USER_ICON> Thomas Tan
-> (for example)

  • <USER_ICON> Thomas Tan

@remo5000
Copy link
Contributor

remo5000 commented Jun 5, 2018

Sounds good!

@remo5000 remo5000 added this to To do in Sprint 2 via automation Jun 5, 2018
@remo5000 remo5000 moved this from To do to In progress in Sprint 2 Jun 5, 2018
@remo5000 remo5000 mentioned this issue Jun 5, 2018
@remo5000
Copy link
Contributor

remo5000 commented Jun 5, 2018

I think a combination of an icon and the word works well. I have added the admin and game buttons as well (as they have been scaffolded). Is this something like what you had in mind? @martin-henz

image

@martin-henz
Copy link
Member Author

martin-henz commented Jun 5, 2018

Generally ok. Three comments:

  • Maybe if there is not enough space, such as when viewed on a mobile device, the words can go away?
  • What is that "Game" button for? Could we do away with the "Game" button by combining it with the "Source Academy" button?
  • Can we avoid ALL CAPS for the menu items? In most fonts, words get less readable when rendered in ALL CAPS. Some reading about this:
    https://danieltitus.com/blog/advertising/237-why-all-caps-is-usually-a-bad-idea

@remo5000
Copy link
Contributor

remo5000 commented Jun 5, 2018

@martin-henz

  • We shall address the space issue when resolving Make Navbars responsive #76.
  • The Game button is for the "story". I can move it into Source Academy.
  • The article makes a lot of sense, I'll remove the all caps. Thank you for the feedback! 😄

One question: Given that the back end models refer to "Announcements", could we keep that name instead of "News"? This would allow the button to match the filenames, making it clearer in terms of software design. The visuals, front end and backend would then be consistent.

@martin-henz
Copy link
Member Author

martin-henz commented Jun 5, 2018

Regarding the "game": In theatre, we call it "breaking the fourth wall", when we remind the audience that they are sitting in a theatre. That's generally avoided. In the same way, if we say the Source Academy is a game, we want to immerse the audience in it. So ideally, the game should be the default, and we shouldn't remind the audience that it's a "game" by having a menu item "Game". So how about taking the users (who are authenticated) by default to the game. Then they can escape the game using the buttons. But the "home" button, called "Source Academy" at the top left takes them to the game. Once they are in the game, they can "escape" in two ways: They can choose a top-level item and escape their identity for a while, by going to "Material" or the "Playground" or they can choose an "in-game" item by going directly to a "Mission", "Side Quest" etc.

@martin-henz
Copy link
Member Author

(maybe we can discuss during the meeting on Saturday)

@remo5000
Copy link
Contributor

remo5000 commented Jun 5, 2018

@martin-henz I have made the changes you requested, it looks like this now! Kept the upper case on the title to make it prominent.
image

You make a good point on the "fourth wall"! I feel intuitive UX should have a clear "path" to get to a certain display/state. Perhaps we could rename the button to make it immersive, in the sense that it isn't an offshoot from the idea of a "Source Academy" e.g "Spaceship". That being said, looking forward to discussing this further during the meeting 👍As for now, is the above layout alright?

@remo5000 remo5000 moved this from In progress to To do in Sprint 2 Jun 6, 2018
@martin-henz
Copy link
Member Author

What if the "Source Academy" button takes you to the current game state and shows the buttons "Missions", "Side Quests", "Contests"? What if that's the default view after authentication? This way, the game would be the default, but opting out would be very easy: just click on any of the buttons.

@ning-y ning-y closed this as completed in 1ddb02f Jun 6, 2018
Sprint 2 automation moved this from To do to Done Jun 6, 2018
@remo5000
Copy link
Contributor

remo5000 commented Jun 6, 2018

@martin-henz Ah I see your idea a bit more clearly now. We've implemented it in #85 (commit is above), thank you for the feedback once again!

Aulud pushed a commit to Aulud/cadet-frontend that referenced this issue May 25, 2020
* Change public subnet CIDRs

* Add subnet for postgresql RDS

* Add aws_db_instance

* Change ssh key

* Add variables for RDS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal Tentative suggestion inviting discussion
Projects
No open projects
Sprint 2
  
Done
Development

No branches or pull requests

4 participants