Skip to content
This repository has been archived by the owner on Feb 19, 2022. It is now read-only.

General thoughts for design tweaks #109

Open
2 of 4 tasks
mialondon opened this issue Aug 3, 2013 · 6 comments
Open
2 of 4 tasks

General thoughts for design tweaks #109

mialondon opened this issue Aug 3, 2013 · 6 comments

Comments

@mialondon
Copy link
Contributor

  • remove the 'go to top' button from secondary content pages
  • Tighten up the spacing between the text box and the 'make some magic' button so the relationship is really clear - at the moment the button is closer to the footer than the text box. See Front page 'get started' call to action #143
  • Introduce some separation between the 'Go home and feed the machine new text!' and 'Like what you see? Save these results (will open on another page)' texts, as it looks like a paragraph and header rather than two separate actions. See Front page 'get started' call to action #143
  • On a small screen that shows only the logo and three steps, there's no indication that there's more below. (And we have two pieces of anecdotal evidence via reports from friends that people thought that was the whole page). We could tighten up the whitespace so the call-to-action text is more likely to be visible, or use a design element to direct attention down. Thoughts? See Front page needs an indication of more content or cues to scroll down #119
@scottkleinman
Copy link
Contributor

Just my thoughts:

  • The about and connect pages are right on the edge of where a 'go to
    top' link is useful. An alternative to removing it is to restyle it to be
    less prominent (the button was really just to get the element in there).
  • I agree.
  • I think tightening up the whitespace a bit is a good idea, but we
    should try something more radical for mobile screens. At present, I don't
    have a good suggestion.

On 3 August 2013 13:25, Mia notifications@github.com wrote:

remove the 'go to top' button from secondary content pages

Introduce some separation between the 'Go home and feed the machine
new text!' and 'Like what you see? Save these results (will open on another
page)' texts, as it looks like a paragraph and header rather than two
separate actions.

On a small screen that shows only the logo and three steps, there's no
indication that there's more below. (And we have two pieces of anecdotal
evidence that people thought that was the whole page). We could tighten up
the whitespace so the call-to-action text is more likely to be visible, or
use a design element to direct attention down. Thoughts?


Reply to this email directly or view it on GitHubhttps://github.com//issues/109
.

Scott Kleinman
Professor of English
Director, Center for the Digital Humanities
California State University, Northridge

@fontnerd
Copy link
Contributor

fontnerd commented Aug 4, 2013

I will offer some suggestions when I'm at a computer.
On Aug 3, 2013 4:25 PM, "Mia" notifications@github.com wrote:

remove the 'go to top' button from secondary content pages

Introduce some separation between the 'Go home and feed the machine
new text!' and 'Like what you see? Save these results (will open on another
page)' texts, as it looks like a paragraph and header rather than two
separate actions.

On a small screen that shows only the logo and three steps, there's no
indication that there's more below. (And we have two pieces of anecdotal
evidence that people thought that was the whole page). We could tighten up
the whitespace so the call-to-action text is more likely to be visible, or
use a design element to direct attention down. Thoughts?


Reply to this email directly or view it on GitHubhttps://github.com//issues/109
.

@moltude
Copy link
Contributor

moltude commented Aug 5, 2013

  • Agreed.
  • Agreed that there should be less space between the box and the button. I don't know if this has been mentioned in previous tickets (so please ignore if this is been discussed and decided) but I think that bringing the 'Grab text' box and the 'Zotero box' should be more horizontally aligned (I think the box should only be as big as the placeholder text we have in there).
  • Agree as well, did you want to keep the same formatting?

@fontnerd
Copy link
Contributor

fontnerd commented Aug 5, 2013

A few other issues I'd like to get to:

• I made a class called ".main" that, if added to the about and connect page divs would update the styling of the h2s + h3s to the same red color found on the homepage, as well as the Typekit webfonts. The class rule is in the "base.css" folder but the class isn't assigned in the HTML.

• increase the margins on the left / right of the about + connect page. As of right now, the line length is a bit long for optimal reading but this is quasi-minor. 30px on the left (to better align with the serendipomatic logo) and 10px on the right should do it.

• the hover state on the "Make Some Magic" button should have a shadow of #FFFFFF instead of #000000. The black shadow and black text look weird.

• on the results page, the "Go Home" should definitely have more separation from the "Save Results" action and perhaps that entire section can move down a bit.

I'm still a bit unclear where I am supposed to make any of these changes and terrified of screwing things up.

@mialondon
Copy link
Contributor Author

@fontnerd - I'll have to check back through the discussion but if you push changes from your laptop or directly on the site, they should be honoured as people will check for any more recent changes (with re-merge) and merge any lines individually before committing their own stuff.

Can we also have external links as a slightly different colour (perhaps darker so less prominent) than internal app links? The idea being that it helps keep attention on the main call-to-action in using the site (especially the first time).

@mialondon
Copy link
Contributor Author

Forgot to add, when you submit to master it should deploy to http://dev-serendipomatic.herokuapp.com/ so you can see it all... (Clearly I should either edit or respond to OWOT emails, not both!)

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

No branches or pull requests

4 participants