IBX-10684: Document translation management

[dabrt]

Question	Answer
JIRA Ticket	IBX-10684
Versions	5.x
Edition

Document translation management in user doc.

Counterpart of ibexa/documentation-developer#3249

PR waits with images and specific procedures for UI changes to the product.

Checklist

• Text renders correctly
• Text has been checked with vale

[github-actions]

Preview of modified files

Preview of modified Markdown:

• docs/content_management/create_edit_content_items.md
• docs/content_management/translate_content.md
• docs/getting_started/dashboard/work_with_dashboard.md
• docs/getting_started/get_started.md
• docs/getting_started/notifications.md
• docs/product_catalog/products.md

[github-actions]

Summary

Status	Count
🔍 Total	13261
🔗 Unique	1320
✅ Successful	511
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	12748
❓ Unknown	0
🚫 Errors	2
⛔ Unsupported	0

Errors per input

Errors in site/content_management/translate_content/index.html

• [ERROR] file:///home/runner/work/documentation-user/documentation-user/repositories/devdoc-5.0/site/multisite/languages/translations_management/index.html (at 2437:52) | File not found. Check if file exists and path is correct
• [ERROR] file:///home/runner/work/documentation-user/documentation-user/repositories/devdoc-5.0/site/multisite/translations_management/configure_translations_management/index.html#configure-translation-providers (at 2454:67) | File not found. Check if file exists and path is correct

Full Github Actions output

[juskora]

I think it misses mention a Workflow status in the Versions tab following:
https://github.com/ibexa/workflow/pull/190

[juskora]

This screenshot also needs an update, the drop-down is different.

[dabrt]

That modal displays a search field when there are more than four services. I'd rather leave the version without the search field to save people from wondering why they can't see it when they have only two providers configured in the system.

This way, when they have more providers, there's a bonus to be happy about.

@julitafalcondusza WDYT?

[julitafalcondusza]

First, a "technical" thing - we don't leave cursors in screenshots (if we do, it's exceptional and with a good reason).
I'll be able to comment on the context of the screenshot once I do a full review of the PR.

[dabrt]

The cursor does not make it to the screenshot. The image in comment is just to show you how the pulldown behaves

[julitafalcondusza]

Got it.
I'd keep the one with search field and add some info about it (appears when at least 4 services configured).

[julitafalcondusza]

plus: quality is really poor
It’s also better to avoid cropping the image in a way that leaves a “darker frame” from the background. It's better if only the white window is visible (even though the drop-down causes that some of the darker background is still visible at the bottom), or to change the crop and show a larger context of the image.

[juskora]

Please mention policies that allow editor user use AI providers also and add info that translations can be in system workflow.

[julitafalcondusza]

Note that this part or review only "touches" the screenshots.

[julitafalcondusza]

Got it.
I'd keep the one with search field and add some info about it (appears when at least 4 services configured).

[julitafalcondusza]

plus: quality is really poor
It’s also better to avoid cropping the image in a way that leaves a “darker frame” from the background. It's better if only the white window is visible (even though the drop-down causes that some of the darker background is still visible at the bottom), or to change the crop and show a larger context of the image.

[julitafalcondusza]

Quality is poor (frame looks much wider)
plus: what about adding step-circles from Snagit here?

[julitafalcondusza]

Why is this view so condensed? The text wraps as if the window had been resized. A wider view would look much better.

[julitafalcondusza]

This looks really bad: the image quality and cropping are off.
Please show wider context, add steps (available in Snagit) and frame.