# Export and published sites

Start from what you are seeing rather than from what you think is broken. Each page below names the symptom, explains why it happens, and says what to do about it.

Several of these are the product working as designed, which is worth knowing before anybody raises a ticket.

---

## At a glance

| **Symptom**                                                       | **Usually because**                                                                                                                                       |
| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| On a published Capable Site the file is replaced by an amber note | Deliberate. The file is read through an authenticated GitHub connection belonging to a person in your tenant, and a published site has no access to that. |

---

## In this section

[On a published Capable Site the file is replaced by an amber noteOn a published Capable Site the file is replaced by an amber note.](https://help.gocapable.com/git/on-a-published-capable-site-the-file-is-replaced-by-an-amber-note.html)

---

## Related

[TroubleshootingEvery symptom.](https://help.gocapable.com/git/troubleshooting.html)

[ReferenceLimits and gaps.](https://help.gocapable.com/git/reference.html)

[How it worksThe behaviour.](https://help.gocapable.com/git/how-it-works.html)

---

_Most of these are expected behaviour._