Web integration

Draw the path from source data to the page a visitor sees. Decide which work happens during publishing, which happens in the browser, and which requires a protected application environment. This choice affects freshness, credential handling, failure behavior, and the experience during a slow request.

The website API integration guide develops visible loading, success, empty, and error states. Keep the displayed result tied to the latest relevant request, and avoid assuming every record has the same optional fields or a usable image.

For a content-driven example, read the WordPress integration workflow. Test the mapping from source fields into the interface as carefully as connectivity. Preserve the previous successful presentation when an update cannot complete, and define how an editor or developer verifies that a later refresh produced the intended page.