@n suggested in #47 to use zoom and blur effects similar to how GitHub does it, instead of red circles.
I think we should agree on a highlighting style and apply this Documentation-site-wide.
@n suggested in #47 to use zoom and blur effects similar to how GitHub does it, instead of red circles.
I think we should agree on a highlighting style and apply this Documentation-site-wide.
My opinion: Zoom-and-blur looks really nice, but (correct me if I'm wrong 😉) it is a bit harder to do than adding simple red circles. Remember that we might have to re-do screenshots as Gitea/Codeberg develops and changes its shape.
So I'm personally torn in between the time-efficient, effective but less visually appealing solution of adding big red circles and the more time-intensive, equally effective (plus maybe drawing attention a bit better?) and visually very nice solution of zoom and blur.
What's the general feeling? Do we lean towards quick-but-plain or beautiful-but-elaborate?
I personally like both approaches, but I'm slightly leaning towards quick-but-plain.
Agreed!
What do you think about just cropping screenshots? It shouldn't be much more effort since we can do it on the fly. See this GitHub guide for examples.
I like it! 👍 It also makes it better readable, especially on mobile.
As a side note: I wonder if there are any handy tools out there that speed up making and highlighting screenshots in a consistent style.
Then again, for highlighting and explaining multiple elements on a screen (like in Orienting yourself on Codeberg), how would that approach work?
It would depend on the context, but when multiple elements are highlighted it is fine to have a full screenshot.
In that case, would we fall back to the red circles and numbers as well?
Yes. Though we should use rounded rectangles instead of circles there since it more accurately represents the button there.
Here's a guide that I think is worth following: https://medium.com/technical-writing-is-easy/screenshots-in-documentation-27b45342aad8
Also, in my opinion, the first picture on the First Steps article is not necessary since there's a big register button at the center of the page.
Yes, the guidelines shown in the article sound very reasonable. 👍
I also like the style the author uses for their numbering.
I'll sum up the results of this discussion in #69 next weekend, and then we could get started re-doing the screenshots in the new style.
As for the first picture of First Steps: True that. Feel free to remove it, if you want :)
Should we open an extra issue for the task of updating previous screenshots to the current guidelines? Should we even do that at all or just apply the guidelines for future screenshots, to save some time?
Let's keep it to future screenshots. We might want to update them once Gitea 1.13 is released :)
True 😉 Okay, then I'm closing this issue here.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?