Skip to content

Track Names for DMC27

Status: Draft — seeking team feedback | Last updated: 28 April 2026

Overview

Mountain Camp 2027 will organize sessions into thematic tracks with mountain-inspired names. This document proposes track names for team review and refinement.

Visual inspiration: Dries has used mountain imagery effectively in Drupal presentations (e.g., Drupal 9 Mountain from State of Drupal 2019). We should develop graphic support material for each track.

Proposed Track Names

1. Sovereign AI Base Camp

Topics: Drupal AI, Open Models, data sovereignty, Apertus, Infomaniak, Amazee.ai, OpenClaw, LiipGPT, AI ethics and policy

Target audience: Adjacent builders, Skilled → Expert, policy makers

Why this name: "Base Camp" is where you prepare for the summit — getting the fundamentals right before the climb. Sovereignty + AI is our flagship theme for 2027.

Team feedback: - [ ] Name resonates? - [ ] Topics covered feel right? - [ ] Suggestions?

2. Frontend Ferrata

Topics: React, Next.js, Vue, Nuxt, Drupal Frontend, modern JavaScript frameworks, headless/decoupled architectures

Target audience: Learner → Expert developers

Why this name: Via Ferrata (Italian: "iron path") are protected climbing routes with fixed cables, ladders, and bridges — making challenging peaks accessible. Perfect metaphor for modern frontend development: structured tools that help you reach the summit.

Team feedback: - [ ] Name resonates? - [ ] Topics covered feel right? - [ ] Suggestions?

3. Editorial Summit

Topics: Drupal Canvas, blökkli, Gutenberg, Ghost, content workflows, structured content, content strategy, DAM

Target audience: Learner → Skilled, content managers, site builders, editorial teams

Why this name: The summit is the destination — where content reaches its audience. Editorial work is about reaching the peak of content quality and user experience.

Team feedback: - [ ] Name resonates? - [ ] Topics covered feel right? - [ ] Suggestions?

4. Backend Ascent

Topics: PHP, Drupal Backend, Node.js, Rust, Go, APIs, performance, architecture, migrations

Target audience: Skilled → Expert developers

Why this name: The ascent is the climb itself — technical, demanding, requiring skill and endurance. Backend development is the foundation that makes everything else possible.

Team feedback: - [ ] Name resonates? - [ ] Topics covered feel right? - [ ] Suggestions?

5. Open Col

Topics: Open source sustainability, cross-community collaboration, government tech, open web policy, data sovereignty (policy side), community building, contribution pathways

Target audience: Adjacent builders, all experience levels, policy makers, community leaders

Why this name: A col is a mountain pass connecting two valleys — the route between different communities and ecosystems. Perfect for cross-community topics and open web conversations that bridge different worlds.

Team feedback: - [ ] Name resonates? - [ ] Topics covered feel right? - [ ] Suggestions?

6. First Pitch (Optional — depends on newcomer focus)

Topics: Getting started with Drupal, first contributions, Drupal in a Day graduates, beginner workshops, career paths

Target audience: Learner → Participant transition

Why this name: In climbing, the "first pitch" is the initial section of a multi-pitch climb — where you learn the fundamentals and build confidence. For newcomers entering the Drupal community.

Team feedback: - [ ] Do we need a dedicated beginner track, or should these sessions integrate into other tracks? - [ ] If yes, does "First Pitch" work? - [ ] Alternative names?

Track Count Recommendation

Suggested: 5 tracks (Sovereign AI Base Camp, Frontend Ferrata, Editorial Summit, Backend Ascent, Open Col)

Rationale: - DMC is intimate (100-140 attendees) — too many tracks fragment the audience - 5 tracks allows 2-3 parallel sessions without overwhelming choice - Beginner content can integrate into existing tracks with clear level indicators - Keeps focus on our core themes (AI, sovereignty, community, technical depth)

Team feedback: - [ ] 5 tracks feels right? - [ ] Should we have 4? 6? - [ ] Include "First Pitch" as a 6th track?

Next Steps

  1. Team review (this document) — gather feedback by [DATE TBD]
  2. Finalize track names — decide which 4-6 tracks to use
  3. Design visual assets — create mountain-themed graphics for each track (inspired by Dries' mountain visuals)
  4. Update CFP — add track selection to Pretalx submission form
  5. Communication — announce tracks when CFP opens (July 2026)

Visual Design Notes

Each track should have: - Mountain-themed icon/illustration - Consistent visual style across all tracks - Usable in: website, printed program, signage, social media, slides

Reference examples: - Dries' Drupal 9 Mountain: https://dri.es/files/cache/drupal/drupal-9-mountain-october-2019-1920w.png - State of Drupal 2019: https://dri.es/state-of-drupal-presentation-october-2019

Open Questions

  • Should we have track leads/moderators for each track?
  • Do tracks need distinct colors for program/signage?
  • Should keynotes/featured talks be "above" tracks or assigned to one?
  • Do we want mountain names in German/Swiss dialect (e.g., "Gipfel" instead of "Summit")?

Team: Please add your feedback directly in this document or in the #mountaincamp-claw Slack thread.