Revise channel mapping table format and inclusion #46
Description
In the templates, it should be a parameter. They should be included on a page-by-page basis (e.g. neuropixels hs don't have a mapping table).
We can also use the gid property of the embed link to point to the appropriate page.
Once these docs are more robust, we can potentially do away with the google sheets entirely. We do have to keep their purpose which is to map the pinouts in a table format that ppl can download or copy/paste, in a way that is helpful for probeinterface and custom adapter mappings.
@cjsha suggested doing them programatically. Instead of having a table with all the mappings, each headstage, adapter, and EIB gets its own mapping that comprises of two columns that represent the following information:
headstage function/connector pin (for hs)
connector pin/connector pin (for adapter)
connector pin/EIB pin (for EIBs).
These mappings can get "inner-joined".