Gute Ideen sollten geteilt werden

It would be very useful to have the same article appear in different categories.  I'm sure several use cases exist and many (if not most) users would find benefit from this.  I have two simple use cases that we would benefit from but I'm sure that there are more out there.   The first use case that we organize content in two ways - by type of product and media type.  We put all of our videos in one spot but would like to have those videos show up in applicable product categories as well.   The second case is we separate our Knowledge Base by the type of product.  However, some articles would be applicable to more than one product so it would be nice to be able to multi-list it and have it show up in more than one spot.     In the current state, we have to either duplicate articles (and sometimes 3 or 4 times) or we have to choose the most applicable and hope our customers find it.     I did find this in the community and kudoed long ago but went to check on it and it wasn't in ideas so I decided to post it here. ... Mehr anzeigen

URLs of articles posted within a subcategory are currently set up this way: https://hub.suiteengine.com/knowledge-base/homebuilder-getting-started-cfo (i.e.: https://'current-default-domain'/'current-default-slug'/'article-title') This is what we need it to display: https://hub.suiteengine.com/knowledge-base/homebuilder-for-residential-production-builders/getting-started/homebuilder-getting-started-cfo (i.e.: https://'current-default-domain'/'current-default-slug'/'category'/'subcategory'/'article-title') Additionally, when trying to share or link to an entire category or subcategory, the default URL settings only include the main category in the slug, and the 'main content' or subcategory is marked with a pound sign (#). Example of Category: https://hub.suiteengine.com/knowledge-base/homebuilder-for-residential-production-builders#main-content  Example of Subcategory: https://hub.suiteengine.com/knowledge-base/homebuilder-for-residential-production-builders#getting-started What we need (using the same example as the URLs above):  https://hub.suiteengine.com/knowledge-base/homebuilder-for-residential-production-builders/ or https://hub.suiteengine.com/knowledge-base/homebuilder-for-residential-production-builders/getting-started/   Why this is important to us: A general 'best practice' for SEO and UX is to keep the site structure (breadcrumbs) in the URL for improved: navigation and clarity (UX) crawlability and indexing (contextual relevance) (SEO) When embedding URLs into other platforms (in our case, Microsoft Dynamics 365 Business Central), the pound symbol (#) is not recognized as a correct URL structure, so when referencing/linking entire categories or subcategories, it must be a proper slug. We have multiple product lines and channels, which can get confusing for our subscribers and even our own content editors and service teams if the categories and subcategories are not clear. The titles of our articles could be shorter if the categories and subcategories were included in the URL. ... Mehr anzeigen

The Knowledge Base really needs multi-level subcategories to allow better content structuring. Right now, it’s too flat to handle complex/long documentation. Also, having a sticky table of contents (on the left side) in long articles would improve navigation. Without these, the KB is hard to scale and becomes nearly useless for advanced support content. ... Mehr anzeigen

In the previous version of the knowledge base, it was possible to add "custom text links" to the footer of the theme which was very useful for adding the privacy policy, cookie policy, accessibility statement etc.   In the new version of the knowledge base, this is not possible and the links have to be added and spaced out within a single block of rich text. This means that in the mobile version of the knowledge base, the formatting is completely thrown off.   This workaround is unsatisfactory and gives a poor impression of the page when viewing on mobile. It would be great if we could restore the ability to add custom text links on the new knowledge base as well as the other editing features which were available in the old Knowledge Base. ... Mehr anzeigen

Adding another level to the subcategories would help keep information together and make the knowledge base easier to navigate.   Example:   1. Category (shown on help center home page)     a. Subcategory level 1            i. Subcategory level 2               - article 1               - article 2               - article 3 ..... etc.    1. Products      a. Product A            i. Feature A               - articles related to feature A            ii. Feature B                - articles related to feature B      b. Product B..... etc.                   ... Mehr anzeigen

I would like the ability to report on Knowledgebase article creation in the reports section of HubSpot. Right now the Dashboard provides views over time and specific article views, but to see published articles, drafts, or archived articles you have to be in the Knowledgebase inside of Service Hub. I also believe it would be beneficial to have the ability to show the other fields from "Insights" in the reporting dashboard (i.e. total searches, searches with no result, most searched terms). Being able to see the data in a presentable dashboard is important for many reasons, but as organizations scale Knowledgebase reporting is as important as ticket reporting. ... Mehr anzeigen

We currently publish our social media posts to all four channels that are currently available in HubSpot (Facebook, Instagram, X, and LinkedIn).   It would be great to be able to post to TikTok & Pinterest from the same social ads tool.   Are there any plans to implement these additional social channels? ... Mehr anzeigen

You can create a category that only has private articles within it, and create an access group for your staff members, only allowing that access group to see articles within that category.   So, you can effectively build an internal knowledge base inside your external knowledge base.   However, if someone were to not configure an internal article properly, they could display that article on the public knowledge base that is used by your customers.   It would be great if an internal and external knowledge base were included with Service Hub.   Right now, we use a separate platform for internal documentation, and I would love to be able to accomplish this within HubSpot. ... Mehr anzeigen

You should be able to clone Knowledge Base articles like you can blogs and webpages ... Mehr anzeigen