Recruitment architecture

Overview

See also “Integrations.md” for mp-core website settings that affect the JSON-LD output.

Current architecture

Extension configuration (global)

Configured under ‘Admin’ → ‘Settings’ → ‘Extension configuration’ → ‘mpc_vidply’ (ext_conf_template.txt):

These settings apply to every front-end player unless they are overridden in Fluid/TypoScript.

Website settings (per website)

Defined by the mpc/mpc-vidply Website Set (Configuration/Sets/mpc-vidply/settings.definitions.yaml). Editors and integrators can change them under ‘Site Management’ → ‘Websites’ → your website → ‘Settings’ → ‘VidPly Player’ → ‘Accessibility’; integrators can also retrieve them in config/sites/<id>/settings.yaml or as constants in TypoScript.

# config/sites/<id>/settings.yaml
mpcVidply.screenReaderAnnouncements: false
mpcVidply.resumePlayback: true

# available as TypoScript constants
{$mpcVidply.screenReaderAnnouncements}
{$mpcVidply.resumePlayback}

Disabling announcements suppresses the status messages that the player sends to assistive technologies (WCAG 4.1.3). Only do this if something else on the page is already announcing the same status – the player’s own prompts (help dialogue, sign language instructions for dragging and resizing) will continue to be spoken in all cases, as they are the only feedback for the action that triggered them.

Privacy level settings (tx_mpcvidply_privacy_settings)

Site-wide settings for privacy levels of external services:

Available for YouTube, Vimeo and SoundCloud. Supports multilingual content via sys_language_uid. Empty fields use the translations from the language files.

Player settings (tt_content)

Global settings that apply to the entire player instance:

Player options (bitmask)

Default: 8 + 64 + 256 = 328

Notes:

• The customisable size is always enabled (no option to toggle).
• The transcript display is controlled on a per-media-record basis (tx_mpcvidply_media.enable_transcript). The transcript user interface is available if at least one selected item enables it.

Settings for media items (tx_mpcvidply_media)

Settings per item that are specific to each media record:

Best practices

Extension configuration (installation-wide)

Use these for branding and security standards that should not vary from page to page:

• Permitted external media domains
• Default ‘Dark’/‘Light’ theme and page theme synchronisation
• Custom playback icon for privacy overlay and player
• CSS icon mode for integration into the design system

Website settings (per website)

Used for policies that differ between websites within an installation:

• Whether the player reports its status to screen readers
• Whether visitors are offered the option to resume playback by default

Privacy level settings (site-wide)

Use these for settings that should be consistent across all external services:

• Privacy policy text
• Links to policies
• Button labels
• Multilingual translations

Player level (global)

Used for settings that should be consistent across all tracks:

• User interface behaviour (controls, keyboard)
• Initial state (volume, speed)
• Playlist behaviour (automatic playback)

Media level (per item)

Use this option for settings that are specific to the content:

• Source files/URLs and slug
• Metadata (title, artist, descriptions, categories)
• Accessibility features (subtitles, chapters, AD, sign language)
• Visual elements (poster)
• Settings toggles per item (download, floating player, hide speed/help)

Reason

This separation offers:

• Consistency – A uniform user experience regarding data protection across all external services
• Centralisation – Data protection texts are managed in one place
• Multilingualism – Data protection settings can be translated for each language
• Flexibility – Content can be customised for each individual entry
• Maintainability – Clear distinction between site-wide, global and local settings
• Reusability – Media elements work in different contexts

Future considerations

Possible improvements:

• Default labelling per element (for multilingual content)
• Overrides for ‘Loop’ and ‘Mute’ per element (some of the behaviour of playlist tracks is already in place to ensure the visibility of speed and help)
• Template overrides for custom use cases

The current architecture is robust and complies with TYPO3 best practices.