Upgrade grommet experiment

[srallen]

This is an experiment to see what the v1 to v2 Grommet is like. There are more components that could use updating, but I think functionally everything works, except:

• I dropped in the ZooHeader from @zooniverse/react-components and the register link doesn't work. We could update this to not render if the registration function isn't defined.
• The admin toggle for the footer isn't wired up. Is it needed still for this app?
• Some components haven't been swapped for their newer Grommet equivalent, so aren't getting styling right now.
• The app has few specs, so I'm unsure if everything is working:
  • It's unclear to me if the language Select is working as intended. Projects I try on staging don't have languages to choose from and the SO answer isn't really clear on how to use the app (i.e. just add a translator role user to the project). Are there more docs somewhere I missed?

[srallen]

@eatyourgreens I worked on this before the holiday. I have a few questions above which would determine what if anything more needs to happen with this.

[eatyourgreens]

https://pandora.zooniverse.org seems pretty broken, after a very quick look on my phone. I’d be inclined to hold off on any major work until there’s time and resources available for it.

[srallen]

@eatyourgreens this is a sandboxed research / experiment to understand what's involved in grommet major version update so that we know what'll be involved with Zooniverse Classrooms and this (Zoo Classrooms) will be having work done on it.

[srallen]

Answers to my questions would be appreciated because similar approaches will likely be taken with Zoo Classrooms. Thanks!

[srallen]

It'll also allow us to retire the old ZRC, theme, and other packages we don't really want to maintain anymore as a side benefit

[eatyourgreens]

That's a good point. If you want to try out the app, to see how it works, I usually use Galaxy Zoo as a test. The project translations page in the project builder links through to translations in various languages. You'll probably need to enable admin mode in the project builder and in translations in order to see them. I guess that answers the question about admin n mode too.

The language selector should act as an autosuggest, but filtering out options that already exist as translations. From memory, selecting a new language fires the action that creates a new translation in Panoptes.

There's no requirement to use the official Zoo header and footer but they seem like a good idea if they aren't a lot of work to add.

[eatyourgreens]

No need for registration here either. Anyone who's following a link to a translation would almost certainly be logged in already.

Better integration with the project builder might be nice, though. Eg. Sharing the admin mode cookie between the two.

[eatyourgreens]

https://translations.zooniverse.org?env=staging won’t authenticate. I’ll see if I can fix that tomorrow. It might be missing from Doorkeeper.

[eatyourgreens]

I've updated Doorkeeper on staging, so https://translations.zooniverse.org/?env=staging#/ works now if you want to play around with translations for your staging projects.

[eatyourgreens]

Here's a screenshot of the language selector on one of my staging projects. I was right. It should suggest new languages as you type (but filter out existing languages.)

[srallen]

Thanks! I'll hope to have tiny bits of time throughout this month to finish having a look at this and then write up a strategy for updating for Zoo Classrooms.

[eatyourgreens]

Leaving a comment so GitHub stops asking me to read this PR. Initial changes look good. The language selector and responsive layout on phones might be the big issues for this upgrade.

I'm not massively attached to the current selector layout, particularly on phones (#107).