.github

Org-wide defaults for nexlabz. GitHub reads this repo specially — nothing here needs to be wired up.

What's in here

File	What it does
profile/README.md	The public org page. Rendered at github.com/nexlabz.
profile/assets/	The N-mark logo, light and dark variants. Exported from Figma — see below.
CONTRIBUTING.md	Contribution guide, inherited by every public repo without its own.
CODE_OF_CONDUCT.md	Contributor Covenant 2.1.
SECURITY.md	How to report a vulnerability. Drives the Security tab.
SUPPORT.md	Where to ask what. Linked from the new-issue page.
ISSUE_TEMPLATE/	Issue forms — bug, feature, experiment pitch — plus config.yml links.
PULL_REQUEST_TEMPLATE.md	Pre-fills the PR description box.

How inheritance works

A repo uses its own version of any of these if it has one, and falls back to this repo if it doesn't. So override per-repo only where the repo genuinely differs — a shared default that's slightly wrong everywhere is worse than one good default.

Health files here apply to public repos. Private repos don't inherit them.

The logo

profile/assets/nexlabz-mark.svg is the N mark, exported from the Logo / N Mark node in the logo-templates Figma file. It's a mono mark — one fill colour, swapped per surface:

File	Fill	Use on
nexlabz-mark.svg	#0B1020	Light backgrounds
nexlabz-mark-dark.svg	#EFF1F6	Dark backgrounds

Both files carry identical path geometry; only the fill differs. The profile page picks between them with <picture media="(prefers-color-scheme: dark)">, because #0B1020 on GitHub's dark theme measures 1.00:1 contrast — the mark would be completely invisible.

Re-exporting? Keep the intrinsic width/height (93.7898 × 107.116) on the <svg> root and size at the callsite instead, or the mark distorts.

Known artifact: the mark is two abutting paths that meet at x≈46.89 with a 0.003-unit gap, which renders as a faint hairline down the centre above roughly 300px. It's in the Figma source, not the export. To fix it properly, union the two shapes in Figma and re-export.

Editing the profile page

profile/README.md is the first thing anyone sees. Changes go live on push to main — there's no build step and no preview, so read the diff before you merge.

To add a project, add a row to the In the lab table. There's a commented-out example above it with the format. Retire a project by moving it down and switching its status to 🪦 rather than deleting the row — the graveyard is part of the pitch.

Setup checklist

Before pointing people at the org page, replace the placeholders:

• Domain — nexlabz.dev appears in the profile, SECURITY, SUPPORT, and issue config. Swap it for the real one: grep -rl 'nexlabz\.dev' .
• Email — hello@, security@, and conduct@ need to resolve somewhere real.
• X handle — x.com/nexlabz is assumed, not verified.
• Discussions — enabled on this repo, at /nexlabz/.github/discussions. To move them to an org-level page instead, set this repo as the discussion source in org settings, then repoint the links in the profile, SUPPORT, and ISSUE_TEMPLATE/config.yml.
• First project row — replace the placeholder row in the lab table.
• Labels in new repos — issue forms only apply a label that already exists in that repo. needs-triage, experiment, and proposal exist here; recreate them in each new repo, or the forms open unlabelled.
• Org description and avatar — set in org settings; they show above this page.

A private profile page

This repo's profile is public. For a members-only page — internal roadmap, who owns what — create a second repo named .github-private with its own profile/README.md. Members see that one instead when signed in.