Summary
Four server-side feature stacks are completely dead: bookmark, certificate, discussion, and progress. Their route modules and utility modules exist in the repo but are never registered or imported anywhere. The features they advertise (server-side bookmarks, project certificates, a discussion forum, progress tracking) do not exist on the running site; only static JS/CSS and page-landmark tests cover them.
Dead files
Routes (repo root routes/):
routes/bookmark_routes.py
routes/certificate_routes.py
routes/discussion_routes.py
routes/progress_routes.py
Utils (repo root utils/):
utils/bookmark_manager.py
utils/certificate_generator.py
utils/discussion_manager.py
utils/progress_tracker.py
Evidence
src/app.py registers only auth_bp, admin_bp, main, and github_bp (lines 95-102). None of the four route modules are imported or registered.
- A repo-wide import search (
from routes.bookmark..., from utils.bookmark_manager..., etc.) returns no application code referencing them.
- Neither the root
routes/ nor the root utils/ directory contains an __init__.py (they shadow the real packages src/routes/ and src/utils/ and are not importable as packages).
tests/test_bookmarks.py only verifies that the bookmark static files (bookmarks.js, bookmarks.css) are served and that the homepage contains bookmark UI landmarks — it never exercises any backend API.
- The tests for the four utils (
test_certificate_generator.py, test_discussion_manager.py, etc.) only exercise the utility classes directly; no HTTP endpoint calls them.
Impact
- Advertised features (certificates for completed projects, a discussion/Q&A forum, server-side bookmarks, progress tracking) are silently missing.
- The
User DB columns intended for bookmarks/skills are never written (see profile issue), because the module that would write them is dead.
Suggested Fix
Either register the missing blueprints and wire them to the frontend, or delete the dead modules and remove the feature references from the README/UI. At minimum, add an __init__.py or move these into src/ so they do not shadow the real packages.
Summary
Four server-side feature stacks are completely dead: bookmark, certificate, discussion, and progress. Their route modules and utility modules exist in the repo but are never registered or imported anywhere. The features they advertise (server-side bookmarks, project certificates, a discussion forum, progress tracking) do not exist on the running site; only static JS/CSS and page-landmark tests cover them.
Dead files
Routes (repo root
routes/):routes/bookmark_routes.pyroutes/certificate_routes.pyroutes/discussion_routes.pyroutes/progress_routes.pyUtils (repo root
utils/):utils/bookmark_manager.pyutils/certificate_generator.pyutils/discussion_manager.pyutils/progress_tracker.pyEvidence
src/app.pyregisters onlyauth_bp,admin_bp,main, andgithub_bp(lines 95-102). None of the four route modules are imported or registered.from routes.bookmark...,from utils.bookmark_manager..., etc.) returns no application code referencing them.routes/nor the rootutils/directory contains an__init__.py(they shadow the real packagessrc/routes/andsrc/utils/and are not importable as packages).tests/test_bookmarks.pyonly verifies that the bookmark static files (bookmarks.js,bookmarks.css) are served and that the homepage contains bookmark UI landmarks — it never exercises any backend API.test_certificate_generator.py,test_discussion_manager.py, etc.) only exercise the utility classes directly; no HTTP endpoint calls them.Impact
UserDB columns intended for bookmarks/skills are never written (see profile issue), because the module that would write them is dead.Suggested Fix
Either register the missing blueprints and wire them to the frontend, or delete the dead modules and remove the feature references from the README/UI. At minimum, add an
__init__.pyor move these intosrc/so they do not shadow the real packages.