maybe we can ask Fred?

Hello, I will take this opportunity to summarise the situation about the code.
There are 3 possibles visualisations for the code:

1. The code is displayed in a fix-height block which can be expanded with a button. The code can be edited and ran with Thebe. The explain code feature is also proposed
2. The code is hided by default and can be displayed with a toggle show/hide button. No edit, run or explain code features
3. The code is not displayed at all. It's used for cover. (cover tag)

We still have to determine when the point 2 (hided code) is used (tags ?). For the moment, ti's only used for sound on this article: https://journalofdigitalhistory.org/en/article/6ig87tC5GKjQ

Regarding the ticket request, I put the code first for point 1 and 2 ?

Hello, I will take this opportunity to summarise the situation about the code. There are 3 possibles visualisations for the code:

1. The code is displayed in a fix-height block which can be expanded with a button. The code can be edited and ran with Thebe. The explain code feature is also proposed
2. The code is hided by default and can be displayed with a toggle show/hide button. No edit, run or explain code features
3. The code is not displayed at all. It's used for cover. (cover tag)

We still have to determine when the point 2 (hided code) is used (tags ?). For the moment, ti's only used for sound on this article: https://journalofdigitalhistory.org/en/article/6ig87tC5GKjQ

Regarding the ticket request, I put the code first for point 1 and 2 ?

@biumiamy @danieleguido
I would not be in favour to add extra tag ( as for sure it would an extra work for the editorial team) but it's the problem with image , or if you can determine a bit with a regex ( type Image()) , if not computational figure hide the code

I put the code first for the case 1: https://deploy-preview-678--journalofdigitalhistory.netlify.app/en/article/6ig87tC5GKjQ