flathub-infra / frontend Goto Github PK

I think we need to improve the display, if there's no changelog for the latest version. So if description is empty. Not sure if trimming it down will work, having it going the full width for only the release number and a date is a bit weird.

What's the plan for Version history, is that a popup showing all releases with their descriptions or a new page? How mandatory is it? Can it be parked?

Is the endpoint still up to date? It seems like flathub-backend.openshift.gnome.org:8080/ isn't there anymore?

At least I can't get a build, that actually shows something. I also fail to get it working when running the backend in a local docker compose. But there might be something else missing, as docs are very rough.

In all the categories, pagination doesn't seem to work because the router doesn't replace the category with the current one and we ended up with a url like this

https://frontend.bilelmoussaoui.vercel.app/apps/category/[category]?page=3

which doesn't work.

We need to make the navbar nice. It might make sense to use a npm package for this, if we can find one.

Could also be a css package. Centering the searchbar is not perfect with the current approach.

https://flathub.org/ currently also switches to a meatball menu for small devices

It would be nice to correctly tag our apps with schema.org definitions. I think declaring them as SoftwareApplication would be correct. https://schema.org/SoftwareApplication

It seems a bit weird, I would either go for | or a simple -

Focus search after loading, so users can just type away

We need to go over each page and check if the meta tags are set correctly

The new detail page should at least have the infos the old page had. The link to the setup guide is also missing.

We could add more with the changes in #49

Or are there any infos we want to drop?

This might also be a problem with some desktops

The old page had tracking via the gnome matomo. The new site is still missing this.

The people over in the gnome design matrix channel suggested, that the editors game picks are probably an unnecessary burden.

1. Let's merge them with the normal picks
2. It will be hard enough to keep these updated, we should do another set of apps each month I think
3. Let's only list 6 apps and remove the show more button
4. Should also make it easier to find enough nice things

I'm not completely happy with the Editor's Choice Apps naming. I think I thought of something better, but forgot it...

The page at https://flathub.vercel.app/apps almost entirely duplicates the home page. Which is a shame!

We need new categories to expand on this page. I will curate some new lists of more esoteric things. As noted in #171 investment in curatorial tools and processes would help app discovery here and justify browsing.

Detail pages like https://flathub-razzeee.vercel.app/apps/details/org.signal.Signal currently go very wide on wide screen monitors. We probably want to set a max width here like on the other pages.

Currently, @razzeee deployed the website using Vercel, same way we have done a long time ago. it would be nice to auto-deploy it somewhere else using Github Actions, and maybe do the same for release versions in the future.

cc @barthalion any opinions?

https://nextjs.org/docs/advanced-features/custom-error-page

currently we are using the latest updated for all of them

It would be nice to have a little tick animation or similar confirmation after pressing the copy action on the manual install action on the item page. It currently feels a little floaty. For an example of how this can feel nicer see the copy action on github itself whilst copying a URL for a build (which is of course the exact same action):

flathub/flathub#2814 (comment)

we should change the 'show more' copy on the developer apps carousel to make it clearer that it's linking to a developer's catalog page since it won't always 'show more' apps unless the developer has >6 apps.

Next version 12 came out, we can give it a try. Some interesting experimental features appeared in that version, as well as preparations for react 18.

https://nextjs.org/blog/next-12

We still need to port the following pages to the new website

• About
• Badges
• Feeds

See https://socialsharepreview.com/?url=https://flathub-razzeee.vercel.app/

Would be nice, if translations could be added to the new frontend. This would include 2 things:

1. The Website itself can be translated. All text, that is from the Website itself can be translated into different languages.

2. When the AppStream data contains a translation for name, summary description etc. and I user, which has a language that has a translation in the AppStream file, the translation should be displayed instead of the default English one.

Should we implement a sitemap for e.g. using this?

https://www.npmjs.com/package/next-sitemap

We are currently missing side menu that should be visible on the left of collections and categories. On smaller screens (only smartphones) it should be replaced by burger menu. After clicking it appears on left side of the screen,

There are currently some pages, that don't use the centerend layout.

I'm aware of:

• Search
• Categories
• Collections

It might be good to know how many people actually use the manual download copy button.

Especially if we want to see, if we could get rid of that element all together.

Would be fun to have a statistics page.

Some ideas:

• downloads total
• downloads by country (world map)
• downloads daily (plot a graph)

https://stackoverflow.com/questions/62757419/whats-the-difference-between-import-and-use-scss-rules

We should check if the urls are still the same between the old and the new site. And see if we need to add any redirects.

Issue: flathub-infra/linux-store-frontend#263
I don't see it in the details page from the source code.

Today, there is still confusion when users try to install packages that are not available for their architecture. It is usually Chromebook users (arm or aarch64 platform) for packages that are Intel only and all they get is a "package not found" error.

The details page should display:

• architecture the package is available for
• a clear mention that the package might not be available for architecture the user runs (by checking the User-Agent)

Seems like the CI can only use Github actions hosted on the flathub Github organization or the docker one.

Any ideas @barthalion ?

It would be nice to host the current dev build online. This would also need the backend to be running somewhere.

Might also help with testing the tracking setup, as it might fail due to being run on localhost.

In my testing of the vercel site search is too slow, 1.75s currently vs about 120ms on the current site. e.g. a search for news https://flathub.vercel.app/apps/search/news

at the very least we're going to need a spinner for transitions we expect to take more than 500ms. This may be a symptom of not being on production hardware, in which case it can be resolving by #62

We have only the basic readme. It is not helpful at all for people who would potentially like to contribute.

The whole thing needs some CSS refinement to make sure things are looking pretty!

cc @bertob

And some fixes where possible