Host Nextclade dataset reference trees at nextstrain.org/nextclade/*

[victorlin]

from @trvrb in https://github.com/nextstrain/nextstrain.org/issues/1033#issuecomment-2391923991

My desire would be for every nextclade dataset to be represented at /nextclade. Right now I find myself going to clades.nextstrain.org and picking a reference pathogen and example dataset if I want to see the nextclade reference tree for a particular nextclade dataset. I don't know how easy including an automated push to data.nextstrain.org as part of the release process for nextclade datasets would be. Having these pushed to data.nextstrain.org would have the added benefit of easily looking at past versions, eg https://nextstrain.org/nextclade/sars-cov-2@2024-01-01 cc @rneher and @corneliusroemer

Tasks

• [ ] /pathogens: Find a better way to display the SARS-CoV-2 (Nextclade) tile which currently represents all of nextstrain.org/nextclade/*
• [ ] Add nextstrain.org/nextclade/flu
• [ ] Add nextstrain.org/nextclade/mpox
• [ ] TODO: add more Nextclade datasets

[victorlin]

This was discussed with @rneher on a call today. It should be doable after figuring out the process to keep things up to date.

@joverlee521 also mentioned a workaround of using /fetch with a GitHub URL, for example: https://nextstrain.org/fetch/raw.githubusercontent.com/nextstrain/nextclade_data/refs/heads/master/data/nextstrain/sars-cov-2/BA.2.86/tree.json