HSLG Media

PresenterOverlays.js

PresenterOverlays.js

Source file: apps/demo-runtime/src/PresenterOverlays.js

Module: app-demo-runtime

Size: 181 lines

SHA-256: 906f7fcf19569b3c85c069ece454d26843f446553dbb1c5001184a0fda02e1de

Responsibility

Runs the same customer UI with explicit fictional responses only inside the WordPress showcase.

Declared entry points

  • reviewSplash — source line 3.
  • closeReviewSplash — source line 4.
  • showReviewSplash — source line 5.
  • walkthroughStories — source line 8.
  • walkthroughLayer — source line 15.
  • walkthroughHTML — source line 16.
  • id — source line 17.
  • isLight — source line 18.
  • beginWalkthrough — source line 29.
  • drawWalkthrough — source line 35.
  • walkthroughAdvance — source line 36.
  • closeWalkthrough — source line 37.
  • dx — source line 39.
  • eventShowcaseLayer — source line 44.
  • closeEventShowcase — source line 45.
  • openEventShowcase — source line 46.
  • drawEventShowcase — source line 51.
  • eventShowcaseBooked — source line 60.
  • socialLayer — source line 66.
  • closeSocialPromotion — source line 67.
  • openSocialPromotion — source line 68.
  • v — source line 69.
  • channels — source line 71.
  • socialShare — source line 82.

Imports and dependencies

No direct import declarations detected in this file.

Behaviour and audit locations

Review control flow and returned values in the named source file; no special integration marker was detected.

Relationship to the system

This page is the file-level source reference, not the architecture rationale. Read the module explanation, the corresponding architecture decision and user guide before changing behaviour. Names and line locations above are extracted from this exact source version; they are reference points, not proof that an external service or a phone feature works.

Change verification

Review the entry points and errors in this file, then run the module’s associated tests, source dependency gate, history gate and documentation coverage check. If the file changes an API response, user interaction, data model, deployment or third-party dependency, revise those human explanations and disaster recovery/licensing when relevant. Do not infer actual native or external API operation from source presence.