Skip to content

Conversation

@cjsha
Copy link
Member

@cjsha cjsha commented Sep 2, 2025

  • Only 1 template for all headstages:
    • To help with this, make CSV into JSON
    • This allows adding EIBs and Adapters by simply adding their names to a list in the JSON file. The template will then pull images/content/assets that relate to those EIBs and Adapters. I think is better than making a new template for every EIB/adapter combination which I think is what y'all were trying.
    • This change also means that the "Acquisition System", "Dimensions", etc. table can now be generated by a for loop instead of manually written in template
  • Generate title in template
  • Overall, this template is incomplete. It's proof-of-concept

Fix #12 Fix #34


I know you've been working on the channel-maps-docs, I figured I should suggest these changes sooner than later to see if you like and if it would be something you'd like to merge. Please take a look and see if it makes sense to you and if you think it would benefit your workflow.

- Only 1 template for all headstages:
  - To help with this, make CSV into JSON
- Table can now be generated by for loop instead of manually written in template
- Generate title in template
- Put SKU in subtitle
- Overall, this template is incomplete. It's proof-of-concept
@cjsha
Copy link
Member Author

cjsha commented Sep 2, 2025

Look at the OEPS-6570 page to see how it looks when the EIB/Adapter logic works in the template. That's the headstage in the JSON file that has the EIBs and Adapters lists filled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Simplify templates to reduce amount Simplify template logic to forego unavailable data

1 participant