Tag the three Academy sessions on the new platform

Aperta
#510 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
django, python
Ambito
backend, content

Direzione di ricerca

Start with PR #495 and the event model in _docs/specs/05-events-registration-email.md, then review the database-only content and production-ingest runbooks. The work includes a narrowly scoped, safe production update plus independent browser verification and deployment evidence. Done means the three event pages show the approved titles and Academy tag, while preserving existing event data and passing the listed acceptance checks.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement events operations P2

Alexey's Academy fix-list item 23 requires the Academy tag on the three Hireable With AI events only on prod.datatalks.club. Item 8a supplies their approved titles. Source: bots-management a860f84, context/courses/academy/copy-bank/facts.md and sessions.md (15 November update wins over older titles). Do not change old static events.html.

Normative references

  • _docs/specs/05-events-registration-email.md, Event model: database-owned event rows; immutable public IDs; cosmetic slugs; existing schedules/provider links/host relationships.
  • _docs/architecture/database-only-content.md: author ordinary content through Studio or reviewed importers; source input lives outside the repo; no runtime hardcoded records, projections or content data migrations.
  • _docs/runbooks/data-ingest.md and scripts/prod/target/__init__.py: explicit target selection and production write opt-in.
  • _docs/PROCESS.md, _docs/ci/change-selective-ci.md: independent tester and PM acceptance, versioned verification evidence.
  • _docs/runbooks/coolify-production-deployments.md: main PR → green CI → rolling follower → served-SHA/live checks. User expressly requires a PR and exact-head green CI, overriding the local no-PR convention.

Existing capability and scope

PR #495 (96a9f0f8) already preserves and renders display tags on /events and public detail pages. Reuse that capability. Public IDs 449, 450 and 451 are the three target events. Author a narrow, input-driven update for their title and display tags through existing Studio/import mechanisms, or a small reviewed importer if no suitable mechanism exists. Title input must be the approved text below, and display tags must include Academy exactly once. No real content is embedded in runtime code, migrations or committed input files.

Public ID Berlin schedule, unchanged Approved title
449 23 November 2026, 17:00 AI Engineering vs Agentic Engineering for Experienced Developers
450 30 November 2026, 17:00 How I Build Software with Claude Code and Other Coding Agents
451 7 December 2026, 17:00 AI Engineering for Experienced Developers: How to Build Apps on Top of LLMs

Preserve all metadata tags (dtc-type:, season, episode), other display tags, identities/public IDs, descriptions, scheduling, materials/provider links, host relationships and registration behavior. A repeated update is a no-op. Unknown, duplicate or mismatched input is rejected atomically, without partial updates. Existing Studio authorization stays unchanged; an importer must require explicit target/write opt-in and must not expose secrets or protected records in stdout.

Homepage and shared footer Academy/session links already exist (core.tests.test_homepage.AcademyLinkTests). Retain them. Verify their rendered destinations; include a relevant Zoomcamp public page's shared footer in live evidence. No additional navigation redesign is needed for this issue.

Non-goals

No static-host edits, academy.datatalks.club work, redirects, llms.txt, changes to course content, registrant queries/writes/exports, registrations, email sends, worker activation, generic tag-management redesign or source-content snapshots in the repository. An operational content write touches only the three public event rows and the approved title/tag fields.

Acceptance criteria

  • AC1. On https://prod.datatalks.club/events, the cards for public IDs 449, 450 and 451 display their exact approved titles and an Academy pill. Each corresponding detail page shows the same title and tag. No unrelated event receives this tag.
  • AC2. The update preserves stable event IDs and all pre-existing metadata, schedule, provider links, descriptions and hosts; retry produces no duplicate Academy tag. Bad/duplicate/mismatched input fails atomically. Tests prove the allowed field boundary without accessing production registrants or delivering mail.
  • AC3. Content remains database-owned. Any importer uses external reviewed input and explicit production targeting; no runtime fallback/content migration or checked-in real-content source is introduced. No old static events.html changes, registrant access or email sends occur.
  • AC4. Existing homepage and shared footer Academy links still resolve to /academy/ and /academy/sessions/; verify homepage and one relevant Zoomcamp page, without breaking current navigation.
  • AC5. Applicable independent Django/browser verification passes with plan and report provenance. Capture and inspect desktop/mobile event index/detail screenshots using synthetic fixtures. For code changes: PR exact-head CI green before merge; record merged SHA, deployed/served SHA, public live URLs and HTTP results. The public content update is applied and live-checked after the needed capability is deployed. Do not claim live completion from code alone.

Browser scenarios

  1. Anonymous desktop and mobile visitors open /events, locate each target event and see the exact approved title and Academy badge; open the detail and confirm the same title/badge, unchanged start time and provider action.
  2. An unrelated synthetic event has no Academy badge unless its own stored data includes it. Metadata tags are never shown as badges.
  3. Empty events retain the existing empty state. An unknown event remains a safe 404.
  4. Homepage and a relevant Zoomcamp public page retain accessible Academy links through the existing navigation/footer.

Dependencies

Generic tag support is merged in #495. Live production currently displays older titles and no Academy badge, so final acceptance requires an authorized narrow database update plus the deployed capability. If production access is unavailable, report the precise blocked operation and required operator action; do not claim AC1 met.

Lingua principale
Python
Stelle
0
Fork
0
Merge medio
37m
PR unite (30g)
36

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DataTalksClub/website

Tutte le issue di DataTalksClub/website

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.