My template changes are not showing up in production. Where do I look?

Look in these places, in order:

1. Which template is actually being used

   • Confirm the production route/view is pointing at the file you edited.
   • It’s common to have duplicate templates or a different template loaded in prod vs local.

2. Production cache

   • Template/view caching is often the culprit.
   • Clear or restart any cache layers:
     • app/framework cache
     • template cache
     • OPcache / bytecode cache
     • CDN / edge cache if templates are server-rendered into cached pages

3. Deployment issue

   • Verify the updated template file was actually deployed to the production server/container.
   • Check timestamps or hashes on the live machine.

4. Build pipeline

   • If templates are compiled/bundled at build time, make sure the new build was created and deployed.
   • A stale artifact can make it look like the source changed when the deployed output did not.

5. Wrong environment or config

   • Ensure prod is using the same template directory/config as expected.
   • Sometimes a feature flag, theme override, or tenant-specific config swaps in a different template.

6. Browser / edge caching

   • Hard refresh, inspect network headers, and verify responses aren’t cached.
   • If HTML is cached at the CDN or reverse proxy, you may need to purge it.

7. Permissions / file sync

   • If production pulls from mounted volumes or shared storage, the file may not be syncing correctly.
   • Check that the server can read the updated file and that there isn’t a second copy being served.

8. Logs

   • Look for template-loading logs, cache hits, render errors, or deployment logs.
   • These often reveal whether the old template is still being used.

If you tell me what framework/CMS you’re using (e.g., Django, Rails, Laravel, WordPress, Next.js, etc.), I can give you the exact place to check and the cache command to run.