Changelog

Minor wording improvements.

• ✓Minor wording clarifications across the site.

CERNBox no longer needs a request, and service access now updates correctly.

• ✓CERNBox is now available on its own once your account is ready — no group request needed.
• ✓Fixed service access (SWAN, REANA, Rucio, CERNBox) sometimes staying stuck as "pending", or not showing as granted, after approval.
• ✓The homepage now names the Node "CERN EOSC Node", matching its official EOSC Federation registration.

Cosmetic improvements.

• ✓Minor UI adjustments.

Production readiness banner.

• ✓Added a banner at the top of every page noting that the CERN Node is not in production yet.

Fixed the public Route still carrying its CERN-internal restriction.

• ✓The restriction is now removed on every prod deploy.

The CERN Node is now open to the public internet.

• ✓eosc.cern is reachable from outside CERN for the first time.
• ✓Fixed the Status page occasionally showing "temporarily unavailable" right after a deploy.

A CERN-wide top bar now sits above the site header.

• ✓Added a CERN global top bar (CERN | Accelerating science, and a link to the CERN Directory) above the header, matching cern.ch’s masthead style.
• ✓The footer now uses the same dark CERN palette as the new top bar.

The Node now publishes the policies that govern its services.

• ✓New Policies section: the Acceptable Use Policy, the User Access Policy, and the Terms and Conditions, reachable from every page without signing in.
• ✓Each service in the catalogue now links to the two policies that govern it.
• ✓The service catalogue feed now carries the policy, helpdesk and security-contact links, so they travel with the Node’s entry in the EOSC Resource Hub.
• ✓Added Matomo-based traffic analytics, hosted by CERN. No cookies are set and browsers sending "Do Not Track" are excluded automatically.

Site fonts and footer logo now follow CERN's design guidelines.

• ✓Switched the site to Open Sans for headings and Source Sans Pro for body text, per CERN's web fonts guideline.
• ✓The CERN logo in the footer now links to home.cern and is sized to meet CERN's logo guidelines.

Fix a duplicate-site issue on eosc.cern.ch.

• ✓eosc.cern.ch now redirects to eosc.cern instead of serving a separate copy of the site.

New support channels on the Contact page.

• ✓The Contact page now offers two channels instead of one: the EOSC Federation Forum for lasting Q&A, and the CERN Node Helpdesk for tracked tickets.

Small fixes.

• ✓The Training & Tutorials card on the Get Started page now uses the same icon as the Training section below it.

HEP Training catalogue, EOSC monitoring feeds, and several small fixes.

• ✓Added /training: a searchable browser over CERN’s HEP Training catalogue, linked from the header and the Get Started page.
• ✓The service catalogue is now also published as a machine-readable EOSC Service Bundle feed, and the Node exposes live status and availability metrics in the EOSC ARGO Monitoring format, for the EOSC Federation’s own systems to consume.
• ✓Added a support email to the Contact page, and cross-links from Services to the Technology page and from the CERN Node page to its listing on the EOSC Federation site.
• ✓Added this changelog page.

Small polish release.

• ✓The footer now shows exactly which version of the site is running.
• ✓Cleaned up icons and made service names consistent across pages.

A new status page, access control, and the FAQ.

• ✓Rebuilt the status page on a dedicated monitoring backend, with live checks for the CERN Node services.
• ✓Service catalogue access is now gated by IdP group membership, with a request-access flow for signed-in users.
• ✓Added the FAQ page and the rollout stages timeline on the CERN Node page.

First release — the CERN Node site goes live for the build-up phase.

• ✓Site structure: sticky header with dropdown navigation, a contextual "On This Page" sidebar, and a full-width homepage.
• ✓Services catalogue listing CERN platforms.
• ✓Analysis catalogue with real ATLAS Open Data and interactive SWAN notebooks, including a first CMS analysis example.