Implementation issue for adding the query parameters to list the last updated extension

[slemeur]

This is the implementation issue to allow listing the 4 latest updated extensions

[cdrage]

Implementation will be added to the website, it will be shown on https://podman-desktop.io/extend the last 4 extensions updated.

[cdrage]

on hold until #301 is merged in order to be able to update the podman desktop website, we need the catalog updated first to query it (since it's in an iframe)

[cdrage]

#301 is merged, but putting on hold since UX/UI changes will be done as well here:

podman-desktop/podman-desktop#10641

So will discuss with UX/UI before implementing (upcoming UX meeting)

[cdrage]

Per the UX call:

I am putting this in the backlog as we need to rework the UI/UX of the /extend page and have further discussions on what we can do to further improve it whether it's the page of a registry site, unsure for now.

cc @rujutashinde @MariaLeonova

[slemeur]

I don't think there is a relationship with the UX discussion of the extend page and its usability.

The ask is to allow listing the last 4 updated extensions by adding query parameters to the URL.

A first step has been done with #301 which allows to list only a certain number of extensions. Now we need another improvement that list the lastest updated extensions.

If I'm not mistaken, this will be used to display a widget on podman desktop dashboard with the latest updated extensions.

cc @Firewall

[cdrage]

I don't think there is a relationship with the UX discussion of the extend page and its usability.

The ask is to allow listing the last 4 updated extensions by adding query parameters to the URL.

A first step has been done with #301 which allows to list only a certain number of extensions. Now we need another improvement that list the lastest updated extensions.

If I'm not mistaken, this will be used to display a widget on podman desktop dashboard with the latest updated extensions.

cc @Firewall

The PR #301 does list the last 4 updated extensions based on query parameter.

I'll need the UX mockup to add the last 4 extensions to the /extend page, unfortunatley bringing that up in the call brought a larger discussion with regards to what to do with that page overall.

Once @MariaLeonova creates the UX design, I can implement it on the page.

As right now implementing it doesn't look good as it's bringing over an iframe onto the page.

[MariaLeonova]

I believe we agreed to have a call to talk about strategy for the extensions work? @nichjones1

[slemeur]

If list the last 4 updated extensions based on query parameter - then the ticket can be closed.
thanks