Compose styles
Rather than blending styles toward a middle, this gives them roles. The first one carries the structure, the next comes in as the accent, and anything after that shows up in a single detail. Where they fight each other, it says so before you start.
How to divide the work
- Composition
- Follow Atlassian Design System: Keep navigation, list and detail roles stable; use token multiples for spacing
- Type
- Set in Atlassian Design System's manner (Fix the steps for headings, body and labels; keep status names short inside lozenges), and let GitHub Primer's lettering (Use one plain sans for body and labels; build hierarchy through weight and color) appear only where you want the eye to catch.
- Material
- Ground in Atlassian Design System's material (Use white and pale gray as the base, blue for primary actions and one semantic meaning per status color); bring in exactly one thing from GitHub Primer (Start from neutrals; reserve blue for links and semantic colors for success, warning and danger).
- Colour
- Build on #FFFFFF, #0C66E4, #172B4D and admit one accent from #F6F8FA, #0969DA, #24292F.
Where they fight
- Atlassian Design System and GitHub Primer both belong to Platform Screen Languages, so the difference is small. Push the roles further apart than feels comfortable.
Caution
- Atlassian Design System Too many cards and status labels give every component equal force and hide the work that matters next.
- GitHub Primer Adding borders and tiny controls to look like GitHub only creates a cramped admin screen when the work has no clear priority.
Image prompt
Produce four original images that take their structure from Atlassian Design System (style, 2012–) and their accent from GitHub Primer (style, 2017–). ## What to make Make the kind of thing Atlassian Design System exists for: work-management products where people move repeatedly between lists and details, or keeping a trusted family resemblance across products without hiding their complexity. Choose one subject and hold it across all four. ## Structure comes from Atlassian Design System - White and pale gray layers with blue primary actions - Rounded cards and lozenge-shaped status labels - Clear divisions among sidebar, table and detail pane - Color, spacing, radius and elevation controlled by tokens Composition: Keep navigation, list and detail roles stable; use token multiples for spacing. Type and lettering: Fix the steps for headings, body and labels; keep status names short inside lozenges. ## Accent comes from GitHub Primer, used sparingly - Neutral surfaces with blue links and restrained status colors - Octicons paired with short action labels - Thin borders separating lists, tabs and sidebars - Consistent steps of type and spacing even at high density Let one material quality come from it: Start from neutrals; reserve blue for links and semantic colors for success, warning and danger. ## Colour and feeling Build the ground on #FFFFFF, carry the structure in #0C66E4 and #172B4D, and let a single accent come from #0969DA. These are read off real works, so a direction rather than a fixed palette. Feeling to carry: trust, technique, intimacy, calm. ## Where they fight - Atlassian Design System and GitHub Primer both belong to Platform Screen Languages, so the difference is small. Push the roles further apart than feels comfortable. ## What goes wrong - Atlassian Design System: Too many cards and status labels give every component equal force and hide the work that matters next. - GitHub Primer: Adding borders and tiny controls to look like GitHub only creates a cramped admin screen when the work has no clear priority. ## Across the four Keep the roles fixed in all four. Vary the framing, the scale and the arrangement so the set shows what this pairing can do rather than four versions of one picture. ## Constraints - Do not imitate, reference or name any specific artist, studio, brand, character or copyrighted work. - Do not reproduce the composition of an existing work. - Produce original compositions in the general period languages described above.
Related entries
- Atlassian Design System 2012– / Style / Platform Screen Languages
A system that translates the complexity of Jira and Confluence into shared tokens, content rules, spacing, grids and components. Consistency builds trust while keeping large sets of issues, documents and states navigable.
- GitHub Primer 2017– / Style / Platform Screen Languages
GitHub's design system for turning dense development workflows into shared rules for color, type, icons, spacing and components. It favors flow over decoration, keeping many states and actions in a small area without giving up accessibility or responsive behavior.
Share this composition:https://indexstyle.org/compose?ids=atlassian-design-system+github-primer