This section is new, and it is open for comment
Release notes and governance decisions now have a home on the site instead of living only in commit messages. Every post takes comments — with a few rules that a cancer-information site genuinely needs.
Until now, everything about how OpenOnco changes lived in commit messages, review documents and specs. That is fine for contributors reading the repository and useless for a clinician who wants to know what moved this month. This section is the fix.
Posts are written in both English and Ukrainian, and they are checked into the repository as structured YAML under content/news/. They are built by the same pipeline as the rest of the site, so a post is reviewable as a diff like everything else here.
One request
Comment threads are public and indexed by search engines, so please keep your own medical details out of them — a diagnosis or a set of test results is not something you can really take back once it is on a public page.
And if you have found something clinically wrong in the knowledge base, a comment is not the fastest route. Open an issue tagged clinical-error instead: per CHARTER §9.1 that path has a triage SLA of 48 hours, and it leaves a public record of the fix.
How comments work
You do not need an account. Type a name and a comment and post it — no sign-up, no login, no GitHub. The comment box runs on infrastructure the project controls, so there is no third-party advertising and no tracking network attached to it.
Each article has one comment thread shared between its English and Ukrainian versions, so a discussion does not get split in half by which language you happened to be reading in.
Comments
Threads are public and indexed — please keep personal medical data out of them. Found a clinical error? Open an issue instead.
Comments are not switched on yet — the backend still needs to be configured.