Codeberg/Documentation
43
151
Fork
You've already forked Documentation
128

Make highlighting of screenshots nicer #52

Closed
opened 2020年09月01日 10:39:04 +02:00 by lhinderberger · 14 comments
Contributor
Copy link

@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.
Author
Contributor
Copy link

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.

My opinion: Zoom-and-blur looks really nice, but (correct me if I'm wrong :wink:) 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.
Contributor
Copy link

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.

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](https://guides.github.com/features/pages/).
Author
Contributor
Copy link

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.

I like it! :thumbsup: It also makes it better readable, especially on mobile. <sub>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.</sub>
Author
Contributor
Copy link

Then again, for highlighting and explaining multiple elements on a screen (like in Orienting yourself on Codeberg), how would that approach work?

Then again, for highlighting and explaining multiple elements on a screen (like in [Orienting yourself on Codeberg](https://docs.codeberg.org/getting-started/first-steps/)), how would that approach work?
Contributor
Copy link

It would depend on the context, but when multiple elements are highlighted it is fine to have a full screenshot.

It would depend on the context, but when multiple elements are highlighted it is fine to have a full screenshot.
Author
Contributor
Copy link

In that case, would we fall back to the red circles and numbers as well?

In that case, would we fall back to the red circles and numbers as well?
Contributor
Copy link

Yes. Though we should use rounded rectangles instead of circles there since it more accurately represents the button there.

Yes. Though we should use rounded rectangles instead of circles there since it more accurately represents the button there.
Contributor
Copy link
Here's a guide that I think is worth following: https://medium.com/technical-writing-is-easy/screenshots-in-documentation-27b45342aad8
Contributor
Copy link

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.

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.
Author
Contributor
Copy link

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.

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.
Author
Contributor
Copy link

As for the first picture of First Steps: True that. Feel free to remove it, if you want :)

As for the first picture of First Steps: True that. Feel free to remove it, if you want :)
Author
Contributor
Copy link

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?

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?
Contributor
Copy link

Let's keep it to future screenshots. We might want to update them once Gitea 1.13 is released :)

Let's keep it to future screenshots. We might want to update them once Gitea 1.13 is released :)
Author
Contributor
Copy link

True 😉 Okay, then I'm closing this issue here.

True :wink: Okay, then I'm closing this issue here.
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/lycheeverse-lychee-0.x
git-pages
pr-554
pr/554
gitea-icons-shortcode
No results found.
Labels
Clear labels
Codeberg Pages

Issues affecting Codeberg Pages
Documentation Usability

Issues related to using and reading docs.codeberg.org
Forgejo
Good First Issue! 👋
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Question
Kind: Security
Licensing
Part: Generator

This is related to the generation of the documentation, not to the content itself
Priority: High

The priority is high
Priority: Low

The priority is low
Priority: Medium

The priority is medium
Reviewed: Confirmed

Something has been confirmed
Reviewed: Duplicate

Something exists already
Reviewed: Invalid

Something was marked as invalid
Reviewed: Wontfix

Something won't be fixed
Status: Blocked
Status: Help wanted

Contributions are welcome!
Status: In progress

Work is in progress
Status: Needs feedback

Feedback is needed
Status: Ready for Review

Work is completed
Status: Review

Review is in progress / Reviewers wanted
Status: Stale
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Documentation#52
Reference in a new issue
Codeberg/Documentation
No description provided.
Delete branch "%!s()"

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?