-
Notifications
You must be signed in to change notification settings - Fork 7
Home
Graham Smith edited this page Apr 1, 2016
·
4 revisions
Here is where we document the pattern library and front-end build of eLife version 2.0. Yes, we have gone back to 2004. Here lies the definitive list of standards used and decisions made for the initial build and continuing maintainability of the project. All will be followed. All will be obeyed.
The project priorities have been defined as follows:
- Access
- Maintainability
- Performance
- Visual Appeal
Any decisions should use this list of priorities when reaching an agreement.
- Devs will write, by default, clean, well structured HTML. (No bloat)
- Given the clean, minimalist style of the new design, issues around unsupported browsers and accessibility will be minor.
- Adding ARAI roles (
role="main"
) to elements with the same semantic meaning (<main>
) does not cause problems. - Site will be served over HTTP/2.
- Site host will have font cross-origin protection.
- Article related links section: Would prefer not to have the space after the title and the list of links. What is the output from the CMS editor? Can the space be negated with through CSS (negative margin or some such)?
- http://projects.jga.me/jquery-builder/
- https://dev.opera.com/articles/responsive-images/
- https://www.filamentgroup.com/lab/font-events.html
- https://github.com/typekit/webfontloader
- fonts.com tracking script needs adding + async loading JS code
Project Management