Documentation Screenshots
Screenshots should prove a real user scenario. Do not use random test data or private information.
Demo Data
Use a stable demo set:
- employees with clear roles: manager, assignee, co-executor, observer;
- tasks in different states: new, in progress, overdue, with a checklist, with files;
- CRM entities without real clients;
- documents with neutral names;
- notifications created specifically for the scenario.
Demo scenes for tasks
The tasks section needs not one universal screenshot, but a set of demo scenes. Each scene shows a concrete working situation in LadVen OS and should be repeatable in every language.
| Scene | What to prepare in LadVen OS | What the docs show |
|---|---|---|
task-new | new task with title, description, deadline, and assignee | correct result assignment |
task-ready-to-work | task with participants, project, client, files, and checklist | full work context before the start |
task-in-progress | task with active timer, comments, and a partly completed checklist | execution and current control |
task-blocked | task with a blocker in comments and deadline risk | how to record obstacles |
task-review | task with final file and acceptance request | handing the result to a manager |
task-rework | task returned to rework with a concrete comment | correct feedback |
task-overdue | overdue task in the list and card | deadline control and management risk |
task-template | template with description, roles, and checklist | standardizing repeatable work |
task-recurring | recurring task with schedule | calendar process without manual reminders |
task-automation | automation rule with condition and action | LadVen OS reaction to a process event |
Use neutral demo task names without real clients. Good examples: "Prepare client launch report", "Check the contract before approval", "Send materials for acceptance", "Weekly overdue task review".
First task screenshot queue
The first queue explains the task lifecycle: creation, execution, control, acceptance, and standardization.
| Screenshot ID | Page | What to capture |
|---|---|---|
tasks.create-task.details-light-desktop | tasks/create-task.md | creation form with open details: deadline, priority, estimate, project, client |
tasks.create-task.participants-light-desktop | tasks/create-task.md | participants block with requester, assignee, co-executors, and observers |
tasks.drawer.progress-light-desktop | tasks/task-drawer.md | card in progress: partial checklist, active discussion, files |
tasks.drawer.review-light-desktop | tasks/task-drawer.md | card in acceptance with final file and review request |
tasks.comments.blocker-light-desktop | tasks/comments.md | blocker comment, participant mention, and expected action |
tasks.list.saved-views-light-desktop | tasks/list-views.md | saved manager slices: overdue, acceptance, no assignee |
tasks.list.people-schedule-light-desktop | tasks/list-views.md | people schedule for department load control |
tasks.time.timer-light-desktop | tasks/time.md | card or list with active time tracking |
tasks.close.rework-light-desktop | tasks/close-task.md | return to rework with a concrete comment |
tasks.automation.template-light-desktop | tasks/templates-automation.md | task template with roles, checklist, and readiness criteria |
tasks.automation.recurring-light-desktop | tasks/templates-automation.md | recurring task with schedule and execution deadline |
tasks.automation.guard-light-desktop | tasks/templates-automation.md | guard check before closing or changing status |
Recommended task capture batches
Capture screenshots in batches with shared demo data. This closes the first user-facing pages faster and reduces the risk of adjacent screenshots showing different versions of the same task.
| Batch | IDs together | Demo scenes | Pages covered first |
|---|---|---|---|
| 1. Basic task cycle | tasks.create-task.light-desktop, tasks.create-task.files-light-desktop, tasks.create-task.checklist-light-desktop, tasks.create-task.details-light-desktop, tasks.create-task.participants-light-desktop, tasks.drawer.view.light-desktop, tasks.drawer.progress-light-desktop, tasks.view.comments-light-desktop, tasks.comments.blocker-light-desktop, tasks.view.checklist-light-desktop, tasks.files.view.light-desktop, tasks.time.timer-light-desktop | task-new, task-ready-to-work, task-in-progress, task-blocked | tasks/create-task.md, tasks/task-drawer.md, tasks/comments.md, tasks/checklist.md, tasks/files.md, tasks/participants.md, tasks/time.md |
| 2. Manager control and work changes | tasks.list.filters-light-desktop, tasks.kanban.light-desktop, tasks.schedule.light-desktop, tasks.list.saved-views-light-desktop, tasks.list.people-schedule-light-desktop, tasks.block.bulk-actions.partial-result, tasks.block.grouping.ordering, tasks.details-context.view.light-desktop, tasks.relations.view.light-desktop, tasks.edit.drawer.default, tasks.activity.light-desktop, tasks.close.review-light-desktop, tasks.close.rework-light-desktop, tasks.block.time.summary, tasks.drawer.review-light-desktop | task-overdue, task-review, task-rework, task-in-progress | tasks/list-views.md, tasks/details-context.md, tasks/relations.md, tasks/edit-task.md, tasks/activity-history.md, tasks/close-task.md, tasks/time.md |
| 3. Standardization, automation, and responsiveness | tasks.surface.automation.hub, tasks.surface.automation.rules, tasks.surface.automation.admin, tasks.automation.template-light-desktop, tasks.automation.recurring-light-desktop, tasks.automation.guard-light-desktop, tasks.drawer.view.light-mobile, tasks.drawer.edit.light-mobile, then localized en, de, zh, es, fr, kk, ky versions for already captured IDs | task-template, task-recurring, task-automation, mobile task-ready-to-work | tasks/templates-automation.md, tasks/task-drawer.md, tasks/edit-task.md, localized task pages |
Start each batch with the Russian light-desktop screenshot as the composition reference. After the frame is approved, mark Russian as ready; keep the other locales planned until the interface is captured in the matching language.
Localized capture order
For tasks/list-views.md, capture localized screenshots in this order:
tasks.list.filters-light-desktop- top panel, quick filters, and working task list.tasks.list.saved-views-light-desktop- saved manager slices.tasks.list.people-schedule-light-desktop- people schedule and department load.tasks.block.bulk-actions.partial-result- partial result of a bulk action.tasks.block.grouping.ordering- grouping, sorting, and list reading order.
Next P0 block for Russian capture after the creation form:
| ID | What must be visible | Why it matters |
|---|---|---|
tasks.kanban.light-desktop | status columns, buildup in In review or In progress, assignees and deadlines on cards | the manager sees a process bottleneck, not just a task list |
tasks.block.bulk-actions.partial-result | how many tasks changed, which did not apply, row-level reasons, and next step | bulk action requires result review, especially with permissions and guard checks |
tasks.surface.automation.rules | condition, action, scope, and consequence preview | a rule must not be enabled blindly; the manager must understand the scale of changes |
tasks.automation.recurring-light-desktop | schedule, assignee, process owner, deadline, and duplicate policy | a recurring task must be a managed process, not calendar noise |
tasks.automation.guard-light-desktop | restricted action, unmet condition, and clear correction | a guard check must explain how the user can bring the task to a correct state |
Rules
- capture the real UI, not a drawn mockup;
- verify key screens in light and dark themes;
- capture mobile breakpoints for mobile-specific scenarios;
- hide tokens, private URLs, real names, phone numbers, emails, and commercial data;
- store screenshots in the localized folder that matches the UI language.
- add a Markdown PNG link only together with
readystatus for the same locale inscreenshot-manifest.json.
Screenshot Localization
Final standard: every published screenshot must exist in every portal language: ru, en, de, zh, es, fr, kk, ky.
Screenshots can be added gradually, but locale coverage must stay visible. If a scenario is captured in at least one language, the remaining languages must be tracked in screenshot-manifest.json with a status:
ready- the file exists and is used;planned- the screenshot is required but has not been captured yet;blocked- the screenshot is temporarily blocked, with the reason innote.
Do not use Russian UI screenshots on other language pages as the final version. They are acceptable only as temporary working material that is not published in a localized article.
If a localized PNG has not been captured yet, do not insert a Russian image-folder reference into translated Markdown. Leave the article without the screenshot, use a localized SVG diagram, or add the scenario to the capture plan.
File Names
static/img/en/tasks/create-task/light-desktop.png
static/img/en/tasks/create-task/light-desktop.png
static/img/de/tasks/create-task/light-desktop.png
What to Record in PRs
Record the documentation page, portal route, UI language, theme, breakpoint, screenshot path, and screenshot-manifest.json status.