Skip to content

Content Operations

This page covers day-to-day content management tasks available to curators and admins.

Events

Navigation: Admin console → Events

You can create events directly rather than waiting for them to arrive via ingestion. Events have:

  • Title, description, and category
  • Start and end date/time
  • Location (link to a Place record, or freeform address + coordinates)
  • Status (draft, review, published, postponed, cancelled, outdated, archived)
  • Photos (upload or link to media)

Publishing an event

Events must be in published status to appear in the Kubuli app. Set status to published when the event is confirmed and accurate.

Closing an event

When an event ends, move it out of published. Use outdated for stale listings that should disappear from live surfaces, or archived when you want to retain the record strictly for historical reference.

Places of Interest (POIs)

Navigation: Admin console → Places

Places represent physical locations — venues, landmarks, beaches, restaurants, and businesses. They are reusable across events and the map.

Each place has:

  • Name, category, and description
  • Coordinates (latitude / longitude)
  • Opening hours
  • Place kind (venue, landmark, beach, business, …)
  • Photos

Linking events to places

When creating or editing an event, select an existing Place as the location. This keeps venue data consistent and allows the map to display the event at the correct pin.

Cultural Stories

Navigation: Admin console → Stories

Stories are the text-to-speech cultural content served by the Cultural & History Explorer feature. Each story has:

  • Title and body text (used for TTS)
  • A topic tag (e.g. “Kalinago Heritage”, “Carnival History”)
  • Optional audio URL (previewed when a generated TTS asset already exists)
  • Related place (optional)

Topics

Stories are grouped by topic. Topics are configured separately and appear as filters in the mobile app’s Explorer section.

Media & Photos

Navigation: Admin console → Photos

Photos can be uploaded directly or arrive via ingestion. You can:

  • Upload new photos for any event, place, or story
  • Reorder photos within a gallery
  • Mark a photo as the featured cover image
  • Delete photos that are low quality or inappropriate

Community-submitted photos arrive via the API and appear in the media console for moderation before they are published.

Ingestion source monitoring (admin only)

Navigation: Admin console → Ingestion Sources

Each source record shows operational state such as last scrape time, items ingested, and the most recent error. For n8n-backed sources, use the n8n Executions action to inspect recent runs and Update n8n Workflow to refresh the injected token and source configuration.

Built with VitePress