Rebuild the site as a datasheet rather than a landing page - #8
Merged
Conversation
The old page read as a developer portfolio: a terminal mock with fake traffic lights, pill-shaped tags, rounded cards, icon circles. Those are decorations standing in where a fact should be, and the copy had the same problem - a rhetorical question opening the course section, "Interfaces, not just libraries", "Structure that outlives the sprint". Clever headings and the not-just-X-but-Y construction are exactly what the writing standard in this organisation rejects. What replaces it is the shape a specification uses. Near-black, one accent, hairline rules, no rounded corners and no shadows. Every number now carries the conditions it was measured under directly beneath it: 86% is followed by "line coverage, pytest-cov in CI, the build fails below the threshold". A claim with its measurement attached is the thing that reads as premium; an adjective is not. Headings are plain nouns now - Projects, Method, Licensing - and the sections were renamed accordingly, so #course became #reading and #engineering became #method on both language pages and in the legal page's navigation. Also fixed while here: stadion and research were missing from the site entirely. A visitor reading only this page would not have learned either existed. The colour-scheme toggle is gone. The site commits to one scheme, for the reason already written into the lemma documentation: a toggle means designing the whole thing twice, and the second design is the one nobody checks. That removed the theme code from site.js and the pre-paint script from every page. Clause 7 of the privacy policy described storing a chosen theme in localStorage. With no theme to store, the clause described behaviour that does not happen, so it now says the site stores nothing at all. That is the only change to the legal text.
The English footer linked the legal document with a Cyrillic label. A reader who cannot read the label cannot tell what the link is, and finds out by clicking into a document they also cannot read. The language switcher beside it stays in Russian, because that is what it is for: it is written in the language it points at so a speaker of that language recognises it. The legal link is not a switcher, so it now reads Legal (in Russian) - the destination named in the reader's language, with the language of the destination attached. The document itself being Russian-only is the actual problem and is not fixed here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The old page read as a developer portfolio: a terminal mock with fake traffic lights, pill-shaped tags, rounded cards, icon circles. Those are decorations standing in where a fact should be.
The copy had the same problem, and against this organisation's own writing standard: a rhetorical question opening the course section,
Interfaces, not just libraries,Structure that outlives the sprint. Clever headings and the not-just-X-but-Y construction are the two things that standard rejects by name.What replaces it
The shape a specification uses. Near-black, one accent, hairline rules, no rounded corners, no shadows, no gradients outside the mark.
Every number now carries the conditions it was measured under, directly beneath it —
86%is followed by line coverage, decisionrl, measured by pytest-cov in CI; the build fails below the threshold rather than reporting it. A claim with its measurement attached is what reads as premium. An adjective is not, and this organisation already says so in rule 03.Headings are plain nouns: Projects, Method, Licensing. Sections renamed to match, so
#course→#readingand#engineering→#method, on both language pages and in the legal page's navigation.Fixed while here
stadion and research were not on the site at all. A visitor reading only this page would not have learned either exists. Both are now in Projects and in the footer.
The colour-scheme toggle is gone. The site commits to one scheme, for the reason already written into the lemma documentation: a toggle means designing the whole thing twice, and the second design is the one nobody checks. That removed the theme code from
site.jsand the pre-paint script from all four pages.Clause 7 of the privacy policy is corrected. It described storing a chosen theme in
localStorage. With no theme to store it described behaviour that does not happen, so it now states that nothing is stored. That is the only change to the legal text — the document keeps its edition date and everything else is untouched.Verified
python scripts/check_site.py .passes on all four pages: structure, metadata, links, anchors and self-containment.Rendered locally and checked in the browser at 1280px and at mobile width: no horizontal overflow at either, every measured
border-radiusis0px, the burger replaces the nav below 760px, and the legal page picks up the new system through its existing class names rather than being rewritten.