I like this idea! I think that such a content type could help with a better user experience, but I also know that others like @bjoern_schulze pointed out that such a content type would be valuable for SEO. Google can interpret the steps of a how-to guide and surface this information in a rich result on search pages, just like we are doing it with questions and answers. 

While I naturally would feel that this content would rather be produced by the company and not the user, I am all in for opening this option in the frontend as well, so you can have user-generated how-to guides. Currently, you could only create a discussion / conversation, which does not feel like the best category possible for such content.

Thanks @Julian we see that some how-to guides are written by externals, others are written by our employees

Thanks for the idea, @Anitahg and thanks to @Julian for mentioning me, as I have posted a similar idea recently:

In our community, both users (externals) and the team (employees) would benefit from such a content type. If inSided provides us with a content type “How to” (or “Step-by-step tutorial”), but it will be located in Control, then one possible workaround could be to be able to transform discussions into a “How to”. We are doing a similar thing already with articles.

In the long run, I want to provide all users (based on permissions we’re setting) with the ability to publish articles, how-to’s and FAQs.