It would be fantastic to have a production ready URL before publishing content live. The current preview, includes preview and a few other things that means you can’t reference the URL in other content until pushing the content live. This post provides a workaround, but that is prone to manual error, typos, and a bunch of other issues. Please provide a better way to do this.
Get public URL before publishing
CC Ideation
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
You got my vote!
Mine too! Can't believe this wasn't an idea already tbh.
The problem with that work around is that the publish date is older when you actually move it to the public section. Not pretty imo.
Other (ugly) work around: The preview url gets a redirect to your published article. So you can share the very very long preview url beforehand.
Hi@mbonnell ! Thank you for sharing this suggestion! I am wondering where would the draft link be referenced before publishing? Is your use case around creating a set of draft articles which would link to one another? We could consider a solution around generating the topic URL before publishing, though I’m not entirely sure it is feasible as the URL contains the topic ID which is generated at the time of publishing the content to avoid conflicts with other topic’s ID.
The workaround@Paul_ mentioned that might solve the issue you’re encountering, especially if you use it in a hyperlink so the readers do not see the long preview link. Once the draft is publish, you will not need to update it because it will automatically redirect to the published topic’s URL.
Other marketing and product efforts, for example, email campaigns, marketing websites, in-product links to additional information and content. As a broad example, our general flow for releasing a product change is:
a) beta test as employees
b) ship product change to production
c) ship marketing updated
d) ship community posts/information
b and c will often contain links to the community posts, but we have to re-deploy b and c after the community posts are live due to not having a trusted URL that can be used. We don’t want someone to go from a marketing email or marketing website to an invalid URL, but are forced to take that risk due to a lack of a definitive URL being presented.
Could the topic ID be generated at draft time to avoid the conflict?
I see, the issue is that users will arrive from external sources on a page that will show the 404 error. Even if we would be able to generate the exact URL of a topic before it’s published, users will still not be able to see the content until it is actually published, because the “published” state is what makes a content piece visible to community visitors. I’m afraid your problem would not be addressed, if I understand it correctly.
Please let me know if I’m missing something in defining the problem you’re encountering.
Thanks@Cristina , the URL is still valuable because then we don’t need to do a re-deploy of marketing or production systems with the correct URL. To be super explicit:
1) Without a valid draft URL:
2) With a valid draft URL:
Here’s an example preview link:
When this page goes live, based on other examples, I think the page will be:
Aside from removing /preview/article/Number and the very long string thereafter, the final URL doesn’t look anything like the draft URL.
Here’s an example preview link:
When this page goes live, based on other examples, I think the page will be:
Aside from removing /preview/article/Number and the very long string thereafter, the final URL doesn’t look anything like the draft URL.
I agree. Reserving a short/def. url before publishing would make it a lot easier if other teams need that url for their content. Be it marketing for a newletter or another online team that whants to link to the article. It makes ‘going live’ at the same time easier. The preview url works, but it is long, it says “preview” in it and it is not very SEO friendly to use redirects. I don't think it's designed to use it that way(?).