# GitHub's 2026 brand guidelines > A landscape brand-guidelines deck combining stark section dividers, annotated identity specifications, color swatches, event photography, bright 3D mascots, and sample editorial layouts within a consistent green-ruled framework. - Kind: Slides - Live deck: https://brand.github.com/GitHub-BrandGuidelines-2026.pdf - Page: https://meetreference.com/v/github-s-2026-brand-guidelines/ - Ready-to-use agent handoff: https://meetreference.com/v/github-s-2026-brand-guidelines/agent.txt - Authorship: Not stated - Made with: Not stated - Model: not stated - Built with: not stated - Style: Decks; editorial grid, minimalist, oversized typography, monochrome, green accents, 3d illustration, brand guidelines - Slides: 89 - Preview: a flip-through of inspected screenshots; open the live work to experience its motion and interactions. - Shared by GitHub in Website, January 2026: https://brand.github.com/GitHub-BrandGuidelines-2026.pdf - Prompt fidelity: Unavailable in this entry. The recreation brief is written by Reference. ## Before you start Guidance from Reference, separate from the creator's instructions. 1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present. 2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized. 3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed. 4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting. 5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use. ## Recreating this deck This is a visual reference. No original creator prompt is available. The following brief was written by Reference after inspecting the work. Build a consistent top metadata strip with segmented labels, page numbers, and a single thin accent rule across light and dark slides. Alternate near-empty section dividers with gridded specification pages, using oversized sans-serif titles and small monospaced annotations to establish contrasting scales. Present imagery in aligned panels and explain applications through swatches, lockups, and annotated examples. For a new subject, replace the brand marks, characters, photography, and color family while preserving the neutral framework and rhythm between sparse and dense pages. 1. Open the live work or source and inspect the frame images below. 2. Adapt its layout, hierarchy, palette, and interaction patterns to the user's own content and brand. 3. Compare the result against the reference. Use your own assets and credit the original creator. ## What it looks like Written by Reference from the captured walkthrough frames, not by the creator. A polished, contemporary GitHub brand-guidelines presentation combining geometric illustrations, playful three-dimensional mascots, interface examples, and event imagery. - Color: White and pale gray foundations with GitHub green, vivid blue, cyan, purple, and magenta accents; some pages use near-black backgrounds with white text. - Type: Clean sans-serif typography, with oversized lightweight section titles, compact navigation and labels, and smaller explanatory text. - Framing: Editorial web-page layouts with generous whitespace, clear headline-and-copy areas, and neatly arranged panels showing color, interface, mascot, and photographic examples. - Structure: A cover introduces the 2026 guidelines, followed by sections on imaginative branding, sub-branding, security, contribution usage, mascots, and layout, ending with contact information. Storyboard of the slides: https://meetreference.com/media/github-s-2026-brand-guidelines/storyboard.webp - Slide 1: https://meetreference.com/media/github-s-2026-brand-guidelines/f1.webp - Slide 12: https://meetreference.com/media/github-s-2026-brand-guidelines/f2.webp - Slide 23: https://meetreference.com/media/github-s-2026-brand-guidelines/f3.webp - Slide 34: https://meetreference.com/media/github-s-2026-brand-guidelines/f4.webp - Slide 45: https://meetreference.com/media/github-s-2026-brand-guidelines/f5.webp - Slide 56: https://meetreference.com/media/github-s-2026-brand-guidelines/f6.webp - Slide 67: https://meetreference.com/media/github-s-2026-brand-guidelines/f7.webp - Slide 78: https://meetreference.com/media/github-s-2026-brand-guidelines/f8.webp - Slide 89: https://meetreference.com/media/github-s-2026-brand-guidelines/f9.webp ## Links - View deck: https://brand.github.com/GitHub-BrandGuidelines-2026.pdf - Original post: https://brand.github.com/GitHub-BrandGuidelines-2026.pdf