Tag the three Academy sessions on the new platform
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
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
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.mdandscripts/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 anAcademypill. 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
- 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. - An unrelated synthetic event has no Academy badge unless its own stored data includes it. Metadata tags are never shown as badges.
- Empty events retain the existing empty state. An unknown event remains a safe 404.
- 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
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di DataTalksClub/website
-
bug infra operations P1 testing
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
DataTalksClub/website#329 ·
I maintainer di solito rispondono entro 1 giorno
-
bug content data-migration documentation events operations P1
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
DataTalksClub/website#327 ·
I maintainer di solito rispondono entro 1 giorno
-
bug frontend P0 testing
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
DataTalksClub/website#300 · 7 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
bug data-migration events P0 testing
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
DataTalksClub/website#295 · 6 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Show pending evaluation instead of premature project failure and zero scores (CMP drift)Forse già presa Una pull request collegata a questa issue è aperta o già unita. Apertabug courses frontend P1
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
DataTalksClub/website#525 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di DataTalksClub/website
Issue simili
-
[dbt] exported dataset keys reference physical columnsForse già presa @WilliamKelley l’ha presa oggi. Apertaneeds-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
apache/ossie-converters#251 ·
I maintainer di solito rispondono entro 2 giorni
-
cli difficulty: easy enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
desec-io/desec-stack#1312 ·
I maintainer di solito rispondono entro 14 giorni
-
needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
aws/aws-durable-execution-sdk-python#977 ·
I maintainer di solito rispondono entro 1 giorno
-
needs-triage
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
flashinfer-ai/flashinfer#9803 ·
I maintainer di solito rispondono entro 1 giorno