You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attached are the desktop views that I see for the work page.
Comments:
Thinking about the transition/deployment:
It would be good to use a a different base template ("newbase.html" in stead of "base.html") so that pages could be deployed one by one.
People hate drastic changes. so where ever you can, use designs that evoke the previous design. Trivial example - make the header background color the same as before.
Non-trivial example: don't change the nav menu to a "hamburger" on large screens.
Design issues
logo size/position bothers me. As it is, my eye wants the text to line up
search box has become more prominent. Do we want this on the work page? Will people think it's for searching the book?
buttons. some have rounded corners others don't. What do our colors mean? does the ">" in Sign up still make sense? Is the text bold enough? Should "add to fave" be buttonified?
why added text on Goodreads/LibraryThing/Worldcat/OpenLibrary ? Also, if text is added, the whole region should work as a button.
Download button is key function on this page; is it noticeable?
cover. white covers don;t work. add border as we have now?
center column. Text running up to edge very hard to read. Font sizes should be more balanced, lines in abstract too long for good readability. see https://baymard.com/blog/line-length-readability
the title and author fields will look very awkward with long titles and many authors.
need to add back content/functionality (you already know this) but maybe the way to do this is to chunk out the existing templates, separating the function from the layout.
With respect to https://github.com/EbookFoundation/regluit/tree/newfoundation -
(works with production database)
Attached are the desktop views that I see for the work page.
Comments:
It would be good to use a a different base template ("newbase.html" in stead of "base.html") so that pages could be deployed one by one.
People hate drastic changes. so where ever you can, use designs that evoke the previous design. Trivial example - make the header background color the same as before.
Non-trivial example: don't change the nav menu to a "hamburger" on large screens.
old-workpage.pdf
new-workpage.pdf
The text was updated successfully, but these errors were encountered: