Designer Guide
Neurodesk Design Style Guide
Section titled “Neurodesk Design Style Guide”This style guide provides clear standards to ensure visual consistency across all Neurodesk platforms and materials.
Brand overview
Section titled “Brand overview”Neurodesk is a community-oriented open-source solution for neuroimaging analysis with four guiding principles: accessibility, portability, flexibility and, overarchingly, reproducibility. This guide ensures visual consistency across all Neurodesk products and documentation.
Where these files live
Section titled “Where these files live”All Neurodesk visual assets are stored in the neurodesk/media repository, which is the single source of truth. This page explains how to use them; the repository holds the files themselves.
If an asset is missing, or you need a variant that doesn’t exist, open an issue rather than editing an existing file.
Licensing and permitted use
Section titled “Licensing and permitted use”Two different sets of terms apply, and the distinction matters.
| What | Terms |
|---|---|
| Figures, diagrams, and screenshots | CC BY 4.0 — reuse freely with attribution |
| The Neurodesk name and logo | Project marks — not CC BY |
Attribution string: Neurodesk (https://neurodesk.org), CC BY 4.0
You may, without asking
Section titled “You may, without asking”- Use an unmodified logo to link to neurodesk.org or a Neurodesk repository.
- Use an unmodified logo in slides, posters, papers, or blog posts that describe, teach, review, or cite Neurodesk.
- State truthfully that your tool, pipeline, or course uses or supports Neurodesk.
- Scale the logo proportionally, and choose whichever variant reads best on your background.
Please ask first
Section titled “Please ask first”Open an issue on neurodesk/media, or email mail.neurodesk@gmail.com, before you:
- Change the logo’s colours, proportions, typography, or artwork.
- Combine it with another mark into a new lockup.
- Use it on merchandise, event branding, or in a domain name.
- Use it in a way that could imply Neurodesk endorses or certifies your product.
Neurodesk is a community project and generally says yes — asking is mostly so we know it is happening.
Full detail is in BRAND.md.
Logo usage
Section titled “Logo usage”Below are the official Neurodesk logos. Every file links to its copy in the media repository.
The chequerboard behind each preview marks the transparent areas of the PNG — the logos have no background of their own. Light chequers are used for the standard variants and dark ones for the -on-dark variants, matching the background each was drawn for.
Acceptable logo usage
Section titled “Acceptable logo usage”Use these logos on light or neutral backgrounds.
Simple logo
Section titled “Simple logo”
Inclusivity and Pride logo
Section titled “Inclusivity and Pride logo”
Horizontal format logo
Section titled “Horizontal format logo”
Logos for dark backgrounds
Section titled “Logos for dark backgrounds”These logos are optimised for use on dark backgrounds.
Simple logo
Section titled “Simple logo”
Inclusivity and Pride logo
Section titled “Inclusivity and Pride logo”
Other variants
Section titled “Other variants”No image
Which variant should I use?
Section titled “Which variant should I use?”| Context | Variant |
|---|---|
| Light or neutral background | the standard variant |
| Dark background | the -on-dark variant |
| Wide header, one line of space | the -horizontal variant |
| You want the web address visible | the neurodesk-org- prefix |
| Pride and inclusivity contexts | the -pride variant |
Colour palette
Section titled “Colour palette”The palette is published in several formats so you do not need paid software to use it.
| Format | Opens in | Download |
|---|---|---|
| PowerPoint | PowerPoint, Keynote, Google Slides, LibreOffice | .pptx |
| Adobe swatches | Illustrator, Photoshop, InDesign, Affinity, Figma | .ase |
| GIMP palette | GIMP, Inkscape, Krita | .gpl |
| CSS custom properties | any text editor, for web work | .css |
| JSON | scripts and build tooling | .json |
| Illustrator swatches | Illustrator only — the original file | .ai |
Hex is canonical. The RGB column below is derived from it.
Primary colours
Section titled “Primary colours”| Colour name | Hex code | RGB code | Usage |
|---|---|---|---|
| Seafoam green | #6aa329 | (106, 163, 41) | Primary actions |
| Logo ink | #101806 | (16, 24, 6) | The dark used in the logo artwork |
Secondary colours
Section titled “Secondary colours”| Colour name | Hex code | RGB code | Usage |
|---|---|---|---|
| Black | #0c0e0a | (12, 14, 10) | Regular text, menu bar |
| Darkest green | #161c10 | (22, 28, 16) | Successful selection |
| Muted olive green | #1e2a16 | (30, 42, 22) | Accent background |
| Dark olive green | #4f7b38 | (79, 123, 56) | Selected buttons, hyperlinks |
| Light green | #b7d886 | (183, 216, 134) | Hover over a button |
| Lighter green | #d3e7b6 | (211, 231, 182) | |
| Verdant haze | #e6f1d6 | (230, 241, 214) | Unselected buttons |
| Pale lime green | #f0f7e7 | (240, 247, 231) | |
| White | #ffffff | (255, 255, 255) |
Hex codes are authoritative; the RGB column is derived from them. Do not sample colours from a rendered logo — anti-aliasing gives slightly different values.
Naming and capitalisation guidelines
Section titled “Naming and capitalisation guidelines”To ensure consistency in our branding, please follow the guidelines below when referring to Neurodesk and its associated tools.
Correct usage
Section titled “Correct usage”- Neurodesk: capitalise only the first letter.
neurodeskorNEURODESKmay be used where the surrounding style calls for it, such as an all-caps heading or a lowercase URL.
- Use “Neurodesk” to refer to the overall project, platform, or community.
- Use consistent casing in product names:
- Neurodesktop
- Neurocommand
- Neurocontainers
- NeurodeskApp
Do not use
Section titled “Do not use”Avoid the following incorrect variations:
- Variants with an internal capital letter
Neuro Desk— space in the middleneurodeskin running prose, titles, or headings, where Neurodesk is correct
Icons and favicons
Section titled “Icons and favicons”The icon mark on its own, plus a complete favicon set.
Source icons
Section titled “Source icons”| File | What it is |
|---|---|
neurodesk-icon.svg | The icon mark — outlined, no font dependency. Everything else derives from this. |
neurodesk-icon-solid.svg | Solid dark box and brain |
neurodesk-icon-outline.svg | White / outline treatment |
neurodesk-icon-green-circle.png | White box and brain in a green circle |
Favicon set
Section titled “Favicon set”.ico ·
16px ·
32px ·
Apple touch ·
Android 192 ·
Android 512 ·
Windows tile ·
Safari pinned tab ·
web manifest
These are stored under this repository’s naming convention rather than the filenames
browsers expect. Copy them out and rename to whatever your framework wants —
icons/README.md has the
mapping.
Typography
Section titled “Typography”Scirich Regular
Section titled “Scirich Regular”Scirich is a modified version of Aldrich by Matt McInerney, adapted and renamed by Michèle Masson-Trottier. It is licensed under the SIL Open Font License 1.1, as is the original.
- Download
Scirich-Regular.ttf— installable font - Download
Scirich-Regular.sfd— FontForge source, for editing - Upstream: micmas/Scirich-font
If you redistribute it, the OFL requires you to include the full licence, avoid the reserved name “Aldrich”, attribute the original designer, and describe your changes.
When exporting a logo or figure to SVG, convert text to paths so it renders correctly for people who do not have Scirich installed.
Template presentations
Section titled “Template presentations”Slide decks
Section titled “Slide decks”Neurodesk Overview Slides (accessible for the Neurodesk team)
To request access, please email mail.neurodesk@gmail.com.
Poster template
Section titled “Poster template”- Download Neurodesk vertical poster template (.potx)
- Download Neurodesk horizontal poster template (.potx)
Contributing an asset
Section titled “Contributing an asset”To add a figure, diagram, or screenshot to the shared library, see CONTRIBUTING.md in the media repository. In short: use the naming convention, commit a vector master where one exists, keep files under the size limits, and update the folder’s README table.