Use Case
I am finding the admin config fussy to edit the larger it gets, especially as the disease and normal cell line configs overlap, might be nice to split them up.
Proposal:
- split config into smaller
.yml files: cell line, disease cell line, gene name, disease, pages, etc
- compose them into the larger config in build/CI step
Option B:
- I think
gatsby-plugin-netlify could compose .ts configs (instead of .yml) which might have less syntax headaches than the raw yml
- downstream easier, but more set up/migration
Acceptance Criteria
Please describe how you know this is done
Details
Please provide any helpful specifications
Use Case
I am finding the admin config fussy to edit the larger it gets, especially as the disease and normal cell line configs overlap, might be nice to split them up.
Proposal:
.ymlfiles: cell line, disease cell line, gene name, disease, pages, etcOption B:
gatsby-plugin-netlifycould compose.tsconfigs (instead of.yml) which might have less syntax headaches than the raw ymlAcceptance Criteria
Please describe how you know this is done
Details
Please provide any helpful specifications