affiliation in content page headers

[swbioinf]

Hi,

I had a bit of issue with the jeckyl build of the scRNASeq howto workflow with the latest version of the elixar theme (v2.5)
(see mess here: swbioinf/scrnaseq_howto_ga_workflows#3)

In the end this was avoided by taking affiliation out of the pages/content.md file header, in this edit: swbioinf/scrnaseq_howto_ga_workflows@60daf93
I don't know enough about jeckyll or themes to fully understand why that happened though.

If you look at the template, there is a affiliation entry in the pages/example_page.md (https://github.com/AustralianBioCommons/guide-template/blob/main/pages/example_page.md?plain=1).

I'm wondering if that line should be removed from the template?

[supernord]

Hi @swbioinf

Thanks for adding this issue. We are able to use affiliations with ETT v2.4 without issue: https://github.com/AustralianBioCommons/ables/blob/5e20fbef16996254c72016c35533d39463acc356/index.md?plain=1#L59

It might be that the affiliations feature requires type: infrastructure

Could you please try adding type: infrastructure into the https://github.com/swbioinf/scrnaseq_howto_ga_workflows/blob/c6e8df3a29fce1613bc7d08e40a00557b72fb184/_data/affiliations.yml entry for QCIF, and let me know if the same error occurs when affiliations: QCIF is included in the guide markdown?