alejandrotejero/gamerank

Purpose and Runtime

GameRank is a server-rendered Django 5.1 web application for aggregating game catalog data and supporting authenticated user interactions: ratings, comments, comment reactions, follows, profile settings, and JSON game export. It runs via Django’s development/WSGI/ASGI entry points: project/manage.py, project/project/wsgi.py, and project/project/asgi.py. Persistence is SQLite (project/db.sqlite3); remote catalog ingestion uses requests.

Request Routing and Presentation

Project-level routing delegates application URLs through project/project/urls.py and project/gamerank/urls.py. Request handlers in project/gamerank/views.py render Django templates, primarily using shared layout/navigation plus catalog, detail, account, and interaction screens:

• project/gamerank/templates/gamerank/base.html

• project/gamerank/templates/gamerank/detalles_juego.html

• project/gamerank/templates/gamerank/detalles_juego_dinamico.html

Django’s registration/login templates under project/gamerank/templates/registration integrate with the authentication flow.

Domain and Persistence Model

The core domain is defined in project/gamerank/models.py and evolved through project/gamerank/migrations/. It centers on games with source-prefixed stable IDs, stored rating aggregate fields and vote counts; user-to-game ratings; comments; per-user comment votes; game follows; and user profile data. The migrations show the key schema evolution for ratings, followers, profiles, and comment likes/dislikes:

• project/gamerank/migrations/0002_game_rating_game_votes.py

• project/gamerank/migrations/0005_perfilusuario.py

• project/gamerank/migrations/0008_votocomentario.py

Catalog Ingestion Boundary

Catalog synchronization is separated from request views in project/gamerank/manageData.py. This boundary consumes a remote XML feed and the FreeToGame and MMOBomb APIs, normalizes source records, and persists them as games under LIS1-, FTP-, and MMO- ID namespaces. Remote network/API variability is therefore isolated from the local database-backed browsing experience.

Game Interaction Flows

Catalog requests list games ordered by stored aggregate rating and can filter by source prefix. Detail requests combine game metadata with ratings and comments. Authenticated actions update relational state: one rating per user/game is created or revised, then the game’s average and vote count are recalculated; comments are attached to games; comment reactions toggle or switch like/dislike state; and follows create/remove user-game membership. These flows are implemented across project/gamerank/views.py, project/gamerank/forms.py, and project/gamerank/models.py.

Dynamic and Export Interfaces

The dynamic game-detail variant supports HTMX-driven comment refreshes, allowing a fragment response rather than a full document reload:

• project/gamerank/templates/gamerank/detalles_juego_dinamico.html

• project/gamerank/templates/gamerank/comments.html

A separate view path exposes individual game information as JSON for download/API-like consumption. This is a server-generated export over the same persisted game model, not a separate service.

User Experience and Shared UI

Shared navigation, footer content, and styling support the server-rendered interface:

• project/gamerank/templates/gamerank/navbarFuncional.html

• project/gamerank/manageFooter.py

• project/gamerank/static/css/style.css

User-facing account pages surface voting metrics, followed/voted games, and profile alias/font preferences through the same Django session/authentication boundary.