You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Github's CSV viewer allows for searching the table, so it could create an interesting mechanism to filter the list of codes.
The choice of columns is open for discussion, but once declared, each new contribution would need to include an addition to the CSV table for their tool.
I'm not sure whether the CSV viewer renders URLs that might link to the repo/source.
The text was updated successfully, but these errors were encountered:
Having the data stored in some structured format is a great idea. Another option might be to put it in json or yaml and then render it using the static site generator capabilities of GH Pages, which I think uses Jekyll? . This can loop over the data and make a few different views/filters, etc. That said, I haven't seen the csv viewer yet, so maybe that's better.
CSV viewer is the 60-75% solution - requires 0 development effort but only 60-75% of what may be desired. Jekyll can read CSV, so it may be a good upgrade path, as well.
Github's CSV viewer allows for searching the table, so it could create an interesting mechanism to filter the list of codes.
The choice of columns is open for discussion, but once declared, each new contribution would need to include an addition to the CSV table for their tool.
I'm not sure whether the CSV viewer renders URLs that might link to the repo/source.
The text was updated successfully, but these errors were encountered: