Make /slack the canonical destination for Slack links in the Docs

[alexeygrigorev]

User outcome

Every link in rendered source-backed content that sends a reader to the DataTalks.Club Slack
community lands on this site's own /slack page instead of going straight to an external
Slack URL. /slack is the one canonical destination for community-Slack links.

Owner note (recorded at intake): the /slack page itself does not need to show a Slack
join/invite link. That is an explicit non-goal; the missing invite is not a gap.

Normative links

• _docs/specs/02-url-link-seo-compatibility.md § "Route rules that must remain exact"
  (historical hub aliases redirect permanently in one hop, queries preserved; no catch-all
  redirects) and § "Link preservation checks" (rendered-page link resolution).
• _docs/specs/01-platform-architecture.md § "Member signup, profile, Slack, and course
  registration" (the authenticated Slack-access reveal is a different, member-flow surface —
  see Non-goals).
• Issue Repair stale and broken links in rendered documentation #167 (closed, commit 14b7812) established the render-time rewrite layer this issue
  extends.

Current state at main (9603342)

Already canonical today

• /slack is served by content/review_views.py::slack from
  content/review_projection.json (slack record: title, lead, 8 channel chips, one
  troubleshooting CTA) and is primary navigation
  (templates/core/_site_shell_head.html:25,197).
• Route and alias contract is exact and tested
  (content/tests/test_canonical_routes.py::test_slack_route_and_alias_have_exact_method_and_query_contracts):
  GET/HEAD /slack → 200 with canonical https://datatalks.club/slack; POST → 405
  (Allow: GET, HEAD, no-store); GET/HEAD /slack.html?<query> → 301 to
  /slack?<query> preserving the raw query byte-for-byte (website/urls.py:73).
• Render-time hub-alias rewrites to /slack already exist:
  • Docs (content/docs_projection.py _INTERNAL_HUB_PATHS, lines 145-152): /slack.html
    and /slack/guidelines.html, both relative and https://datatalks.club absolute, inside
    Markdown link spans, preserving query and fragment.
  • Course FAQ (content/faq_data.py::render_faq_answer, the
    https?://datatalks.club/slack.html substitution).
  • Article FAQ (content/article_faq.py::_rewrite_legacy_links, same family).

Remaining inventory (checked projections at main)

Verified by scanning Markdown link destinations in content/docs_projection.json and
content/faq_projection.json:

1. Workspace deep links in Docs — the core gap. 32 distinct external Slack URLs for this
   workspace (31 https://app.slack.com/client/T01ATQK62F8/<channel> plus
   https://datatalks-club.slack.com/archives/<channel>), 72 link occurrences across 16 pages,
   concentrated in /docs/general/slack/ (channel directory), course "getting started",
   "resources", and zoomcamp-logistics pages, and community guidelines pages. All still go
   straight to Slack.
2. FAQ workspace links. One app.slack.com/client/T01ATQK62F8/... link and one
   datatalks-club.slack.com/archives/... link, in answers rendered on
   /faq/machine-learning-zoomcamp.html and /faq/llm-zoomcamp.html.
3. Absolute canonical-form links in Docs. 6 pages link
   https://datatalks.club/slack (already the right destination, wrong form: absolute
   same-host instead of root-relative /slack). The Repair stale and broken links in rendered documentation #167 map does not normalize it.

Classification of what is not a community-Slack link and must stay untouched:

• https://slack.com/help/articles/... (2 in Docs, 1 in FAQ): Slack's own product
  documentation, cited as reference, not an entry to our community.
• /docs/general/slack/ and {{ '/general/slack/' | relative_url }} links: Docs-internal
  pages about Slack, already routed correctly by _docs_url.
• Event descriptions: content/event_description_link_policy.py already removes
  app.slack.com (provider action) and forbids join.slack.com (join host) in reviewed event
  descriptions. There are no join.slack.com invite links anywhere in the Docs projection.

Destination contract

• The canonical destination for community-Slack links in rendered source-backed content is
  the root-relative /slack (canonical https://datatalks.club/slack).
• A link is a community-workspace link when its host is datatalks-club.slack.com (any
  path) or its host is app.slack.com and its first path segment is T01ATQK62F8 (this
  workspace's ID). Workspace links rewrite to /slack and drop their query and fragment:
  both address Slack's own UI (/client/..., /archives/...), not anchors on /slack.
• Hub aliases (/slack.html, /slack/guidelines.html, absolute https://datatalks.club/slack)
  continue to rewrite to /slack preserving query and fragment per the existing Repair stale and broken links in rendered documentation #167
  mechanism; absolute https://datatalks.club/slack joins the map so it normalizes to
  root-relative.
• Preserving a ?utm_*/?source= tag on hub-alias rewrites stays safe: /slack has no
  strict query grammar (the view ignores the query string), so the catalogue-query strictness
  addressed in 643ea32 does not apply here.
• Rewrites happen at render time, keeping the checked projections byte-identical — the
  architecture Repair stale and broken links in rendered documentation #167 set and the immutability test enforces
  (content/tests/test_docs_projection.py::test_rendering_keeps_projection_source_and_metadata_immutable).

Scope

1. Extend the render-time link policy in content/docs_projection.py with the
   community-workspace rule above (Docs Markdown link destinations only, not literal text or
   code spans, matching the existing span-scanning approach).
2. Extend content/faq_data.py::render_faq_answer with the same community-workspace rule.
3. Normalize absolute https://datatalks.club/slack link destinations in Docs to /slack.
4. Add the missing legacy alias: GET/HEAD /slack/guidelines.html?<query> → 301
   /slack?<query> in one hop, query preserved, with the same method/cache contract as
   /slack.html (website/urls.py, alongside line 73). This serves inbound legacy links that
   today get a 404, per spec 02's no-unexplained-404 parity rule.
5. Documentation: add one clarifying sentence to _docs/specs/01-platform-architecture.md
   § "Member signup, profile, Slack, and course registration" distinguishing the public
   /slack landing page from the specified authenticated
   /accounts/community/slack/ reveal surface. No change to that member-flow contract.
6. Focused tests: new rewrites (Docs and FAQ), unaffected links byte-for-byte, the new
   redirect's method/query contract, and projection immutability.

Non-goals

• No join/invite link on /slack (owner note above) and no change to the /slack page's
  content, channels list, or design.
• No per-channel anchors on /slack (e.g. /slack#ml-zoomcamp): the page lists channels as
  plain chips today; adding 30+ targets is a separate product decision. Deep links rewrite to
  plain /slack, accepting the loss of channel-specific landing.
• No edits to content/docs_projection.json, content/faq_projection.json, or the upstream
  content source; the immutability tests must stay green.
• No changes to the event-description link policy (already removes these hosts there) or the
  article-FAQ pipeline (zero workspace links in content/article_faq.json today; adding
  untestable rewrite code there is not part of this slice).
• No rewriting of slack.com/help/... product documentation links or any other external host.
• No decision here on the member-flow Slack-access reveal: whether/how
  /accounts/community/slack/ gets built stays with the member-onboarding flow and
  _docs/specs/open-decisions.md (open decision 19). This issue only clarifies the wording.
• No newsletter, Luma, or other hub-link changes (Repair stale and broken links in rendered documentation #167 owns those).

Dependencies

• None open. The render-time rewrite layer (Repair stale and broken links in rendered documentation #167, commit 14b7812) and the source-backed Docs
  renderer (Add source-backed navigation to the Documentation site #176, commit 896799b) are on main.

Acceptance criteria

• Rendered Docs Markdown link destinations matching the community-workspace rule emit
  href="/slack"; no rendered Docs page emits href="https://app.slack.com/client/T01ATQK62F8/…"
  or href="https://datatalks-club.slack.com/…".
• All 16 affected Docs pages and both affected FAQ answers are covered by focused tests
  that assert the rewrite (the FAQ test asserts the rendered answer HTML, not the source).
• Absolute https://datatalks.club/slack link destinations in Docs render as
  root-relative /slack with query and fragment preserved.
• Links to slack.com/help/..., /docs/general/slack/, and every unrelated external link
  remain byte-for-byte unchanged in rendered output.
• GET/HEAD /slack/guidelines.html?x=1 returns 301 to /slack?x=1 preserving the raw
  query; POST returns 405 with Allow: GET, HEAD and Cache-Control: no-store, max-age=0,
  matching the /slack.html contract.
• content/docs_projection.json and content/faq_projection.json are byte-identical
  before and after rendering (existing immutability tests stay green and cover the new rule).
• Link-preservation/compat checks over rendered pages stay green with the rewritten links
  resolved internally against /slack.
• Spec 01 clarification sentence added; the member-flow contract text is otherwise
  unchanged.
• Tester screenshots at desktop and mobile for /docs/general/slack/,
  /docs/courses/ml-zoomcamp/getting-started/, /faq/machine-learning-zoomcamp.html, and
  /slack show the expected pages with working links, not errors or broken layouts.

Browser scenarios

1. Open /docs/general/slack/; every channel entry links to /slack; following one lands on
   /slack (community page with channel chips), not Slack.
2. Open /docs/courses/ml-zoomcamp/getting-started/; the community/asking-questions links
   land on /slack; a slack.com/help/... citation still opens Slack's own article in a new
   context without being redirected.
3. Open /faq/machine-learning-zoomcamp.html; the "How do I get help if I'm stuck?" answer's
   Slack link lands on /slack.
4. Visit /slack/guidelines.html?utm_source=docs; the browser ends at
   /slack?utm_source=docs in one hop showing the community page.
5. Repeat 1-3 at mobile width; content and links remain readable and usable.

[alexeygrigorev]

Grooming Complete

Researched at main (9603342); key findings that shaped the spec:

• Part of the raw ask already shipped: Repair stale and broken links in rendered documentation #167 (commit 14b7812) rewrites /slack.html and /slack/guidelines.html hub aliases to /slack at render time in Docs, and the course-FAQ and article-FAQ pipelines rewrite datatalks.club/slack.html too. /slack.html already 301s with an exact method/query contract.
• The real remaining gap, verified by scanning Markdown link destinations in the checked projections: 32 distinct community-workspace URLs (31 app.slack.com/client/T01ATQK62F8/* deep links plus one datatalks-club.slack.com/archives/*), 72 occurrences across 16 Docs pages, plus 2 in course-FAQ answers, and 6 Docs pages using the absolute https://datatalks.club/slack form.
• Groomed into: a precise destination contract (workspace-link classification by host + workspace ID, query/fragment rules), render-time rewrites in content/docs_projection.py and faq_data.py, a missing /slack/guidelines.html 301 alias, one clarifying spec sentence, and testable criteria plus browser scenarios.
• Explicit non-goals recorded: no invite link on /slack (owner note), no per-channel anchors, projections stay immutable, event-description policy untouched, slack.com/help/* product-doc links stay external, and the member-flow Slack reveal stays with open decision 19.

Labels: removed needs grooming; now enhancement, P1, content, seo. No open dependencies — ready for engineering.

[alexeygrigorev]

Software Engineer Report

Implemented #184 only in a new isolated worktree. Community-workspace Slack destinations in source-backed Docs and course FAQ now render as root-relative /slack. Absolute https://datatalks.club/slack hub links normalize to /slack with query/fragment preserved. GET/HEAD /slack/guidelines.html is a one-hop 301 to /slack with the same method/query/cache contract as /slack.html. Spec 01 adds one sentence distinguishing the public /slack landing page from the authenticated /accounts/community/slack/ reveal. Projections stay immutable. The #167 hub-alias rewrite and #176 source-backed Docs renderer are unchanged.

Base / head / worktree

• Base: 284219c04e0da976c7143458ea805f3288554d4a (origin/main at start)
• Head: 284219c04e0da976c7143458ea805f3288554d4a (uncommitted worktree; no commit)
• Branch: issue-184-slack-canonical-284219c
• Worktree: /home/alexey/git/dtc-website/.tmp/website-184-engineer-284219c
• Source mode: worktree
• Source-tree digest: f48652d67030e9b2e1ed3ce1fafaafa421df274a8140a165adc7e0fe003fe2ef (tree 08215a0c76e60d48586a20a4dc4b74d3e71acfd3, 3067 entries)
• Note: while this worktree was frozen on 284219c, origin/main later moved to 8459a08 (“Finish the homepage lede repin and escape event titles in test markup”). This lane was not rebased onto that commit.

Graph / plan

• Graph digest: 4127118b4467a75b40b8dbadc4050b5b2dc3762b292aca93cd9309a4593bca19
• Policy version: 4
• Plan file SHA-256: 5a04c20498edc607c4c00bb02e95f0b19dcd32856c918aaa5ef9761b963bd8f4
• Plan digest (sha256_json): de823f3c49528f4810c861cdbe35264f0d6df1b6be0023f502c4cfa791087e9d
• Plan path: .tmp/verification/verification-plan.json
• Profile: full because render_impact (basename:urls.py)
• Browser profile: full
• Direct nodes: app.content, surface.documentation, surface.website
• Downstream nodes: django.accounts, django.content, django.core
• Risk flags: deployment_runtime, shared_runtime, test_infrastructure
• Unknown paths: none
• Render impact: yes. Graph-required captures: / and /__verification_missing__ at desktop (1440×900) and mobile (390×844).

Changed files

1. _docs/specs/01-platform-architecture.md — one clarifying sentence on public /slack vs member-flow reveal
2. content/docs_projection.py — workspace-link rewrite + absolute /slack normalization
3. content/faq_data.py — same workspace rule in the FAQ renderer link hook
4. content/tests/test_canonical_routes.py — alias contract + rendered Docs/FAQ coverage
5. content/tests/test_docs_projection.py — rewrite, immutability, 16 pages, 6 absolute links, help citations
6. content/tests/test_faq.py — both workspace FAQ answers + untouched slack.com/help
7. website/urls.py — GET/HEAD /slack/guidelines.html → 301 /slack

Four disposition buckets

rerun

• selector — success. command make verification-plan. evidence 8574b4c92faf81254a257a5e5b137f6c7486c6d4c4e9f246a5a13fac1923c300. expiry 2026-08-25T18:25:12Z.
• evidence_validation — success. make test-ci: 531 passed / 0 failed. evidence a553609e2aac7580dbf1c4053e474da9c574fad18df61d047d046d471b07cc65. expiry 2026-08-25T18:25:30Z.
• quality — success. quality-contract-v1 (terminology, portability, security, lint, format, type, migrations, django-check, deploy-check, test-ci): 531 passed / 0 failed. evidence b8fb63d678f7de6b4cb4c56d0ef23eaf0974adb945fd9fe7f815ac4e45f3a2af. expiry 2026-08-25T18:26:34Z.
• django — failure of the planned full make test (2186 collected). Isolated cause is pre-existing on clean 284219c: content.tests.test_events_timeline.EventDetailDesignSystemTests.test_an_event_without_speakers_or_links_draws_neither_of_them asserts an unescaped Q&A heading while the page emits Q&A; parallel mode then pickle-aborts (TypeError: cannot pickle 'traceback' object). Confirmed on a clean 284219c checkout with no Make /slack the canonical destination for Slack links in the Docs #184 files. Not caused by the Slack rewrite. Later 8459a08 on origin/main is the event-title escape fix; this worktree was not rebased. Focused Make /slack the canonical destination for Slack links in the Docs #184 tests on this head: 46 passed / 0 failed. evidence 46a290d4886039020db0935a13146e20b40595a8013dbb53a1e4c54989d94cdf. expiry 2026-08-25T18:29:08Z.
• playwright — failure / incomplete. make test-playwright collected 202 tests. First failures are pre-existing and unrelated: public.events-hub: duplicate ids kind-tip-0 and homework breadcrumb height 44 > 24. The suite then hung on test_accessibility_visual_evidence[chromium-viewport0-desktop]; the runner was terminated (exit_code -15) and no valid envelope was written (EvidenceError: evidence exit status contradicts its result).
• container — executed separately after the runner aborted: make verification-container pass (schema_version 1, revision 284219c04e0da976c7143458ea805f3288554d4a). Not a runner envelope, so the aggregate report cannot treat it as reusable CI evidence.

reused

• none. No prior unexpired envelopes matched this worktree source digest.

skipped

• screenshots — pending_independent_tester (render impact; engineer screenshots are not independent evidence).
• playwright envelope and container runner envelope — missing/invalid after the hung suite; report generation failed closed (a required skipped component must fail the report).

not_applicable

• compatibility — outside_impact_closure (no compatibility-contract risk on these paths).
• content_invariants — outside_large_content_closure.

Commands and counts

DJANGO_SETTINGS_MODULE=website.settings.test uv run --frozen python manage.py test \
  content.tests.test_canonical_routes content.tests.test_docs_projection content.tests.test_faq \
  --keepdb -v2
# 46 passed in 18.081s

make verification-plan \
  VERIFY_BASE_SHA=284219c04e0da976c7143458ea805f3288554d4a \
  VERIFY_HEAD_SHA=284219c04e0da976c7143458ea805f3288554d4a \
  VERIFY_CONSUMER=engineer VERIFY_ISSUE=184 \
  VERIFY_OUTPUT_DIR=.tmp/verification

make verification-run \
  VERIFY_WORKTREE=issue-184-slack-canonical-284219c VERIFY_ISSUE=184 \
  VERIFY_CONSUMER=engineer VERIFY_PRODUCER_ROLE=engineer VERIFY_PHASE=engineer \
  VERIFY_BASE_SHA=284219c04e0da976c7143458ea805f3288554d4a \
  VERIFY_HEAD_SHA=284219c04e0da976c7143458ea805f3288554d4a \
  VERIFY_OUTPUT_DIR=.tmp/verification
# selector/evidence_validation/quality success; django failure (pre-existing);
# playwright hung/failed (pre-existing a11y + no envelope)

make verification-container \
  VERIFY_CONTAINER_OUTPUT=.tmp/verification/evidence/container-check.json
# status=pass

Artifact / report paths

• Plan: /home/alexey/git/dtc-website/.tmp/website-184-engineer-284219c/.tmp/verification/verification-plan.json
• Evidence dir: /home/alexey/git/dtc-website/.tmp/website-184-engineer-284219c/.tmp/verification/evidence/
• Run log: /home/alexey/git/dtc-website/.tmp/website-184-engineer-284219c/.tmp/verification/verification-run.log
• Aggregate report: not produced (report check failed closed on skipped required components)

Screenshots

pending_independent_tester. Graph-required: / and /__verification_missing__ desktop+mobile. Issue-required (tester): /docs/general/slack/, /docs/courses/ml-zoomcamp/getting-started/, /faq/machine-learning-zoomcamp.html, /slack at desktop and mobile. Engineer-produced screenshots are not independent evidence.

Behavior

• Docs Markdown link destinations to app.slack.com/client/T01ATQK62F8/… or datatalks-club.slack.com/… render href="/slack" (query/fragment dropped). 16 pages / 32 distinct URLs / 72 occurrences covered.
• Absolute https://datatalks.club/slack destinations render as /slack with query/fragment preserved (6 pages).
• slack.com/help/…, /docs/general/slack/, other workspaces, literals, and code spans stay byte-for-byte.
• Both FAQ workspace answers render href="/slack"; the ML FAQ slack.com/help citation stays external.
• GET/HEAD /slack/guidelines.html?x=1 → 301 /slack?x=1 (raw query); POST → 405 Allow: GET, HEAD, Cache-Control: no-store, max-age=0.
• content/docs_projection.json and content/faq_projection.json remain byte-identical after render.

Limitations

• Worktree left uncommitted for tester review.
• Full make test / make test-playwright on this 284219c worktree are red for pre-existing reasons unrelated to Make /slack the canonical destination for Slack links in the Docs #184. Focused Django coverage for this issue is green (46/46).
• Aggregate verification report could not be sealed because playwright/container runner envelopes are missing after the hung full browser suite.
• No join/invite link was added on /slack. Event-description policy and article-FAQ pipeline were not changed.

Ready for independent tester on worktree issue-184-slack-canonical-284219c.

[alexeygrigorev]

Tester Final

PASS

Independent verification of uncommitted #184 on the frozen engineer worktree. Homepage templates/copy were not touched. No new DESIGN_5A_* / design_5a identifiers were added. Community-workspace Slack destinations in Docs and course FAQ render as root-relative /slack. Absolute https://datatalks.club/slack hub links normalize to /slack with query/fragment preserved. GET/HEAD /slack/guidelines.html is a one-hop 301 to /slack with the same method/query/cache contract as /slack.html. Spec 01 gained only the public-vs-member-flow clarifying sentence.

Frozen candidate

• Worktree: /home/alexey/git/dtc-website/.tmp/website-184-engineer-284219c
• Branch: issue-184-slack-canonical-284219c
• HEAD: 284219c04e0da976c7143458ea805f3288554d4a (uncommitted; git status shows the same 7 files as the engineer handoff)
• Base: 284219c04e0da976c7143458ea805f3288554d4a
• Source mode: worktree
• Source-tree digest: f48652d67030e9b2e1ed3ce1fafaafa421df274a8140a165adc7e0fe003fe2ef (tree 08215a0c76e60d48586a20a4dc4b74d3e71acfd3, 3067 entries)
• Product files only: _docs/specs/01-platform-architecture.md, content/docs_projection.py, content/faq_data.py, content/tests/test_canonical_routes.py, content/tests/test_docs_projection.py, content/tests/test_faq.py, website/urls.py
• Homepage templates/copy, core/home_content.py, projections, article-FAQ, and event-description policy: unchanged

Plan comparison (no unexplained drift)

Independently recomputed:

make verification-plan \
  VERIFY_BASE_SHA=284219c04e0da976c7143458ea805f3288554d4a \
  VERIFY_HEAD_SHA=284219c04e0da976c7143458ea805f3288554d4a \
  VERIFY_CONSUMER=tester VERIFY_ISSUE=184 \
  VERIFY_OUTPUT_DIR=.tmp/verification-tester \
  VERIFY_PLAN=.tmp/verification-tester/verification-plan.json

Field	Engineer handoff	Tester recompute	Result
Graph digest	4127118b4467a75b40b8dbadc4050b5b2dc3762b292aca93cd9309a4593bca19	same	MATCH
Policy version	4	4	MATCH
Plan file SHA-256	5a04c20498edc607c4c00bb02e95f0b19dcd32856c918aaa5ef9761b963bd8f4	1342606f02bc740e26e94ddd756c3de9c1c15f0265c7f0d08d483454dc723d8f	expected: created_at only
Plan digest (sha256_json)	de823f3c49528f4810c861cdbe35264f0d6df1b6be0023f502c4cfa791087e9d	79a00b1daaab089b7cd8ca876205acffab1129a764717c18b8eccc8e858e3437	expected: created_at only
Profile / reason	full / render_impact (basename:urls.py)	same	MATCH
Browser profile	full	full	MATCH
Direct nodes	app.content, surface.documentation, surface.website	same	MATCH
Downstream	django.accounts, django.content, django.core	same	MATCH
Risk flags	deployment_runtime, shared_runtime, test_infrastructure	same	MATCH
Render impact / digest	yes / 19d28d14414ae686e397828d3b550b94a63301ce0a91c3cc270173bafc49f498	same	MATCH
Required captures	/ and /__verification_missing__ desktop 1440×900 + mobile 390×844	same	MATCH
Dispositions	compatibility/content_invariants not_applicable; all others rerun	same	MATCH

Plans are byte-identical after stripping created_at. That timestamp drift is explained and is not a failure.

Reused provenance (validated, not treated as CI)

Every engineer success envelope was reopened. Artifact path/size/SHA-256, origin, expiry, input/environment/policy digests, result, and exit status match the handoff. Latest django/playwright results are failures, so they were not reused as passes.

Component	Evidence ID	Origin	Expiry	Counts	Artifacts
selector	8574b4c92faf81254a257a5e5b137f6c7486c6d4c4e9f246a5a13fac1923c300	local engineer	2026-08-25T18:25:12Z	exit 0	SHA-256 OK
evidence_validation	a553609e2aac7580dbf1c4053e474da9c574fad18df61d047d046d471b07cc65	local engineer	2026-08-25T18:25:30Z	531 passed / 0 failed	SHA-256 OK
quality	b8fb63d678f7de6b4cb4c56d0ef23eaf0974adb945fd9fe7f815ac4e45f3a2af	local engineer	2026-08-25T18:26:34Z	quality-contract-v1; 531 passed / 0 failed (includes migrations-check)	SHA-256 OK
django	46a290d4886039020db0935a13146e20b40595a8013dbb53a1e4c54989d94cdf	local engineer	2026-08-25T18:29:08Z	failure exit 2 (make test)	SHA-256 OK; not reused as pass
container standalone	cdd46cf957c72fd2dcb9cecd4a78c87b228d716ea9fb83fa714e6d0dab3251fd	engineer make verification-container	n/a	status=pass, revision 284219c	not a runner envelope

Commands and counts executed here

DJANGO_SETTINGS_MODULE=website.settings.test uv run --frozen python manage.py test \
  content.tests.test_canonical_routes content.tests.test_docs_projection content.tests.test_faq \
  --keepdb -v2
# 46 passed / 0 failed in 24.558s

make verification-plan VERIFY_CONSUMER=tester ... VERIFY_OUTPUT_DIR=.tmp/verification-tester
# graph/plan/dispositions match; only created_at differs

# Application start: documented `make run` equivalent on a free loopback port
# (host :8000 is occupied by an unrelated process). Local SQLite migrated first.
DJANGO_SETTINGS_MODULE=website.settings.local uv run --frozen python manage.py migrate --noinput
DJANGO_SETTINGS_MODULE=website.settings.local uv run --frozen python manage.py runserver 127.0.0.1:8011 --noreload
# then independent Playwright capture of graph + issue routes

make test-playwright-core
# collected 205 / selected 177 core tests; multiple pre-existing failures appeared
# immediately (a11y smoke, homework breadcrumb, design-parity/home). Run killed at 300s.
# Not a #184 regression; same class of pre-existing red the engineer reported on this SHA.

Four-bucket tester-final report

rerun

• selector — tester plan regenerated; semantic match to engineer plan.
• django (issue closure) — focused Docs/FAQ/canonical suite 46 passed / 0 failed.
• screenshots — independent desktop/mobile capture and inspection (14 views). Issue routes pass. Graph 404 mobile overflow is the local DEBUG=True technical 404 page from make run, not the product 404.

reused

• evidence_validation — engineer success, independently hash-validated (531/0).
• quality — engineer success, independently hash-validated (531/0; migrations-check included).

skipped

• none required for Make /slack the canonical destination for Slack links in the Docs #184 acceptance. Planned full make test / make test-playwright remain red on this frozen 284219c for pre-existing reasons already recorded by the engineer (event-title Q&A vs Q&A; events-hub duplicate ids / homework breadcrumb). Those failures are not caused by the Slack rewrite and are not reused as passes.

not_applicable

• compatibility — outside_impact_closure
• content_invariants — outside_large_content_closure

Screenshots

Independent envelopes: .tmp/screenshots/issue-184/screenshots.json (SHA-256 d965bff167dde424a1d7ab5e87cc2161eafdae3936152bbddf9a8d01af41c636). Every image was opened and inspected.

Graph-required:

• .tmp/screenshots/issue-184/home-home-desktop-1440x900.png — homepage 200, current 5a composition, Slack in nav. No overflow.
• .tmp/screenshots/issue-184/home-home-mobile-390x844.png — same page at 390×844. Readable. No overflow.
• .tmp/screenshots/issue-184/verification-missing-not-found-desktop-1440x900.png — 404 (local DEBUG technical page). slack/guidelines.html is listed in the resolver.
• .tmp/screenshots/issue-184/verification-missing-not-found-mobile-390x844.png — same 404; horizontal overflow 669/390 from the DEBUG resolver dump. Not a product-page layout break and not introduced by Make /slack the canonical destination for Slack links in the Docs #184.

Issue-required (all 200, no workspace hrefs, no overflow):

• .tmp/screenshots/issue-184/docs-general-slack-docs-slack-desktop-1440x900.png and ...-mobile-390x844.png — Slack Community docs page; channel entries present; slack.com/help citation remains; 33/31 href="/slack".
• .tmp/screenshots/issue-184/docs-courses-ml-zoomcamp-getting-started-docs-ml-getting-started-desktop-1440x900.png and ...-mobile-390x844.png — Getting Started page; Slack workspace/channel copy present; 3 href="/slack".
• .tmp/screenshots/issue-184/faq-machine-learning-zoomcamp-html-faq-ml-desktop-1440x900.png and ...-mobile-390x844.png — ML Zoomcamp FAQ; 3 href="/slack" plus the slack.com/help citation.
• .tmp/screenshots/issue-184/slack-slack-desktop-1440x900.png and ...-mobile-390x844.png — public /slack landing with channel chips and troubleshooting CTA. No join/invite link. /slack content unchanged.
• .tmp/screenshots/issue-184/slack-guidelines-html-slack-guidelines-alias-desktop-1440x900.png and ...-mobile-390x844.png — /slack/guidelines.html?utm_source=docs finished at /slack?utm_source=docs (one hop). Same page bytes as /slack.

No captured page emitted app.slack.com or datatalks-club.slack.com hrefs.

Acceptance criteria

• Rendered Docs workspace destinations emit href="/slack"; no rendered Docs page emits the old workspace hosts (focused tests + live href inventory).
• All 16 affected Docs pages and both FAQ answers are covered by focused tests that assert rendered HTML.
• Absolute https://datatalks.club/slack destinations render as /slack with query/fragment preserved.
• slack.com/help/..., /docs/general/slack/, and unrelated externals stay byte-for-byte.
• GET/HEAD /slack/guidelines.html?x=1 → 301 /slack?x=1; POST → 405 Allow: GET, HEAD, Cache-Control: no-store, max-age=0.
• Docs and FAQ projections remain immutable.
• Rendered-page link resolution now points internally at /slack (compat component remains graph not_applicable).
• Spec 01 gained only the clarifying sentence; member-flow contract otherwise unchanged.
• Tester screenshots at desktop and mobile for the four issue routes show the expected pages with working /slack links, not errors or broken layouts.

Findings

1. No Make /slack the canonical destination for Slack links in the Docs #184 functional defects. Scope is tight: render-time rewrite + one alias + one spec sentence. No homepage/template/DESIGN_5A_* leakage.
2. Planned full make test / make test-playwright on this frozen SHA are pre-existing red. Not caused by Make /slack the canonical destination for Slack links in the Docs #184. Focused closure is green (46/46).
3. Local make run 404 is Django's DEBUG technical page; mobile overflow there is that dump, not the Slack pages.
4. /slack still has no join/invite link, matching the explicit non-goal.

Ready for PM acceptance.

[alexeygrigorev]

Product Acceptance

ACCEPT

/slack is now the one canonical community-Slack destination in rendered Docs and course FAQ. Independent tester-final PASS is valid: every required component is classified once, there are no required skips or pending screenshots, reuse of evidence_validation and quality is hash-validated, and compatibility / content_invariants are not_applicable with graph reasons.

Visitor / operator review

• Docs /docs/general/slack/ and /docs/courses/ml-zoomcamp/getting-started/ render as the expected pages. Channel and community links go to /slack, not app.slack.com or datatalks-club.slack.com. Slack product-doc citations stay on slack.com/help.
• Course FAQ /faq/machine-learning-zoomcamp.html is the expected ML FAQ, not an error page. Workspace answers resolve to /slack.
• /slack itself is unchanged: community intro, eight channel chips, troubleshooting CTA, no join/invite link. /slack/guidelines.html?utm_source=docs finishes in one hop at /slack?utm_source=docs with the same page.
• Desktop and mobile issue-route captures are readable and usable. Graph-required homepage captures still show the current 5a homepage; Slack remains a nav destination only.
• The graph 404 mobile overflow is Django’s local DEBUG=True resolver dump from make run, not the product 404 and not a Make /slack the canonical destination for Slack links in the Docs #184 layout break.

Scope and non-goals

• Uncommitted diff is the seven expected files only. Homepage templates/copy, core/home_content.py, projections, article-FAQ, and event-description policy are untouched.
• Spec 01 gained only the public /slack vs member-flow reveal sentence. Member-onboarding contract is otherwise unchanged.
• Pre-existing red on full make test / Playwright at frozen 284219c is recorded and not caused by this rewrite; focused Docs/FAQ/canonical coverage is 46/46.

Ready for engineer commit (Closes #184) and local merge.