Update README screenshots

[yp05327]

@lunny @techknowlogick
Wait for the update of https://dl.gitea.com/screenshots
Can you move all old screenshots into https://dl.gitea.com/screenshots/old ?
Then run the action to upload new screenshots to https://dl.gitea.com/screenshots

Follow #33149.
As I mentioned here: #33149 (comment), the prepare process is almost finished.
The backend technical is using newly added workflow_dispatch feature for Gitea Action to take the screenshots automatically.
Then we can easily sync the screenshots to the latest version without annoying manual work.
Get more information from https://gitea.com/gitea/deployment

[silverwind]

Can you show one example screenshot? Just want to verify they are in sufficient resolution etc.

[lunny]

Can you show one example screenshot? Just want to verify they are in sufficient resolution etc.

I believe all the screenshots have been added in https://dl.gitea.com/screenshots/2025/ .

[silverwind]

I see, they look good.

[silverwind]

The new layout in markdown may be quite vertical (I'm not sure because preview is not working yet).

If it is one image per line, consider putting the images aside each other by removing the newlines.

[hiifong]

I think it would be better to control the presentation of the screenshot through the img tag in HTML.

[silverwind]

Up to you whether you do it in markdown or HTML. Benefit with HTML is you can specify width:

<div>
   <img width="200">
   <img width="200">
   <img width="200">
   <img width="200">
</div>

[yp05327]

Up to you whether you do it in markdown or HTML. Benefit with HTML is you can specify width:

Users may have different resolutions, if the width is a const, it may be too small or too big?
Then use css to fix this issue? Then readme may include may html codes?
This is my thought about this.

[silverwind]

Users may have different resolutions, if the width is a const, it may be too small or too big?

Resultion of the thumnails will be greatly sufficient, I'd say put 2-4 per line.

Then use css to fix this issue? Then readme may include may html codes?

Markdown does not allow CSS. Only a limited set of HTML attributes work.

Ideally I'd wrap each screenshot in a link, e.g. <a><img></a>.

[yp05327]

As this is still WIP, we can gather more opinions on it.
IMO, the original image seems large enough, so I don't need to click on it to check the details.
If we put 2-4 per line, sometimes I need to click on it to check the details.

[silverwind]

IMO, the original image seems large enough, so I don't need to click on it to check the details.
If we put 2-4 per line, sometimes I need to click on it to check the details.

README markdown rendering on GitHub and Gitea will in any case render images at most at like 1000 CSS pixels, so the image will always be downscaled to 50% or more, even in full width.

I think having 20+ full-width images will be far too excessive, if only for the scrolling effort needed.

[silverwind]

Can we fix all the links? Currently only one is working.

[yp05327]

Can we fix all the links? Currently only one is working.

The links are all correct. The screenshots are not prepared yet.

See: https://gitea.com/gitea/deployment/actions/runs/29
It seems that the s3 token does not have permission to upload files to screenshots folder.
I could not fix this. So still waiting for the upload

[silverwind]

Hmm yeah looks like IAM rules need an adjustment there, @techknowlogick.

[a1012112796]

status?

[silverwind]

Alternatively commit the screenshots to the repo? I don't think a few MBs will hurt and this will make the screenshots easily updateable by anyone.

[yp05327]

@silverwind @a1012112796
CI is finished:
https://gitea.com/gitea/deployment/actions/runs/32

[silverwind]

Why not commit screenshots to repo? Do we want to make it extra hard to update them?

Also, @lunny should have waited on my review. Please stop merging PRs that have open discussions.

[lunny]

Why not commit screenshots to repo? Do we want to make it extra hard to update them?

Also, @lunny should have waited on my review. Please stop merging PRs that have open discussions.

Sorry, I missed that.

Since the images are not small, it should not be put in this repository. We can update with scripts in deployment repository. I don't think it's too difficult.