gameworkersolidarity / website Goto Github PK

The filter selection UI is getting unwieldy due to all the options. We should add a text search / autoselect element (known as a combobox) to make it easier to use.

Examples:

The SolidarityActionCard could do with an og:image tag (etc.) that pulls in the image thumbnail if one is available. Adds a bit of variety to the share cards.

Alternatively we could autogenerate card imagery using the title and other metadata, a bit like how Github does for public repos and issues.

E.g.

Look at https://www.gameworkersolidarity.com/action/2022-04-gamechuck-signs-first-collective-agreement-croatian-gaming-industry

I've been using the Github mobile app and I think they have the right UI model for filtering.

i.e. Replace the generic label with the selected value, when there is one selected value.

(Only use the generic label when there is more than one selected value, with a counter)

I actually enjoy that they treat filters like an OR, not AND, but I think that's tangential to the main point of this issue.

Happy to PR this, just jotting it down in issue form while it's in mind.

• #27
• #28
• #29
• #30
• #31
• Make website pull from "public" entries instead of main view -> #21
• #32
• Install crash/error tracking (Sentry.io) -> #19

Suggest Sentry. npx @sentry/wizard -i nextjs

Relevant support article on the change: https://support.airtable.com/hc/en-us/articles/4852449595671-Changes-to-Airtable-attachments

In an effort to increase attachment security, on November 8th, 2022 Airtable will be incorporating expiring links functionality. That means when you share attachments stored in Airtable via URL with external colleagues the link you provide them will expire after a couple of hours. Read on to learn more about how to prepare for the upcoming changes.

Currently, Airtable attachments include a static URL where the attachment can be publicly accessed via a web browser. These links never expire and could be accessed by anyone who obtains the attachment’s link. This presents a potential security risk for any files that contain sensitive information. For that reason, we are introducing expiring public-accessible attachment links.

I think we're using attachment URLs for action files, which might mean they expire. On the other hand, we're also using next/image, which does some image caching. Do the two cancel each other out, or do we need to figure out a solution?