Authorization page layout #42573

Closed
opened 2014-11-12 00:30:23 +01:00 by Francesco Siddi · 10 comments

Since Blender-ID will soon support OAuth, we would need a layout, similar to 1c3cb4045e00e68194c701d5b99b8761.png. There is already an authorize.html file in the templates folder that could use the treatment.

Since Blender-ID will soon support OAuth, we would need a layout, similar to ![1c3cb4045e00e68194c701d5b99b8761.png](https://archive.blender.org/developer/F123359/1c3cb4045e00e68194c701d5b99b8761.png). There is already an `authorize.html` file in the `templates` folder that could use the treatment.
Author
Owner

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @niklasravnsborg

Added subscriber: @niklasravnsborg

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Niklas Ravnsborg-Gjertsen self-assigned this 2014-11-30 14:38:53 +01:00

I committed a basic design for that :)
Blub_s_Profile_Blender_ID_blender.org.png

I committed a basic design for that :) ![Blub_s_Profile_Blender_ID_blender.org.png](https://archive.blender.org/developer/F127995/Blub_s_Profile_Blender_ID_blender.org.png)

Added subscriber: @pablovazquez

Added subscriber: @pablovazquez

Looks good! We checked it out with Francesco and have some suggestions.

The width of our site is quite big, and since this is a single-action page, we could use a smaller layout for this bit. Perhaps a col-md-6 + col-md-push-3

We are missing:

  • App's logo
  • App's description
  • App's link
  • Permission's description
  • Read more about OAuth
  • Cancel button

What we don't really need:

  • Our name + our email (it's on the subnav anyway)

I made a quick mockup tackling these issues.
page_oauth.png

  • The blue circle would be the app's logo (if none we show fa-question), the green circle is our avatar (if none we show fa-user)
  • The arrows inbetween is just a white fa-arrows-h.
  • The title "Authorize Application" instead of "Authorize app-name" is better because we can predict the size and make it look nice, otherwise we risk beautyness when apps have long or too short names.

What do you think?
Cheers!

PS: Pushing into master is only for final or almost-final (that we know is not going to change much, only eventual fixes) stuff. For WIP you should create a diff.

Looks good! We checked it out with Francesco and have some suggestions. The width of our site is quite big, and since this is a single-action page, we could use a smaller layout for this bit. Perhaps a col-md-6 + col-md-push-3 We are missing: - App's logo - App's description - App's link - Permission's description - Read more about OAuth - Cancel button What we don't really need: - Our name + our email (it's on the subnav anyway) I made a quick mockup tackling these issues. ![page_oauth.png](https://archive.blender.org/developer/F128652/page_oauth.png) - The blue circle would be the app's logo (if none we show fa-question), the green circle is our avatar (if none we show fa-user) - The arrows inbetween is just a white fa-arrows-h. - The title "Authorize Application" instead of "Authorize app-name" is better because we can predict the size and make it look nice, otherwise we risk beautyness when apps have long or too short names. What do you think? Cheers! PS: Pushing into master is ***only*** for final or almost-final (that we know is not going to change much, only eventual fixes) stuff. For WIP you should create a diff.

All right! Looks awesome. I will create a patch! Thank you!

All right! Looks awesome. I will create a patch! Thank you!

Changed status from 'Resolved' to: 'Open'

Changed status from 'Resolved' to: 'Open'

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sign in to join this conversation.
No Milestone
No project
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/blender-id#42573
No description provided.