Frontend Links in Purple Hub

purple hub can automatically display the correct frontend urls for your posts in the editor interface, making it easy to see and share the actual public url of your content what you'll see when editing a post, the permalink section in the editor sidebar shows your actual frontend url instead of an internal hub domain before configuration the placeholder https //your website here com/{article slug} after configuration the actual correct link on your website true 330,331 unhandled content type unhandled content type unhandled content type unhandled content type prerequisites to enable correct frontend urls, you need configured web domain your app must have a custom web domain set up in purple manager see docid 5qp36x0omn32fk oye2ey configured url resolver script your (prod released) dynamic resources need a valid url resolver configured see docid es08jigkb6fkm5erizqb published content posts must be either release published to the content cloud, or release scheduled (planned) with a future publication date for scheduled posts, the future contents api must be enabled in purple manager's api configuration page see docid 7mpvvbavxzy94xrutzci how it works purple hub automatically queries the purple supergraph api to get your app's configured web domain from the webconfig look up the post's url path using the url resolver service combine domain + path to show the complete frontend url this happens automatically in the background with no configuration needed in the hub itself benefits easy sharing copy the correct public url directly from the editor easy frontend verification just click the link to see how your updated article looks on the actual website newsletter links newsletters need the correct frontend urls for linked posts see docid\ p9dzxb5v5yffrydgs7fsi