From screen to product: review the exact version
Follow a concept through feedback, authorized approval, separate mobile design, testing, and eventual publication.
Start with a desktop concept
Generate desktop concepts for TVIJO and Centavra Play in a shared cold white and blue visual family. Give each immutable version an identifier and artifact hash before requesting feedback. Gather likes and comments in native Django admin, bound to that specific version. Feedback on an older image concerns that image. These are proposed workflow steps, not evidence that a reviewed build or public release already exists. Keep the learning task visible beside the artwork.
Distinguish feedback and authority
The existing backend stores KBArticle translations as JSON. KBLike supports a user foreign key and an anonymous nickname; KBComment has a user foreign key and body. A foreign key links a record to a user; a nickname alone establishes no staff authority. Only authenticated, active, allowlisted staff approval on an immutable artifact hash authorizes a future build. Do not expose administrator emails or invent like counts. Popularity cannot supply the missing approval.
Build through the agreed sequence
After approval, build desktop from the approved artifact, then design mobile independently around tasks and touch constraints. Test before publication, including keyboard access, focus, readable errors, motion alternatives, languages, and small screens. Resizing a desktop picture does not solve mobile interaction. A changed concept needs fresh approval for its hash; record test evidence against the built version actually tested. Preserve the connection from approved concept to build rather than treating a screenshot as a functioning product.
Make images and languages understandable
For future article pages, use an img element, descriptive filenames, meaningful alt text, useful surrounding text, and crawlable images. English is the source copy; each language page needs an appropriate canonical URL and reciprocal hreflang links. Google's primary guidance is https://developers.google.com/search/docs/appearance/google-images and https://developers.google.com/search/docs/specialty/international/localized-versions. These practices support comprehension and discovery without guaranteeing ranking. Describe what an image contributes instead of filling its alternative text with keywords. Keep Russian correspondence accurate when the English source changes.
Make one review concrete
The actual next action is to label one desktop concept with its version and hash, then write feedback about one keyboard journey. State the expected action, visible response, and evidence needed to check it.
Try it yourself
DEMO review: concept A has likes; B has an anonymous comment; C has valid approval from authenticated, active, allowlisted staff for hash HC. Which may enter a future desktop build? Acceptance: only the artifact matching HC. Any changed concept requires its own hash-bound approval.
Check your result
- Feedback remains bound to its specific version.
- Desktop build precedes independent mobile design, tests, and publication.
- General likes and anonymous nicknames cannot authorize a build. An authenticated allowlisted administrator’s like selects only its exact concept version.
This draft stays on your device until you download it. Use the TVIJO discussion for server-stored feedback.