Programmer’s Reference

Documentation
& scope.

Reviewed October 5, 2026. Each entry links to the relevant project manual, standard, or developer reference. Web-platform guides use WHATWG, W3C, and Mozilla’s MDN documentation. Examples are original teaching examples, with reserved hostnames and demo records.

These guides cover common tasks rather than every API or command. Match documentation to your installed version. Distribution defaults, authentication, ACLs, SELinux, enabled modules, database engines, and application permissions can change behavior. No example is a complete production security design.

Terminal commands run in a shell. SQL runs in the stated database client, psql backslash commands only in psql, and programming examples belong in the stated language environment. Configuration fragments belong in the relevant configuration file. Cloudflare settings are dashboard instructions.

Copy buttons copy examples without running them. Visible caution notices flag data deletion, overwritten output, service interruptions, and other state changes.

Project documentation

• PHP — Project reference

  PHP 8.x. CLI commands go in a terminal; PHP examples go in a .php file. No private application endpoints or secrets are included.

• Python — Project reference

  Python 3.9+ examples unless stated otherwise. Use a virtual environment for project dependencies.

• Bash / Linux — Project reference

  Bash on Linux, with GNU tools. macOS and other Unix systems may use different flags. Replace demo paths before use.

• SQL · MariaDB / MySQL — Project reference

  SQL runs inside a database client; connection and backup commands run in a terminal. Transactions require a transactional engine such as InnoDB. MariaDB and MySQL are separate products. Query examples assume a demo sites table (id, name, enabled) and checks table (id, site_id, result); schema-change examples use separate demo_sites fixtures.

• SQL · PostgreSQL — Project reference

  PostgreSQL SQL and psql commands are separate from terminal commands. Use a disposable demo database and a provisioned demo user. Query examples assume a demo sites table (id, name, enabled) and checks table (id, site_id, result); schema-change examples use separate demo_sites fixtures.

• JavaScript — Project reference

  Modern browser JavaScript. DOM examples require matching HTML elements. Browser and server JavaScript have different APIs.

• TypeScript — Project reference

  TypeScript 5+; satisfies requires 4.9+. Type annotations are erased during compilation and do not validate external data at runtime. Code examples are independent .ts files, checked with strict mode and an ES2020 target.

• HTML — Project reference

  HTML goes in .html files or templates. Escape dynamic values through your template system.

• CSS — Project reference

  CSS goes in a stylesheet or style block. Examples require the corresponding HTML classes.

• Apache — Project reference

  Apache 2.4. AlmaLinux commonly uses httpd; Debian/Ubuntu commonly use apache2. Paths, modules, and service names vary.

• systemd — Project reference

  Linux hosts using systemd. demo-worker.service is an illustrative unit, not a WGS production service.

• Git / GitHub — Project reference

  Git commands run inside a repository. GitHub CLI examples require gh and an already authenticated account. Never commit secrets.

• Cloudflare — Project reference

  Public examples use reserved demo hostnames. DNS and security changes need the correct zone and existing organizational policy. No credentials or private origins are shown.

• WordPress / WP-CLI — Project reference

  WP-CLI must be installed. Run from a demo WordPress directory as its appropriate owner, or supply --path. Verify backups before changing data; never copy live credentials.