Separating data like urls from the code itself by storing it in config files both helps maintainability and allows users to more readily customize the software. For example, is a user is only using R and Data Carpentry then modifying a config would be an easy way to allow them to just get the files they want.
This won't necessarily be doable in all cases since there is some programmatic handling of pages to identify specific urls for download, but it's definitely possible for lessons and basic config file-based customization would definitely be useful to explore.
Great suggestion by @jcohen02 in openjournals/jose-reviews#322 (comment)
Separating data like urls from the code itself by storing it in config files both helps maintainability and allows users to more readily customize the software. For example, is a user is only using R and Data Carpentry then modifying a config would be an easy way to allow them to just get the files they want.
This won't necessarily be doable in all cases since there is some programmatic handling of pages to identify specific urls for download, but it's definitely possible for lessons and basic config file-based customization would definitely be useful to explore.
Great suggestion by @jcohen02 in openjournals/jose-reviews#322 (comment)