jaguillette / hvd-dh-omeka-theme Goto Github PK
View Code? Open in Web Editor NEWThis is a theme for Omeka developed for use in the Harvard History Department
License: GNU General Public License v3.0
This is a theme for Omeka developed for use in the Harvard History Department
License: GNU General Public License v3.0
What it says on the tin. Have to make sure appropriate hooks are on the show item page.
In the spirit of trial and error...
Could we go back to default Collections display, at least for a bit? I am beginning to see that there are instances in which it makes good sense to use the default, and others in which the Gothic Past model is preferable. Actually, is it possible to make that an option for each Collection?
The real trouble with the default is that it only shows 10 Items, and provides no "next 10" option. If you could engineer a solution to that, perhaps that would be ideal (though I am not yet sure).
The trouble with the Gothic Past model is that the list of Items gets orphaned (example).
When Waypoints are enabled, but Simile is not, there's a gap between the waypoints box and the edge of the page. Removing this space and increasing waypoints transparency was requested by a faculty member.
The headings in exhibit pages are out of sequence, and skip h3.
Assuming that markdown rendered by Atom is copied and pasted into the theme, it should display in a way that makes sense.
Similar to options for "Thanks Roy" and "Seasons" themes, provide an option to display images on item displays as a gallery of images, while preserving the lightbox gallery that we have.
See about making browse by tag display more word-cloud like, aesthetically pleasing, and ordered.
For single-page exhibits, add an option to hide navigation for them, so that the content can take up the full page width, either through a setting or by checking the number of pages, or possibly both.
Just a follow-up to our conversation: if you could fandangle a way to produce iframe embed codes (that is probably not the right combination of words, but you know what I mean) for Neatlines, that would be amazing. That way we could embed bits of Neatline as "files" for Omeka Items.
Going to make this toggleable, so that you can preview items or not on the Browse Collections page. Removing previews was requested by faculty.
Currently the alt text is just the file name, which isn't communicated or changeable, resulting in poor image accessibility. Adding the title of the associated item should help.
What it says on the tin. Add a way to toggle exhibit cover image for individual exhibits.
For main site nav, add option to switch to vertical arrangement
This has two parts. The focus indicator is messed up, and doesn't properly highlight the advanced search button. The advanced search button also doesn't properly respond to standard keystrokes, as space does not activate it, and escape does not dismiss the pop-up
You can currently set a description for the Browse Exhibits page, but it was requested that this be visually distinguished in some way.
Request for pop-up footnotes in the style of xkcd what if.
In headers and footers, the focus can sometimes be partially hidden, when it should be totally visible in all cases.
The "skip to content" link currently has a transparent background when activated by tabbing through the site. This should have a color background with sufficient contrast.
When you zoom in on some pages, text gets cut off.
It would be helpful if Item pages could allow text to flow around the images (i.e. fill in the space width-wise below the item thumbnails).
When navs have multiple lines and a hierarchical layout the lower level nav links aren't accessible because the minimize as soon as the mouse goes off of the title.
The navigation bars on the site are just identified with "navigation", not with anything more specific to make them identifiable to users of screen readers.
Any chance you could install the following plugins?
Item Order (for Collections)
Zoom.It
In items/show
, the image display JS prompts to download tif images, when the usual behavior is to show a larger version of the image. Either this shouldn't happen, or maybe the JS should be disabled when the IIIF Toolkit or Universal Viewer plugins are active.
Currently images can only be displayed up to "fullsize", limiting their resolution significantly. It would be beneficial to have the option to have the images display at original resolution.
The way that the actual inputs are hidden in the tag cloud makes them inaccessible to screen readers. They should be hidden in a better way that doesn't remove them from screen readers, and also that appropriately highlights focus on them.
Should just be able to re-use method from Neatline, requested by faculty.
In cases where Items do not have associated Files, could we adjust the display such that Item Relations and Tags appear in the right-hand column, next to the Dublin Core/Item Type fields? Perhaps the related Collections list as well?
An example of an Item that would benefit from such a rearrangement: http://dighist.fas.harvard.edu/projects/crimeaproject/items/show/182
Investigate possibilities for displaying different metadata elements instead of "Description" for different item types. Try to find a simple way to allow control over this.
This issue is branched off from a conversation here
It would be great if there were an easy way to browse by multiple tags simultaneously. It's supported in that you can construct multi-tag urls for browse pages that work, but there's no front end for it right now.
A request was made for changing the default browse order for collections, may as well try to apply it to items, exhibits, and neatline as well.
Which page is active in footer nav is currently only indicated with color, which isn't an accessible way to work. Add an underline.
Request was made specifically for exhibit pages, ensure consistency across browse pages. Descriptions should be in line with preview images on browse pages for items, collections, exhibits, and neatline.
Feature request: browsing by tag across different content types, so that if exhibits, collections and items share a tag, they can be viewed on the same page, similar to how featured exhibits, collections and items are displayed on index.php
The default timeline bar is not centered and/or does not extend evenly across the bottom of the map.
See here for example. What can we do to make this more aesthetically pleasing?
Particular need for collection displays, which use the browse items page, but generally applicable. Add a display, possibly toggleable, on the browse items page for Item Type. Maybe make it clickable as a filter, if that's easy.
This issue is branched off of a conversation here
When browsing items by collection, the links in the Browse Options are not restricted to the collection, as a user would expect. It would be better if these links were limited by Collection when coming from a page that browses items by collection.
Is there a way to order exhibits and collections, much as we can order Items within a Collection?
(I know we talked about this - just documenting that conversation here!)
Provide images sized appropriately for retina displays
To get to a fullsize image from an exhibit requires four clicks, none of which are obvious. Should be able to get to fullsize image more easily.
It's because the description div is set to display:inline, but changing that messes up most other things on the page.
I just populated a Collection with 39 Items. When I go to the collection page only 10 Items display on the screen. If you didn't know any better you would have no idea there are 29 more Items to view. There might be a more elegant solution than a scrollable list, but such a thing would do (see for example: http://gothicpast.com/items/browse?collection=2).
Neatline Narratives should be visible within fullscreen display. Ideally they should also be minimizable and aesthetically pleasing.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.