iiif / iiifc-theme Goto Github PK

The specs used to constrain width/height of certain images using:
{: .h400px}

See example here:
https://preview.iiif.io/api/wireframe/api/presentation/2.1/#basic-types

See:

• https://iiif.io/calendar.json
• https://iiif.io/eventbrite.json

As included on Demos comp here: https://zpl.io/aNxjkj4

The left-padding seems off when I run the latest version of the theme locally on the API site, and the API-table has lost cell borders:

For comparison, here's what it looks like on current preview for API:

Maybe something about the css refactor caused this?
I'm not skilled enough to fully diagnose, but testing iterations locally looks like it was introduced in this commit:
b70f5cf

How should we handle spec layout pages that don't have any headings, and which therefore don't have a use for the TOC sidebar? Make TOC conditional, or just a slightly modified layout?
A few examples:
https://preview.iiif.io/api/wireframe/api/annex/notes/rotation/
https://preview.iiif.io/api/wireframe/api/annex/

As discussed, should either be white or $grey per the design comps:
https://zpl.io/2GjKrrd

In the design doc for the "Get Started" page, I think the cards under the "Implement a Custom Experience" section are meant to be tied to the selected tab: https://zpl.io/29mRB8y

(and document!!)

As discussed on 7/23, instead of tabbed interface, would be useful to have two columns of text

Now that we've settled on the scheme for linking to internal URLs, we can go through and update copy links

I can do this after our meeting on Friday 7/30 if that's okay? It seems like a good time.

I can then transfer the project board over from the repo-level to the org level (see: https://github.com/orgs/IIIF/projects) to better manage which issues imply changes in which repos.

• calendar.json script. Point to iiif.io rather than beta.iiif.io/groups.json
• update theme defaults to point to iiif.io e.g. api_site in https://github.com/IIIF/iiifc-theme/blob/main/_config.yml
• check cookbook manifests have come through: IIIF/website#523
• copy webp proxy to iiif.io: https://github.com/IIIF/iiif-reverse-proxy-app/blob/master/.ebextensions/nginx/conf.d/beta.conf

On the API site, I'm seeing an odd increase in the global line-height, though not sure why that would be happening.

E.g., https://preview.iiif.io/api/wireframe/image/3.0/
(Previous line-height visible here: https://preview.iiif.io/api/spec_layout_revision/api/presentation/3.0/)

after styling is stable:

• clear out any redundant styling
• rely on bulma vars where possible
• remove unused bulma libraries
• split styles into component files for easier maintenance
• minify output file

• Cookbook
• Guides
• Fixtures
• Registry
• Training (much harder, maybe not possible)

Related to #14, I think you said we could include a button on the tab element that would then anchor down to "user" or "implementer" section, but I can't seem to figure out how to invoke the button on a tab via the front-matter.
Can you explain how it works when you have a sec?

Having a default header color of #0073b0 is problematic because it clashes with the blue in the IIIF logo

This is a very low priority at this point, but would be good to understand what would be involved in making a style sheet that made printed versions of the specs a little bit cleaner...
And for what it's worth, this is mostly for the spec layout if that matters, other layouts are even lower priority on this front

Let's defer this until we settle copy/wrap functionality for code blocks per #21

Is there a way to get the integration tests to fail if there is a problem with the YAML? There was the following issue with the index page which meant the main page failed to load the CSS:

IIIF/website@d5363bc

There was the following warning when Jekyll was built but it passed the GitHub actions tasks:

YAML Exception reading /Users/gmr/development/iiif/website/source/index.md: (<unknown>): did not find expected key while parsing a block mapping at line 37 column 7

Related to #12, need to figure out how to bring over the _posts contents from old site.
They refer to a post layout, which we can either globally find/replace, or figure something else out.

Also, potentially could just use a variation of the page layout, modified just enough to include a byline and dateline at the top?

Josh and I started discussing what the back end JSON should be to drive the events page:

https://preview.iiif.io/root/wireframe/news-and-events/

We currently have:

• calendar.json - this is updated once a day and gets the data from the IIIF calendar. It contains the meetings within the next 7 days and also the time and date for the next meeting of each group like 3d or D4H
• eventbrite.json - this is updated when eventbrite is edited. It contains all IIIF eventbrite events so training and annual conferences. Currently this is used on the training site to generate the link at the top to the latest training: https://training.iiif.io/iiif-online-workshop/index.html
• Google Sheets: generated from the Newsletter google form

@mnyrop could you let me know what data you would need for the website and I can look at combining the difference data sources into a single JSON for your use.

In the category of nice to have, not necessary for launch:
Would be great to make a simple feature/functionality that reads from the front-matter and puts a credit line in the footer for the header image used on that page

Follow up question: do branches need to be "paired" post-sprint?
e.g.,

root_url:       'https://preview.iiif.io/root/wireframe/'
api_url:        'https://preview.iiif.io/api/wireframe/api'

In other words, can we override api_url only on preview deploy for the api repo?

Ticket for noting issues and questions about the Guides site.

As discussed, this conflicts with "copy" button.
Josh will discuss with Editors about relative merits of no horizontal scroll, versus utility of copy button.
Also, Marii helpfully points out that prevailing best practice on sites like Github and elsewhere that have copy functionality enabled is to have horizontal scrolling.

It doesn't look like Safari has good webp support:

https://caniuse.com/webp

I'm using macOS Catalina Safari 14.0.1

E.g., we will need to make sure all things that reference API versions as variables are working correctly, like this one:

{{ site.url }}{{ site.baseurl }}/api/presentation/3.{{ site.presentation_api.draft.minor }}/#language-of-property-values

needs to get converted to something like this:
{{ site.api_url }}/presentation/{{site.data.apis.presentation.latest.major}}.{{ site.data.apis.presentation.latest.minor }}/#language-of-property-values

Internal link checker in CI may already cover this, just documenting here to make sure before I forget.

One of the last remaining top-level content things to import is the news and events, but think we need to figure out that landing page first, from this comp: https://zpl.io/2p3ArGl