It's fantastic to have branched out in terms of viral coverage, but having separate "master" branches for flu, Ebola and MERS is not sustainable for development. Too crazy trying to cherry-pick new additions between branches. We should get everything back master. In this case, rather than flu.nextstrain.org, ebola.nextstrain.org, etc... we should have nextstrain.org/flu/, nextstrain.org/ebola/, etc... sharing JS files, etc... where possible. In this case, I'm not sure if we want nextstrain.org/flu/H3N2/ or nextstrain.org/H3N2/, but this is a minor issue.
I think the first thing to do here to make this possible is to try to abstract some of the branch-specific Javascript in preparation for a merge.
It's fantastic to have branched out in terms of viral coverage, but having separate "master" branches for flu, Ebola and MERS is not sustainable for development. Too crazy trying to cherry-pick new additions between branches. We should get everything back
master
. In this case, rather thanflu.nextstrain.org
,ebola.nextstrain.org
, etc... we should havenextstrain.org/flu/
,nextstrain.org/ebola/
, etc... sharing JS files, etc... where possible. In this case, I'm not sure if we wantnextstrain.org/flu/H3N2/
ornextstrain.org/H3N2/
, but this is a minor issue.I think the first thing to do here to make this possible is to try to abstract some of the branch-specific Javascript in preparation for a merge.