Serve Academy as a database-owned Django app inside the main website

オープン
#515 コメント 9 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
15/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
django, python
領域
backend, databases

調査の方向性

Start with _docs/architecture/database-only-content.md, _docs/specs/07-security-privacy-operations.md, and the current DataTalksClub/academy source named in the issue; inspect the existing Django routing, homepage and shared footer, and core/source_policy.py. Map the eight listed sitemap URLs, functional resources, and existing signup and confirmation contract before planning the app and database import. Done means all acceptance criteria are met, including exact-head CI, independent desktop/mobile verification, and recorded production evidence.

索引モデルが issue の本文から書いたものです。

説明

content enhancement frontend integration P1

Alexey (t3602u–t3604u): «Так надо сделать новый апп» «Для академии» «Часть основного сайта как отдельный Django app».

Intake e6dd364d-2ec7-4688-8758-26a7917ba832 requires Academy to become a separate Django app inside this repository, live at https://prod.datatalks.club/academy/. Existing alternatives #493 (templates/content snapshot) and #514 (upstream proxy) do not replace this task's database-owned application requirement.

Authority and scope

  • _docs/architecture/database-only-content.md: public runtime reads belong to database rows; source builds and ingestion input stay outside the repository under ~/prod; empty databases have no file/proxy fallback. Migrations contain schema only.
  • _docs/specs/07-security-privacy-operations.md and core/source_policy.py: existing consent and minimized analytics boundary; confirmation tokens must not reach analytics.
  • _docs/ci/change-selective-ci.md and _docs/PROCESS.md: impact planning, independent technical review and product acceptance. The user's explicit PR + green exact-head CI + merge instruction overrides the local no-PR convention.
  • _docs/runbooks/coolify-production-deployments.md: live production follows main through the health-gated rolling follower; legacy AWS deployment does not deploy the live website.

Port the reviewed current DataTalksClub/academy source, with no invented copy. Preserve the eight sitemap destinations /academy/, /academy/agentic-engineering/, /academy/ai-engineering/, /academy/sessions/, /academy/bildungsgutschein/, /academy/faq/, /academy/privacy/, /academy/impressum/, plus source confirmation, session materials, historical redirect, calendars and assets. Preserve design, titles, canonicals, OG metadata, sitemap and Umami subject to the site's consent/privacy boundary. Homepage/footer Academy links resolve locally.

Keep the existing Lambda backend and double opt-in signup/confirmation client contract, including its existing fields and session questionnaire. Do not read, remove, overwrite or export registrant records. Browser verification mocks backend responses; the controlled final production submission may address only one [email protected] test recipient.

Non-goals and protected boundaries

No DNS, CloudFront, old S3 site, static site deployment, real registrant mutation, extra email sends, worker activation, new signup backend, or Academy content redesign. Do not merge competing implementations as part of this change.

Acceptance criteria

  • AC1. academy is an installed, separately routed Django app inside this website. Every current Academy sitemap page and non-sitemap functional resource is served under its existing /academy/ URL from database-owned imported source, with no runtime upstream/file fallback. Unknown resources safely 404 and non-read methods are denied.
  • AC2. Source copy/design, canonical and OG tags, calendars/assets, sitemap contents and main sitemap index remain correct. Homepage and shared footer link locally. Desktop/mobile pages and analytics preference controls are usable; any adaptation preserves source copy.
  • AC3. Waitlist/registration and confirmation clients preserve the existing backend and double opt-in contract. Mocked desktop/mobile signup and confirmation pass without sending email. Confirmation responses are private/no-store and tokens never enter analytics. Existing registrant data remains untouched.
  • AC4. Focused app/homepage tests, migration-drift checks and required verification pass; independent tester and PM reports include inspected desktop/mobile screenshots and valid evidence dispositions. The PR has every check green on its exact head before merge.
  • AC5. Merge and production deployment are recorded. Production readiness identifies the merged source; all Academy URLs return 200 with source content and resources; one controlled live test uses only a [email protected] recipient. Record URL status table, PR, commit, deploy evidence and form result in /home/alexey/tmp/agent-reports/2026-11-15-academy-django-app.md. Do not claim deployment complete from local evidence alone.

Browser and operational scenarios

  1. Anonymous visitors at desktop and mobile widths traverse all eight sitemap pages, sessions/materials, confirmation and the historical redirect; verify headings, styles/assets, navigation and no horizontal overflow.
  2. Mock a successful signup and confirmation using a synthetic token; assert preserved field keys, track/consent/session selections and visible success state. Existing safe validation/error behavior remains source-owned.
  3. Unknown resource and empty database return safe 404; HEAD has an empty body and POST cannot mutate publication.
  4. Analytics remains off without consent; allow/withdraw uses shared preferences, confirmation/material routes never load tracking and query strings/tokens never reach pageview payloads.
  5. Import validates the canonical sitemap before an atomic publish, is idempotent, retains old assets, and touches only Academy publication rows. Production import remains a separate reviewed operational step after schema deployment.

No unimplemented product dependency blocks the code. Production publication and single-recipient form acceptance remain required final operational checks.

主要言語
Python
スター
0
フォーク
0
平均マージ
37分
マージ済み PR(30日)
36

環境構築

  • Dockerfile または Docker Compose ファイルあり
  • プルリクエストのテンプレートなし
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

DataTalksClub/website のほかの issue

DataTalksClub/website の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。