ualibraries / 500 Goto Github PK

• Try using a smaller or repeating background
• Menu background should occupy the full browser viewport height
• Font size should be the same as Browse all items link
• The rest of the body should be darkened when the menu is opened

The title for the first page in an exhibit needs to be hidden. We were going to use theme configuration associated with the homepage image for this.

or at least on my S7:

From http://speccoll.library.arizona.edu/online-exhibits/exhibits/show/reformation/late-medieval-catholicism

When reviewing the Universal Viewer display in the 500 theme, we noticed that the previous and next arrows on the side of the viewer only appear on hover. Is there a configuration option to make them display all the time?

Our Omeka theme currently does not display metadata associated with the file and the alt-text and title element both contain the filename.

We want to at least display the title of each file and improve the alt-text so that it includes the contents of the title field and the contents of the date field separated by a comma.

We don't want too much of the file metadata to show up on the item page. The title is OK and helpful, but the rest, if it is present, should be hidden by way of:

• Change the link so when the user clicks the file they see the file's page rather than the original image
• Add the metadata on the item, but hide it behind a hover effect or an expand/collapse UI control

Things to do:

• Display the title element from the file metadata and hide other metadata behind another user interaction
• Change the alt text to include (if available) the file's title and date. [dc:title], [dc:date]
• Remove the title attribute from the image because it would be redundant

Because the header assumes that we're in an exhibit, setting this to be the active theme on an entire Omeka site doesn't work. Omeka displays an error message: Omeka_View_Exception: A current exhibit variable has not been set to this view.

#21 may be the same or related

• Font size should be the same as Browse all items
• Link target area height should be decreased
• Wider, narrower background image assets should be used

Add visual styling for the item page so that it feels like part of the exhibit.

While working on the item page, make sure the metadata is easy to read and the value is distinguishable from the label.

• Reduce the width of the homepage image (upload a new asset in theme configuration)
• Make the fade to transparent gradient border around the homepage image more narrow (new asset)
• Reduce spacing beneath homepage image

https://masonry.desandro.com/options.html#horizontalorder

https://projects.invisionapp.com/d/main#/console/11557980/244111641/preview

Working on the css, yeah~~

Footer pagination background image is too big, we want to change it to fit the original design.
(pic1 is current look, pic2 is what we want)
In inspector, I changed .exhibit-nav-next a, .exhibit-nav-prev a { height to 3em, line-height to 3.3em} to get it looks like pic2.

Use the files from https://html5boilerplate.com/ as guides.

This notice shows up in the apache log when visiting exhibit pages:

PHP Notice: Undefined variable: exhibit in /path/to/local/site/themes/500/common/header.php on line 59

The current three books on homepage is small than the size in the original design, we will find a way to increase the size.

We might not use this layout in production.

We have the basic skeleton for our front-end build system, now let's flesh it out a bit more. This task encompasses:

• Adding a watch task for the CSS
• Adding an auto reload plugin (possibly the Browserify livereload plugin)
• Adding a .editorconfig so that syntax highlighting works
• Adding a CSS minifier
• Auditing the packages and removing any unnecessary ones

The item page needs to be themed so that images are large.

design review notes

When we looked at the text it seemed blurry or too bold. There was a significant difference in the rendering in chrome and safari, so much so that it looked like it might be loading the wrong font.

The original comp included 25 tracking. Letterspacing isn't usually recommended on the web for the sake of readability, but if the font still seems overly bold it might need an adjustment.

This comparison is chrome/linux vs macos/safari:

• Conditionally include the Universal Viewer at the top of the page based on the item type (set in Redmine issue 9760)
• If the Universal Viewer is included, don't display all the files separate from that
• If there's no UV, display the item files, then item metadata, and last citation and collection
• Remove the "Dublin Core" heading from the metadata section
• Make sure the exhibit header and navigation display and work correctly, so user could navigate to another section of the exhibit from the item page

We need to:

• Make the logo 75% width of the parent element
• Reduce the spacing beneath the logo

Chrome render text thicker than it should be, we will solve this. First pic is what looks like in Chrome, second pic is what it should looks like.


Here maybe the solution for that: http://www.kriesi.at/support/topic/font-weight-renders-very-different-depending-on-browsers/

And after adding those code h2 heading still thicker than it should be, we may need to change the font-weight to make it looks like the forth pic (third pic is what it looks like now)