Start with focused checks
Run php -l for modified PHP entry points and helpers. Test the behavior you changed: navigation destinations, form failures and success, search results, responsive layouts or template identity. A passing syntax check does not prove that a database write or browser interaction works.
Package complete dependencies
Include the changed page, scripts, styles, manifests and any referenced images or fonts. Preserve directory structure. Do not package database credentials, customer uploads or unrelated private files. Shared files can affect other categories, so review their scope.
Verify after upload
Overwrite the intended files, refresh the page and inspect Network requests. Verify on desktop and mobile. Cache-bust changed assets deliberately rather than disabling caching everywhere. Keep a known-good backup so the update can be rolled back if a shared change causes a regression.
Syntax in practice
A focused learning example. Read the referenced source file for its full application context.
C:/xampp/php/php.exe -l academy.php
C:/xampp/php/php.exe -l academy-material.php
// Browser checks: search, filters, new-tab detail links, mobile navigation.Try it yourself
Prepare a file manifest for a small local change and explain how you would verify it on the demo site.
Work on a development copy, then explain what changed and how you verified it.
Project file map
Find these paths in your local WebsHigher checkout. Source paths are references, not public downloads of application code.
scripts/build-travel-subcategory-layouts.pytests/assets/css/assets/js/