Bitmask GitHub organisation profile

Source for the public profile shown at github.com/BitmaskDesign.

How GitHub picks this up

GitHub renders an organisation profile from a public repository named .github, reading the file at profile/README.md. The repository name is fixed; nothing else works.

BitmaskDesign/.github          <- repo name must be exactly ".github", and public
└── profile/
    ├── README.md            <- rendered on github.com/BitmaskDesign
    └── assets/
        ├── banner.png       <- brand banner, 2560x800 (2x)
        └── bitmask-logo.png <- logo lockup, for reuse

Publishing

If BitmaskDesign/.github does not exist yet:

gh repo create BitmaskDesign/.github --public \
  --description "Bitmask organisation profile"

git init
git add .
git commit -m "Add organisation profile"
git branch -M main
git remote add origin git@github.com:BitmaskDesign/.github.git
git push -u origin main

If it already exists, clone it and copy profile/ in.

Anything in this repo other than profile/README.md (this file included) stays invisible on the profile page, so it is a fine place to keep notes and source assets.

Editing notes

• Content is drawn from bitmask.co.uk: the capability list, the expertise sections, product line-up, and contact details. When the site changes, change it here too.
• Image paths in profile/README.md are relative (./assets/…), which GitHub resolves against the profile/ directory. Keep them relative so the banner survives a rename of the org.
• The banner uses the brand green from the logo (#0A7D50), copper (#C89B3C), and IBM Plex Sans / IBM Plex Mono, matching the website. It was rendered from HTML with headless Chrome at 2x. To change it, rebuild at 1280x400 CSS pixels with --force-device-scale-factor=2.
• Shields.io badges are pinned to brand colours where they are ours (0A7D50, C89B3C, 115A40) and to each vendor's own colour where they are not.