This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

• create banner with the SWHAP tree
• change title to: The Pisa collection
• Add subtitle: Stories of landmark legacy code
• Beta version note
• Add link from "Archive" menu with "Browse Software Stories (Beta)" to stories.softwareheritage.org

This has been implemented and deployed to production, closing this.

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

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.

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.

In T3489#69769, @moranegg wrote:

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

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

Cool! LGTM

@moranegg , @rdicosmo , after taking your comments into account, below should be the final design of the iframe view for content or directory:

The key examples are computer museum websites: they will want to keep the visitor on their website, for visibility reasons, and we need to cater to their needs.
Typically, we should be able to provide them with an embedded view that looks like this (possibly without the "download" and "save again" buttons)

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.

Do you have an example of a complex usecase to get a better idea of your needs ?

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.

@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.

where is the Permalinks tab? I do not see it in the images

Thanks for all this great work...
A few questions/remarks:

• where is the Permalinks tab? I do not see it in the images
• for the url, what about "/embed/" instead of "/iframe/"? "embed" seems to be the canonical term used to designate this kind of things (see YouTube, etc.)
• instead of "go to the archive", why not "View in the Software Heritage Archive"?
• it's great that the iframe can use the width and height attibutes! How do you plan to handle strange values (e.g.: width=10px height=200%)?

I would go for option 1 but the path breadcrumbs should remain as it enables to ease
the navigation inside the source code tree (especially when an iframe points to a directory).
I propose to put it below the iframe header, it will also be fixed.

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

Yeah SWHIDs are long so they eat a lot of horizontal space.

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

The one thing that is missing is the current SWHID I’m viewing.
Maybe use a SWHID (or a badge) instead of the path in the center of the panel… or as a footer like a reference…
Not sure about this, but we need to know what artifact is identified in the iframe.

I agree, it looks great!

This looks great!

Some progress report on my work of the last days on the subject.

Pointing to an archived copy of the source code repository isn't the same as the archived copy of the repository.
SWH archive url -> well formatted for acceptance

Adding this link to the case study:
https://docs.google.com/document/d/1EZIBvENaY-atx9PvoOKUb9setQTERV2rmLvpMrJd2e0/edit?usp=sharing

Discussion with the WikiDigi WG was captured here in 2018: https://docs.google.com/document/d/1EZIBvENaY-atx9PvoOKUb9setQTERV2rmLvpMrJd2e0/edit?usp=sharing

This is one possibility by adding a qualifier to the source code repository (option 2).
I see that the task title might be leading.

Given Wikidata software properties already contains "source code repository" URLs, shouldn't we work on our side to make sure those URLs resolve to corresponding origin URLs, rather than adding yet another property (very similar to "source code repository") on their side?

https://github.com/fnielsen/scholia

Here is the approved property on Wikidata:
https://www.wikidata.org/wiki/Property:P6138