Content is not showing on my site
Your item is Published in Acrosite but not visible on your live website. Here is how to find where the gap is — the commit, the deployment, or the build.
Your content shows Published in Acrosite, but you do not see it on your live website. This is almost always a gap between the commit, the deployment trigger, and your host's build — not lost content. This guide finds the gap.
What "Published" means
When an item is Published, Acrosite has committed it to your GitHub repository and triggered your host to rebuild. It does not mean your host has finished building or that the page is live. See What happens when you publish.
Check, in order
- The commit — open Publish Logs and confirm the GitHub commit stage succeeded. Your content should now be a file in your repository.
- The deployment trigger — open Deployment Logs and confirm the trigger was accepted.
- Your host's build — open your hosting provider's dashboard and confirm the build that the trigger started actually finished successfully.
- Your site's templates — make sure your site reads content from the Acrosite-managed paths. See Acrosite-managed content paths.
Common causes
- Your host did not rebuild because no deployment trigger is configured — see Configure a deployment trigger.
- The build failed on your host (check its dashboard, not Acrosite).
- Your templates do not read from
acrosite/content/..., so the new file is committed but not rendered.
Important
Acrosite triggers a deployment and records the response — it does not track build completion. If the trigger was accepted but the page is missing, the issue is on your host's build, which you confirm in your provider's dashboard.
Next steps
Frequently asked questions
No. Published means Acrosite committed the content and triggered your host to rebuild. Whether the page is live depends on your host finishing the build, which you confirm in your provider's dashboard.
Either your host's build failed (check its dashboard) or your site templates do not read from the Acrosite-managed content paths. Confirm both.
You need your host to rebuild. If your host already rebuilds from Git pushes, manual deployment is fine. Otherwise configure a deployment trigger so the rebuild fires after each publish.