Leave as is for a first deployment.
We will test on the partners platform and iterate.

This is really good!
I discussed this option with Kat from Data Current (in charge of the SWH stories interface) and she was wondering if the highlighted text will be centered.
Seems from your example that this will be the case.

@anlambert we have discussed this task this morning with @ardumont and @vlorentz.
I want to start working on the improvements of the deposit admin view to open it up for deposit clients.
Would you have time during September to help on this task? (it is a roadmap task, btw)

To discuss with @rdicosmo

@anlambert : Looks very good!
Can you show an example for a code fragment where you view a content with a few lines marked-up ?

Ipol's editor has agreed that this solution will be good for their use case.

At the moment, I think that all the properties you have selected in the task are needed.
+1 for License (it is something they show on the interface even if it is based on a heuristic).

@anlambert; after discussing with @rdicosmo, here are a few context elements:
We are working on different use cases for the iframe, the first is a rather simpler one with the SWH stories, where just having the source code in a minimalist way is best.
In the future we will also need to answer a more complex use-case where the iframe resembles more as an embedded copy of the archive.

That's really nice, but I still prefer the minimalist first iframe :-)

Looks better with the first implementation with "Go to the archive" :-)
With the badge, it seems right and left side aren't balanced.

This looks great!

@sdruskat Good news about the GitHub support.

Thanks for the quick modifications.
Just a few text changes extra comments.

13. after the lines slides, you can imagine how it is a qualifier on a SWHID but you can't see it. Might be useful to open again the permalink box to see.

Thanks @anlambert for this very intuitive guided tour!

Thanks for the modifications!
Glad you found it useful.

Great work!

An example of a metadata icon for the deposit-admin view:
https://thenounproject.com/term/metadata/77940/

the decision is to create a GitLab repository dedicated to writing the FAQ (Ambassadors can do PR or add issues dedicated to the FAQ)

• the repository will contain a faq-website.md file that can be easily exported into html with the correct tags per question
• concerning the devs/users/sys-admins FAQ, they will be directly edited in the docs
• if issues on the FAQ repository will concern devs/users/sys-admins
  • these issues will be tagged and resolved with addition on the docs instance

Thanks @ardumont !
Looks good, I have a few comments for the answers (nothing major).

Waiting for response from eLife about additional metadata files:

• AUTHORS
• LICENSE
• README

In T3351#65594, @anlambert wrote:

I made some quick hacks in swh-web to see if it was easily feasible to have standalone source code view that could be embedded into an iframe, the answer is yes !

This is great to know (and see :-)

eLife will be using Stencila hub urls as origins: https://elife.stencila.io/article-61523/
We can use https://elife.stencila.io/ as provider url
We can use elife.stencila as the domain.

• is the origin checked with the domain when using create-origin?

1. May 2021 update

Are we matching the create-origin with provider_url or domain?

I'll get back to you with info for provider_url and domain.
Can you copy here the Ipol information?

Put link to this page in the user manual guide:
https://docs.softwareheritage.org/devel/swh-deposit/specs/protocol-reference.html#origin-creation-with-the-swhdeposit-create-origin-tag