HSLG Media

hslg-presentation.php

hslg-presentation.php

Source file: wordpress/hslg-presentation/hslg-presentation.php

Module: wordpress-hslg-presentation

Size: 78 lines

SHA-256: c056a37ac0bcff30b42b595cb2ce32cbfaa77f0c28f78278bdd22ce7ca47c191

Responsibility

Embeds a browser-only demonstration of the shared UI. Never belongs to a native APK.

Declared entry points

  • HSLG_Presentation — source line 12.
  • VERSION — source line 13.
  • OPTION — source line 14.
  • asset — source line 15.
  • defaults — source line 16.
  • settings — source line 19.
  • activate — source line 20.
  • init — source line 26.
  • maybe_upgrade — source line 33.
  • template — source line 40.
  • shortcode — source line 44.
  • menu — source line 48.
  • register — source line 49.
  • sanitize — source line 50.
  • lines — source line 53.
  • admin — source line 54.

Imports and dependencies

  • Line 78: require_once __DIR__ . "/src/AndroidBuild.php";

Behaviour and audit locations

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

Independent WordPress presentation entry

This plugin registers the browser showcase and its page templates. It is a host shell for the shared app's demonstration runtime; it does not own the customer database schema, account endpoints, native SDK bridge or documentation WordPress pages. Install it as its own reviewed ZIP and test on WordPress staging after updating shared screens. Its demo payment and scan results are explanatory simulations, never production evidence.

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.