Skip to main content

Screenshots – Sparks for Teams Documentation (English)

Status: March 2026

This folder contains all screenshots for the user manual (USER_MANUAL.md). The list is aligned with the concept docs in Vistameet-Teams (e.g. Meeting-Chat “Create on first access”: calendar-context-menu-meeting-chat, meeting-chat-tab).

Language: Deutsch

Screenshots noch zu erstellen / Still to create: SCREENSHOTS_TO_CREATE.md


Available Screenshots

These files live under docs/screenshots/en/ (German screenshots under docs/screenshots/de/):

FileDescriptionUse in Manual
login-screen.pngLogin screen with logoGetting Started – First Launch
keycloak-login-page.pngKeycloak login (after clicking "Sign in")Getting Started – Login Options

Further screenshots are generated by script (npm run screenshots) or added manually.


Screenshots Configured in screenshot-config.json

These screens are generated by scripts/generate-screenshots.js when the Vistameet-Teams app runs at http://localhost:5173 and optionally login credentials are set in .env:

Name (→ filename)URLDescriptionLogin required
login-screen/loginLogin screen with SPARKS logoNo
keycloak-login-page/login + actionsKeycloak login formNo (actions)
main-interface/Main interface with sidebarYes
chat-list/Chat list with roomsYes
calendar-month-view/calendarCalendar month viewYes
calendar-week-view/calendarCalendar week view (after click)Yes
planner-board-view/plannerPlanner board viewYes
teams-list/teamsTeams listYes
calls-page/callsCalls / phone bookYes
contacts-page/contactsContacts / peopleYes
settings-general/settingsGeneral settingsYes
settings-appearance/settingsAppearance settingsYes
settings-security/settingsSecurity settingsYes
settings-accounts/settingsAccounts & Organisations (providers)Yes
settings-privacy/settingsPrivacyYes
ms-chat/ms-chatMicrosoft Teams ChatYes
ms-channels/ms-channelsMicrosoft Teams ChannelsYes
call-log/callsCall log / Call historyYes
activity/activityActivity feedYes
assistant/assistantAI AssistantYes
priority-contacts/settings/priority-contactsPriority contactsYes
blocked-contacts/settings/blocked-contactsBlocked contactsYes
marketing-main-interface … marketing-settings-securityvariousMarketing variantsYes

Note: The screens calendar-context-menu-meeting-chat and meeting-chat-tab are listed in the maintainer checklist in the repo (docs/templates/screenshot-checklist.en.md) and SCREENSHOTS_TO_CREATE.md but not yet in screenshot-config.json; add them there if needed.

Delays: After login and page changes, the script waits automatically (4–7.5 s depending on page) for Calendar, Planner, Contacts, Calls, and MS-Chat to load their data. Too short delays lead to loading spinners or empty screenshots. Details and table: SETUP.md.

After running, files are saved as {name}.png per language in docs/screenshots/en/ and docs/screenshots/de/. Locales are configured in scripts/screenshot-config.json (locales) or via SCREENSHOT_LOCALES=en,de.


User accounts and tenant for screens

ItemDescription
Tenantdev03 – Keycloak realm and tenant of the Vistameet-Teams dev environment (authority e.g. https://keycloak.vistameet.eu/realms/dev03). The app loads this config at startup; for screenshots the app must run with this tenant (e.g. locally with Vistameet-Teams .env). Screenshot auth uses SSO (advanced → “Sign in with SSO”) and screenshot-config.jsonlogin.keycloak.tenant.
User 1Credentials from E2E_USER1 / E2E_PASSWORD1 (e.g. Keycloak username test). Used for all screens that require login.
User 2Optional: E2E_USER2 / E2E_PASSWORD2 (e.g. test2) – for screens with a second user or E2E demo; the screenshot script uses only User 1 by default.

Put credentials in Vista-Teams-Docs/.env or Vistameet-Teams/.env. See SETUP.md → “User-Accounts und Tenant für Screenshots”.


Planned Subfolders (optional)

Screenshots can be grouped by feature:

FolderContent
getting-started/Login, initialization, interface
chat/Chat, messages, search
calendar/Calendar, events
planner/Planner, tasks
teams/Teams, channels
calls/Calls, meeting room
contacts/Contacts, priority contacts, blocked contacts
settings/Settings pages
security/Encryption, devices
troubleshooting/Error messages, help

Currently all screens are in screenshots/. If using subfolders, update paths in USER_MANUAL.md (e.g. screenshots/getting-started/login-screen.png).


Screenshots from Main Project (E2E Demo)

In the Vistameet-Teams repository, Playwright tests under tests/e2e/demo/ generate additional screenshots (meeting room with multiple participants):

  • tests/e2e/demo/screenshots/3-participants-grid.png
  • tests/e2e/demo/screenshots/3-participants-speaker.png
  • tests/e2e/demo/screenshots/10-participants-grid.png
  • tests/e2e/demo/screenshots/10-participants-grid-scrolled.png
  • tests/e2e/demo/screenshots/10-participants-speaker.png
  • tests/e2e/demo/screenshots/10-participants-controls.png

These files remain in the Vistameet-Teams project. For documentation they can be copied to Vista-Teams-Docs/docs/screenshots/ (e.g. in calls/ or meetings/) and referenced in the manual.


Planned extension: Google as provider (Vistameet-Teams)

When Google is integrated as calendar, todo, or contacts provider in Vistameet-Teams (see docs/PLAN_GOOGLE_KALENDER_TODO_KONTAKTE_DATEIEN.md), additional screenshots may be useful:

Screenshot (optional)Description
settings-accounts-google.pngSettings → Accounts & Organisations with connected Google account
Calendar/Planner/Contacts with Google badgeViews with Google as active provider (badge “Google” on events/tasks/contacts)

These are not yet in screenshot-config.json; add them here and in the checklist once the Google integration is implemented in the app.


Naming Conventions

  • Lowercase, hyphens: login-screen.png, calendar-month-view.png
  • Descriptive: create-task-dialog.png, encryption-setup-wizard.png

Image Guidelines

  • Format: PNG for screenshots
  • Size: Max width 1920px (Retina: 3840px)
  • File size: Compress images if necessary
  • Privacy: No visible sensitive data (blur if needed)

Generating Screenshots

# 1. Start Vistameet-Teams (in another terminal)
cd ../Vistameet-Teams
npm run dev

# 2. In Vista-Teams-Docs directory
npm run screenshots

Configuration: scripts/screenshot-config.json (baseUrl, selectors, login).
Full checklist (repository only): docs/templates/screenshot-checklist.en.md