Content creation

Before diving into JSON files, let's talk about what you actually need to create an audio tour. Spoiler: it's probably less than you think.

The essential ingredients

Every audio tour needs three things:

That's it. Everything else—themes, multiple languages, offline mode—is optional polish.

Audio files

Your audio content is the heart of the tour. Here's what works:

Supported formats

Tour data (JSON)

The tour data file tells AudioGuideKit about your tour structure. It's a JSON file containing:

• Tour title and description
• List of stops with their content
• Settings like theme and offline mode

Example structure

{
  "id": "barcelona",
  "language": "en",
  "title": "Barcelona Walking Tour",
  "description": "Discover Gothic Quarter's hidden gems",
  "totalDuration": "45 mins",
  "totalStops": 5,
  "image": "https://images.unsplash.com/photo-barcelona...",
  "stops": [
    {
      "id": "1",
      "type": "audio",
      "title": "Welcome to Barcelona",
      "duration": "3 min audio",
      "image": "https://...",
      "audioFile": "https://..."
    }
  ]
}

We'll cover the complete structure in Creating a Guide.

File organization

Here's how your content files should be organized:

src/data/tour/
├── metadata.json     # Shared settings (theme, offline mode)
├── en.json           # English tour content
├── es.json           # Spanish tour content (optional)
└── de.json           # German tour content (optional)