Details
-
Task
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
Description
I was attempting to write a program to generate automation agent cluster configuration files, and stumbled through the current reference page, and I think it warrants some general usability improvements:
- sections should be smaller, in general any unuque object/document should have it's own section.
- the use of hyphens to indicate nesting is a bit confusing, and isn't necessarily great for all display situations.
- names of fields should be in monospaced font and cross refrence-able.
- we should call mapping structures documents, just to match global styles. Object is not an incorrect type identifier, but given situations where "everything's an object," it feels confusing.
- it might be time to split the page in to multiple pages.
It may also be useful to have a page that is only a prototypical document, and document fields separately. I also think that because there's a lot of information here, and a lot of potential ways people might want to access it, it might make sense to store the data in some abstract format and then generate several possible outputs. The MongoDB documentation (on the whole) has a lot of reference documentation of JSON-like objects (serverStatus springs to mind) and I think a multi-output solution might be more generally useful.