Create generic template from this repo

[joshmoore]

• load thumbnails as in https://github.com/will-moore/ome-ngff-validator rather than using IDR URLs
• possibly load table data dynamically from the Zarr itself
• create a new template repo under github.com/ome
• strip out IDR specific columns like "View in IDR"
• slightly unrelated:
  • create an action button to solidify copy/open/validate/...

[will-moore]

@joshmoore, @sbesson Thinking about all of these issues, and working with JavaScript, the current jekyll based deployment of this site is really a pain point. I can't deploy it locally (except with missing JavaScript/CSS!) and it's also very hard for others to review PRs etc.

I'm thinking we should just move to a modern JavaScript based repo (similar to ome-ngff-validator) which has a very nice dev setup (hot reloading etc) as well as deploy of PRs etc.

This could be forked as an IDR-free repo, e.g. at https://github.com/ome/ome-ngff-samples/

My biggest question is what JavaScript framework (if any) to go with!?

[will-moore]

Actually, I think using React make sense, then we can use Viv with <DeckGl> for thumbnails etc.

[joshmoore]

https://github.com/ome/ome-zarr-catalog FTW 🙂

[will-moore]

Ahhh - zarr vv ngff issues again!
This would be what you see from https://ngff.openmicroscopy.org/data right?
So why go from ngff to zarr?
I guess the question is what we do when NGFF is OME-HDF and OME-Zarr?
Would we add hdf support to ome-ngff-catalog or would we start a new ome-hdf-catalog?
I don't know the answer to that, so I guess I could go with ome-zarr-catalog...