Current NodeWriter prints out JCR node structure "as is", with all child-nodes being sub-maps. This makes it hard to iterate over child-nodes and to distinguish them from properties.

As discussed here, option #2 and #4 look promising and meet the need.

– update

Only arrays guarantee the order of child-nodes when iterating, so option #4 is our best compromise to start with.

{
  "title": "SUB-MAPPINGS",
  "company": {
    "title": "Our Company"
  },
  "what-we-believe": {
    "title": "What We Believe"
  },
  "careers": {
    "title": "Careers"
  },
  @nodes: ["company", "what-we-believe", "careers"]
}

We will still consider as future improvement/ticket how to give more flexibility there (applying array vs. map serialization selectively).