Feature Request

We have a knowledge base of multiple languages. When we are updating the article slug in the default language, it gets updated only in the default language and a redirect rule is added. However, the articles in the other languages have the same issue. For this, we have to manually update the article slug and add a redirect rule for the same. We would like to know about the possibility of automating this process within the tool.

Currently, the redirection rule is not working if the source path contains #heading. It would be great if support is provided for redirection rule to work even if the source path contains the anchor link.

I would like the ability to redirect Doc360 urls to external ones. Why: We are transitioning from an old help center to this platform and would like to redirect URLs to the old content while we build it out here. The goal being for them to consistently use the same Doc360 URL for their needs but still have access to the old content while its being worked on. Additionally, we have an external pages that we would like links to go to such as our customer portal and status page.

Request redirection rule to include Regular Expressions (Ex: "_" underscore) in the "Source Path" field. Currently an error is displayed on the screen.

Our company uses various working documents where collaboration takes place. Those documents (for various reasons) can't live inside document 360. Our work around is to add a Custom CSS & Java Script that redirects the article to the external document. I would love a feature that allows you to simply redirect to something external. When selecting the three dots next to the article a page of settings appears. This would be a great place to offer the option to redirect the article by inserting a link.

Creating feature request on behalf of one of our customers: External redirects are manual which can only be updated and maintained via custom Javascript that is more of a “trick” on our end than a fix for the underlying issue. Also, when adding a redirect over an existing link, the new redirection should oveeride any existing redirection. Manual search is a tedious process and we would like to get rid off it.

Requesting a setting to map a URL to a specific heading/section within an article. Currently, it only lets you link to an article, not somewhere specifically in the article.

When customer clicks read more the link will open the relevant page in the widget and not in the docs

We now have 7 versions on our project, and it is becoming difficult to manage the site's redirects, as a redirect rule needs to be set up for each version. It would be much simpler if we could set a rule that would apply to all versions (including future versions), as currently every time we add a version we need to recreate all of the redirect rules.

In markdown, one can add a hyperlink through <description> , where link can either be an http/https address, or a relative link. Relative links will resolve to the same domain (e.g. if my article is https:// . document360.io/docs/foo , then links to ./bar link to https:// . document360.io/docs/bar ). Knowing this, here are the 3 key facts which cause us problems: The article URLs on doc360 are flat (ie all are under /docs/article-slug), and duplicate slugs are resolved by appending -2, -3, etc to the end of URL We have multiple categories set up with the same articles per dev environment (master, qa, rc, preview, production) which each want their articles to reference other articles within the same category It is not really possible to resolve the number suffixes dynamically, or at least this is very impractical and causes other issues. The ideal feature would be to have article URLs in doc360 take on a folder structure for categories, i.e. include the category structure in the URLs (or have the option to do this). An alternative feature would be to allow relative links to reference based on the article/category structure instead of the URL structure, though this solution is not as clean.