-
Type: Task
-
Resolution: Done
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Atlas
-
Labels:None
-
2
Hi
I have received the feedback from a customer during a workshop that the documentation on serverless limitations is ambiguous. Customer was for instance under the impression the "coming soon" in the configuration section applied to all rows in there. Since there's no color row alternation like in actions sections he thought it applied to everything and it was a single row.
He also suspected the different layout, wordings are meant to be ambiguous.
He rightfully stated: "but everything on here are limitations? Why split everything up? Why only mention subtitle 3rd paragraph on page "operational limitations and considerations"?"
He suggested we keep it simple and simplify the page to one table, use configurations, actions and operational as splitter rows if need to be grouped; and mark clearly for each row if it's coming soon. This woulld also allow MongoDB to show all these things are possible with dedicated clusters, which would help us in our decision process.
I think he has a point. For you to consider.