Tour JSON

[christopherchiu]

{
  tourId,
  tourName,
  tourDuration,
  mapImagesList: []
  locations: [{
    name,
    summary,
    spiritualSignificance,
    googleMapsParameter,
    tasks: [{
      icon,
      text
    }]
  }]
}

[mattam]

Should the "spiritualSignificance" be generalized to some sort of general text information block? So you would have an array of the actual history of the location and the spiritual history of the location, and other text data.

generalInfomation: [
  {
     title: "History",
     content: "blah blah"
  },
  {
     title: "Spiritual History",
     content: "blah blah"
  }
]

History

blah blah

Spiritual History

blah blah

[mattam]

The "location" element might also have to be generalized out, because it's going to be a sibling to the "transition" element (in between A->B transitional/walking directions)

So maybe:

tourItems: [
  {
  type: "location",
  title: "Land's end",
  etc etc
  },
  {
  type: "transition",
  title: "Walking directions",
  content: "Here's how you walk there..."
  }
]

[christopherchiu]

Google map parameters: #7

[christopherchiu]

@mattam I think for the first version we won't be doing transitions

[christopherchiu]

@mattam I have mixed thoughts about the generalization. On one hand it makes things more flexible, but on the other, it takes the look and feel away from our hands. E.g. if someone wanted to put tasks at the very top they could, but it might not look and feel great.

[janiceyip]

@mattam @christopherchiu would we assume that every location will have a "history" and a "spiritual history"? Because if that's the case, we should just have both. Otherwise, maybe:

information: [
  { 
  summary: "short blurb", 
  history: "short history",
  spiritualHistory: "short spiritual history"
  }
]

Unless, of course, every place will have a summary but not necessarily a (spiritual) history.