What is ECMWF Sites?¶

ECMWF Sites is a managed service for hosting and sharing web content at ECMWF.

You can think of it as a place where you can create a “site” (a web area) for a team, project, or service, and then:

• publish files (documents, images, data)
• publish simple web content
• control who can see it (private/public, users/groups)
• automate updates with the Sites CLI, Sites SDK, or Site API

The service takes care of the infrastructure and day‑to‑day running.

When should I use it?¶

Use ECMWF Sites when:

• you need a lightweight webspace that’s easy to manage
• you want a URL that colleagues can use immediately
• you want access control tied to ECMWF users/groups
• you want to automate publishing through an API

Key ideas (in plain language)¶

• Hub: the main web portal where you create and manage sites.
• Site: your web area.
• Space: a grouping, often your team or project name, used in the URL.
• Site API: an HTTP API for listing/downloading/uploading content.

Typical URLs you’ll see¶

The exact hostname depends on the environment (stage vs production), but the pattern usually is:

• Hub UI: https://<domain>/hub/...
• Your site: https://<domain>/<space>/<site>/...
• Your site API: https://<domain>/<space>/<site>/s/api/v2/...

Understanding Sites URLs explains all the path types, with examples and when to use each one.

Roles¶

• Viewer: can see the site (public sites: everyone; private sites: allowed users/groups).
• Site administrator: can change site settings, manage sharing, generate tokens/links, and perform operational actions.
• Hub administrator: platform-level admin (not covered here).

If you’re unsure what you are for a given site, open the site in the Hub and check the Access section of its overview page — it shows whether you appear as Administrator or Viewer. The site’s owner (who created it) is always a site administrator.