FAQ

Answers to the questions we hear most. Can’t find yours? Ask in #tech-support or email support@ebrains.eu.

About the Handbook

The handbook is written for current and future EBRAINS team members. It brings together how EBRAINS is organised, how we work together, and the tools, practices and references you need to do your role well.

The sections follow the way people use EBRAINS, from onboarding to deep technical reference:

Use the sidebar to jump between sections, the search in the header (or ⌘ K) to find a page, and the previous / next links at the end of each page to read a section in order.

Yes. The Glossary defines the terms and acronyms used across EBRAINS, with a reference and sources for each.

Content is updated with each new release, typically after every 5–10 commits, or straight away when a critical change is needed. The release notes list what changed.

Getting started

Start with Your First Week at EBRAINS: a step-by-step tutorial covering your account, the infrastructure, key resources and where to get help. Then continue with Navigate the EBRAINS Infrastructure.

Register at EBRAINS Sign Up. Registration requires an institutional email address, for example from your university or research institution; personal addresses (Gmail and similar) typically won’t work. The full steps are in Your First Week at EBRAINS.

The main ones are EBRAINS GitLab, Forms, Notes, the Lab and Chat. Collaboration Tools explains each of them, and EBRAINS Interact covers the practices for using them well.

GitLab at EBRAINS is the cornerstone of our development process: version control, project management and CI/CD. The Version Control section explains how we use it, from creating a project to opening merge requests.

Getting help

Use the Incident Report form. Incident Response explains what happens next and how incidents are handled.

Membership

Institutions apply to the EBRAINS Governing Board for status as a Full Member or an Associate Member. Apply for Membership walks through the five steps, from the application to the signature of the Accession Agreement. For questions, email info@ebrains.eu.

Full Members have voting rights at the General Assembly, take part in the governance structures and can lead an official National Node. Associate Members take part in selected meetings and working groups. There can only be one Full Member per country. Membership Categories compares the two in full.

Contributing to the handbook

Every EBRAINS member is welcome to contribute. Pick the way that suits you:

The Quick Start for Content Authors covers the basics in five minutes. The handbook owners review every merge request before anything is published.

Yes. The assistant needs neither Git, Markdown nor the folder structure: sign in with your EBRAINS account and paste notes, an email or a document. If you already have a Markdown file, you can also share it with a project owner, who will add it for you.

In the top-level folder that matches your topic, for example:

  • Team process docs → working-together/
  • Technical guides → technical-deep-dive/
  • Tool documentation → tools-and-resources/

_index.md creates a section: the landing page of a folder. my-page.md creates a regular page inside that section. Create Sections and Your First Page show both.

When you edit online there is no easy preview. Locally, you need the full handbook app running (see the technical setup guide). Most authors simply commit and rely on the review: the handbook owners check every merge request before it is published.

Don’t worry, that’s what reviews are for: nothing is published until it has been reviewed. If you’re really stuck, share your Markdown file with a project owner and they’ll integrate it for you.

Building for EBRAINS

Yes. The EBRAINS Design System provides the components, design tokens and brand assets, and Design System in this handbook explains how to integrate it. The EBRAINS UI Ecosystem tutorials take you from a first app to a configured Tailwind setup.

In the EBRAINS Docker Registry (Harbor). Publish Your First Docker Image walks through it.