docs(glossary): update the Glossary articles for Crowdin and Crowdin …#778
docs(glossary): update the Glossary articles for Crowdin and Crowdin …#778rohalskyy wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
This is too aggressive screenshots deletion now :)
For example, this screenshot shows the location of an option in a dropdown menu (highlighted). This type of screenshot should probably be allowed because it's more than just a visual capture of a screen, it points to something.
First, let's agree on a policy for screenshots.
There was a problem hiding this comment.
Yeah, it might look like one, because we had a vast number of screenshots that duplicated what the text already clearly explained.
Regarding this particular one, I deleted it because the step right next to it already says to click the particular icon and lists the options (Upload / Download / Download filtered), so it felt like a repeat.
But sure, if you want to keep this kind of screenshot, I'll bring it back.
In general, I only deleted screenshots that just repeated the text (e.g., buttons, simple dialogs, plain tables) and kept the ones that show something text can't (the new concept dialog, the Editor states, the import column mapping). Where I dropped a "where is it" screenshot, I covered the location in the step text.
I've drafted a screenshot policy based on industry best practices. Still polishing it, will add it to CONTRIBUTING.md so we have it there. Let's agree on that, then I'll recheck the deletions against it.
2 participants
…Enterprise