docs: Add error message reference (#7093)

Author: igorlukanin

docs/docs-new/pages/_meta.js

@@ -29,7 +29,7 @@ module.exports = {
 
   product: {
     type: "page",
-    title: "Docs",
+    title: "Documentation",
   },
 
   reference: {

docs/docs-new/pages/reference/_meta.js

@@ -1,8 +1,9 @@
 module.exports = {
   "configuration": "Configuration",
-  "frontend": "Frontend",
+  "frontend": "JavaScript SDK",
   "rest-api": "REST API",
   "graphql-api": "GraphQL API",
   "sql-api": "SQL API",
-  "cli": "CLI"
+  "cli": "CLI",
+  "errors": "Error Messages"
 }

docs/docs-new/pages/reference/errors.mdx

@@ -0,0 +1,25 @@
+# Error message reference
+
+Working with Cube, you might encounter various error messages in logs and API responses.
+This page lists some of them with some practical advice on mitigation.
+
+## `Can't find join path`
+
+```
+Can't find join path to join 'cube_a', 'cube_b'
+```
+
+Error message above indicates that a query failed because it includes members from cubes
+that can't be joined in order to generate a valid query to the upstream data source.
+
+**Please check that you've defined necessary [joins](/product/data-modeling/reference/joins)
+and that they have [correct directions](/product/data-modeling/fundamentals/working-with-joins#transitive-join-pitfalls).**
+
+Also, please consider using [views](/product/data-modeling/reference/view) since they
+incapsulate join paths and completely remove the possibility of the error in question.
+You might also consider setting [`public: false`](/product/data-modeling/reference/cube#public)
+on your cubes to hide them from end users.
+
+If you’re building a custom data application, you might use the [`meta` endpoint](/reference/rest-api#v1meta)
+of the REST API. It groups cubes into `connectedComponents` to help select those ones
+that can be joined together.