Staying in our lane

[auniverseaway]

Was discussing how we could parse metadata.json to show on page what metadata values are inherited. This brought up an interesting point:

If you preview a page, but the metadata.json on content.adobe.com is out of date, your hlx.page content will not match what you saw in the editor.

Depending on how AEM handles metadata, the same statement could be made for preview and publish. When you publish a page, does it take into account the published metadata or the metadata you saw on preview? If publish just asks preview for their HTML, then what would be the point of every publishing metadata.json?

As for where DA should pull metadata, I think our answer is simple: content.da.live.

We should not try to simulate what someone may see on preview and publish. This means that if you are in DA, you see the DA metadata.json and not what has been published. It's much easier to reason, "I'm in the editor, I see everything currently being edited." If an author previews something, and there's out of date metadata.json, they simply preview metadata.json have preview accurately reflect what is on content.da.live.

The side benefit is that we do not have to ask customers to open up for any CORs issues that may hit da.live. We own content.da.live, so we control who can see this content.