We have 21 extensions listed on the extensions website--that is awesome!! One thing that I think could make the website even more useful would be to group extensions into different categories for ease of access. For example: QC extensions (sbx_subsample, sbx_dedup); classifiers (sbx_metaphlan2, sbx_kaiju); assemblers/assembly (sbx_spades, sbx_select_contigs); annotation (sbx_eggnog, sbx_gene_clusters); and visualization (sbx_report, sbx_anvio). We could also have a reproducibility or reproducible-research section for the extensions that are used to regenerate/reproduce existing findings (e.g. sbx_mccann2018).
The data structure could be as simple as this addition to main.js:
const sunbeam_extensions = [
{"owner": "sunbeam-labs", "repo": "sbx_report", "category": "visualization"},
...
];
Which then is used to sort/categorize the extensions in the view when the page is generated. Hyperlinks to jump to different sections/back to top could augment the usability of this proposed feature.
We have 21 extensions listed on the extensions website--that is awesome!! One thing that I think could make the website even more useful would be to group extensions into different categories for ease of access. For example: QC extensions (sbx_subsample, sbx_dedup); classifiers (sbx_metaphlan2, sbx_kaiju); assemblers/assembly (sbx_spades, sbx_select_contigs); annotation (sbx_eggnog, sbx_gene_clusters); and visualization (sbx_report, sbx_anvio). We could also have a reproducibility or reproducible-research section for the extensions that are used to regenerate/reproduce existing findings (e.g. sbx_mccann2018).
The data structure could be as simple as this addition to
main.js:Which then is used to sort/categorize the extensions in the view when the page is generated. Hyperlinks to jump to different sections/back to top could augment the usability of this proposed feature.