Skip to main content
  • Home
  • Ideas
  • Convert Product Updates into Articles

I love the bidirectional conversion capabilities Insided offers for most topic types. However, this one is missing. 

You can convert articles into Product Updates (and questions/conversations through multiple steps like outlined here), but you cannot go in reverse with Product Updates to articles or other content types. 

Use Case: New features or programs announced via Product Updates that should eventually be moved into standard Knowledge Base or Community articles. 

For example, I will use a product update blog to announce new gamification features (new badges or ways to earn points). The Product Updates module is where we publish our latest news and updates, including community. 

After awhile, those updates get buried in the Updates feed and are no longer “news” or “updates,” but a standard part of the Community experience. As such, it’d be ideal to convert them to an article and move them to the category that hosts all our other community documentation. 

Sure, cross-linking, republishing, and quoting text are all possibilities, but they 1.) take time, 2.) clutter search and the overall user experience.

New→Open

Hi @DannyPancratz! Indeed, this is a functionality gap we want to address. Thanks for submitting it as an idea! 

This is a very helpful feature - following! 

Jumping on to bump this thread as I’m currently going through the arduous process of “moving” a product update. 

Our community is moving from inception to establishment. We need to start reorganizing the content across the community accordingly as we scale out content, categories and groups to meet evolving member and business needs. I expect this will keep happening as we continue to grow. 

To “move” posts out of the Product Updates section I need to: 

  • Create a category that’s not visible to end users.
  • Create copies of the product update content that I want to move by individually copying the text, titles, graphics thumbnails and embeds across. 
  • Publish the posts and then let them “age” in that private category. If I don’t do this, then the main feed gets filled up with all my duplicate posts. 
  • Once they’re a day or so old, move the new articles to the new group or category. 

Because these are copied posts, the original conversations and super valuable member feedback doesn’t make it across to the new section. 

Because the feed get’s clogged up if you copy it all at once. It’s a multi-day, multi-step process. It should be instant much like every other type of content in the community.  

I really loved Insided/Digital Hub. Especially because of how incredibly supportive the team is. But we have to have the ability to move all forms of content around freely with replies conserved to use it effectively long term. 

 

Bump!
We just accidentally converted an article into a product update and there’s no way to change it back.

Some articles have been created in the Product Update section in error. This is a feature that we aren’t using but isn’t hidden from view. Please enable this content type to be changed. Or, grey out the product update function if it’s not intended for use and others don’t accidentally create content there. Thanks

Bumping this idea another year later. We had one of our product managers create 20+ “product updates” that aren’t product updates. We need to move them to articles, and it’s going to be a tedious process.

Since the ability already exist to convert an article to a product update, it seems strange it’s difficult to go the other direction.

 

cc: @woodlande @sarahmasterton-brown @Daniele Cmty @BenSmokeBall @AllisonP @Cristina @jmobley @Gainsight2022 @wheelern 

Terms & ConditionsCookie settings