{ "site": "aibrandguidelines.org", "lastChecked": "2026-11-11", "about": "The facts behind Annotated Guidelines. `guides` lists the published brand guides quoted on the site. Each record is one quoted excerpt (field `excerpt`, with the part of a guide it belongs to, a note, and `marks`: which of six things that make a rule easy to follow it has, namely exact = an exact value, shown = a do and don't, limits = where it applies, why = a reason, file = the real file, dated = a date), one thing a guide leaves out (field `leaves-out`), or one fact about a guide, an AI tool or Rainbrand. Every record has the address it came from and the day it was checked. Quotes are verbatim and short; follow the source for the full guide.", "guides": [ { "slug": "mailchimp", "name": "Mailchimp", "company": "Mailchimp", "title": "Mailchimp Content Style Guide", "url": "https://styleguide.mailchimp.com/", "format": "Website", "formatShort": "Website", "sector": "Email marketing software", "parts": [ "voice", "words" ], "dateShown": "None. The footer says © 2023", "dateDetail": "No date or version on the pages; the footer says “© Mailchimp 2023.” The linked GitHub repository's latest commit is dated 4 May 2022.", "files": "None. The guide is text, with its source on GitHub", "filesDetail": "None to download; the guide is text. The full source is public on GitHub. For the Freddie mascot it points to Mailchimp's separate brand assets page.", "contact": "No named person or email. The home page says “We welcome any feedback for improving the guide.” and links to the GitHub repository.", "checked": "2026-11-11", "example": true }, { "slug": "gov-uk", "name": "GOV.UK", "company": "Government Digital Service (UK government)", "title": "GOV.UK style guides and writing guidelines", "url": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/", "format": "Website", "formatShort": "Website", "sector": "UK central government publishing", "parts": [ "voice", "words" ], "dateShown": "None on the pages. A dated “What’s new” page lists changes", "dateDetail": "No date on individual pages. A separate “What’s new” page lists changes by month and day; for example, under September 2026, “29 September”: “Updated the ‘Dates’ and ‘Numbers’ entries to make it clear that days in dates should be formatted as numerals, and not written out or formatted as ordinal numbers.”", "files": "None. The guide is text", "filesDetail": "None to download; the guide is text.", "contact": "Every page links to a feedback survey (“Give your feedback”). Government publishers suggest style guide changes through the content help form, which needs a Signon account; technical A to Z changes go to technical-writers@digital.cabinet-office.gov.uk.", "checked": "2026-11-11", "example": true }, { "slug": "microsoft", "name": "Microsoft", "company": "Microsoft", "title": "Microsoft Writing Style Guide", "url": "https://learn.microsoft.com/en-us/style-guide/welcome/", "format": "Website", "formatShort": "Website", "sector": "Software and cloud services", "parts": [ "voice", "words" ], "dateShown": "Each page shows its own “Last updated on” date", "dateDetail": "Each page shows “Last updated on” with its own date, for example “Last updated on 01/08/2025” on the welcome page, 10/18/2022 on the brand voice page, 07/06/2026 on Top 10 tips and 01/15/2026 on the whitelist entry. The welcome page body also says “© 2024 Microsoft. All rights reserved.”", "files": "None. The guide is web pages", "filesDetail": "None to download; the guide is web pages.", "contact": "Welcome page: “We welcome your feedback about the Microsoft Writing Style Guide. Contact us at msstyle@microsoft.com.”", "checked": "2026-11-11", "example": true }, { "slug": "nhs", "name": "NHS", "company": "NHS England", "title": "NHS Identity Guidelines", "url": "https://www.england.nhs.uk/nhsidentity/", "format": "Website", "formatShort": "Website", "sector": "Public health service in England", "parts": [ "positioning", "logo", "colour", "typography", "imagery", "voice", "words", "layout" ], "dateShown": "None on the pages", "dateDetail": "No page dates. The Fonts page says NHS England secured the Frutiger licence \"in December 2024\"; the research it quotes is labelled \"Public research, 2015\". The colour palette FAQ lists changes but gives no date.", "files": "Logo artwork as zip files. The Frutiger font only for NHS organizations that apply", "filesDetail": "Logo artwork templates as zip files on the Downloads page (NHS logo, NHS service logo, NHS organisational logo, NHS primary care logo) and the public and stakeholder research report as a PDF. Frutiger font files only go to NHS organisations in England that apply to NHS England for a sub-licence.", "contact": "Yes. The Contact us page lists an email for each regional communications team and the national brand team (brandteam@nhs.net), and sends trade mark licence requests and misuse reports to the Department of Health and Social Care.", "checked": "2026-11-11", "example": true }, { "slug": "ibm", "name": "IBM", "company": "IBM", "title": "IBM Design Language", "url": "https://www.ibm.com/design/language/", "format": "Website", "formatShort": "Website", "sector": "Enterprise technology and IT services", "parts": [ "positioning", "logo", "colour", "typography", "imagery", "illustration", "layout" ], "dateShown": "Every page says “Last updated 05 November 2026”, and there is a dated change log", "dateDetail": "Every page footer reads \"Last updated 05 November 2026\" (the same date on all 24 pages checked, so it looks like a site build date). A What's new page lists dated releases, the latest \"05 December 2024\".", "files": "IBM Plex fonts, color swatches, and a grid template. Logo files need an IBM ID", "filesDetail": "Public: IBM Plex font files (GitHub releases at github.com/IBM/plex/releases/latest, also Google Fonts and Adobe Fonts), colour swatches as IBM_Colors.zip (.ase and .clr) on GitHub, a 2x Grid video template (.ai), Illustrator starter files for UI icons, app icons, pictograms and three illustration styles, and Figma libraries. Logo files and photography assets need an IBM ID.", "contact": "Yes. The Support page asks IBMers to use the Slack channel #ibm-design-language and outside vendors or agencies to email designlanguage@us.ibm.com; the footer links an inquiry form.", "checked": "2026-11-11", "example": true }, { "slug": "mozilla", "name": "Mozilla", "company": "Mozilla", "title": "Mozilla Brand Guidelines", "url": "https://brand.mozilla.com/", "format": "Website (a Frontify brand portal that needs JavaScript to show its text)", "formatShort": "Website (Frontify portal)", "sector": "Open-source browser maker and internet advocacy organization", "parts": [ "positioning", "logo", "colour", "typography", "imagery", "illustration", "voice", "words", "layout" ], "dateShown": "Each page shows a “Last modified on” date", "dateDetail": "Each page shows a \"Last modified on\" date, for example Voice & Tone \"Last modified on January 5, 2026 at 10:57 PM\", Typography \"April 18, 2026\" and Photography \"June 23, 2026\". The footer says \"©2025 Mozilla\".", "files": "Logos, color swatches, and fonts as zip files. Templates need a Mozilla account", "filesDetail": "Public zip downloads: Mozilla Logo Library.zip (522 KB), mozilla-colors.zip (ASE, LESS and SCSS swatches), mozilla-type-family-main.zip plus separate Mozilla Headline and Mozilla Text zips (fonts also on GitHub at mozilla/mozilla-type-family), an icon library (61 items) and a Pixelgram guide in Figma. Slide, letterhead and other templates in the Brand Starter Pack need a Mozilla account; stock photos need Mozilla SSO.", "contact": "Partly. Every page footer says \"Need help? Contact the brand team.\" but the link leads back to the About page, with no email shown. The Brand Starter Pack points staff to the Slack channel #brand.", "checked": "2026-11-11", "example": true }, { "slug": "spotify", "name": "Spotify", "company": "Spotify", "title": "Design & Branding Guidelines (Spotify for Developers)", "url": "https://developer.spotify.com/documentation/design", "format": "Website", "formatShort": "Website", "sector": "Music and podcast streaming. Rules for outside developers who show Spotify content", "parts": [ "logo", "colour", "typography", "imagery", "words", "layout" ], "dateShown": "None. The logo files have 2024 in their names", "dateDetail": "No date or version on the page; the logo downloads are named 2024-spotify-full-logo.zip and 2024-spotify-logo-icon.zip; footer says © 2026 Spotify AB", "files": "Logo and icon zips in SVG, EPS, PDF, AI, and PNG", "filesDetail": "Full logo zip (27 files) and icon zip (26 files): SVG, EPS, PDF, AI and PNG in green, black and white, with RGB, CMYK and Pantone (PMS C and U) versions. Like icon as SVG and PNG. No font files: it points to system fonts.", "contact": "Not stated. The page ends by pointing to Stack Overflow (tag: Spotify) and the footer links a developer community forum.", "checked": "2026-11-11", "example": true }, { "slug": "atlassian", "name": "Atlassian", "company": "Atlassian", "title": "Atlassian Design System: Content and Logos foundations", "url": "https://atlassian.design/foundations/content", "format": "Website", "formatShort": "Website", "sector": "Team collaboration software (Jira, Confluence, Trello, Loom)", "parts": [ "voice", "words", "logo", "colour", "typography", "illustration", "layout" ], "dateShown": "None", "dateDetail": "No date or version on the guideline pages; footer says © 2026 Atlassian", "files": "Logo zips in SVG and PNG. The brand font is for staff only", "filesDetail": "Logo zips per logo (SVG and PNG, in brand, neutral and inverse colours) on the Logos page. App fonts Atlassian Sans and Atlassian Mono in TTF through Atlassian Mosaic; the brand font Charlie Sans is for signed-in users only.", "contact": "A Contact us page: outside users post in the Atlassian Developer Community forum or use the feedback form on each page; Slack and design critiques are for Atlassians only.", "checked": "2026-11-11", "example": true }, { "slug": "shopify", "name": "Shopify", "company": "Shopify", "title": "App design guidelines: Content (successor to the Polaris content guidelines)", "url": "https://shopify.dev/docs/apps/design/content", "format": "Website, with a Markdown copy of each page (add .md to the URL)", "formatShort": "Website, with Markdown copies", "sector": "Ecommerce platform. Writing rules for apps that run inside the Shopify admin", "parts": [ "voice", "words" ], "dateShown": "None", "dateDetail": "No date, version or copyright year on the content pages", "files": "None. Each page has a Markdown copy", "filesDetail": "None to download; the guide is text. Each page offers a Markdown copy.", "contact": "Not stated on the content pages; each page has a 'Was this page helpful?' Yes/No form.", "checked": "2026-11-11", "example": true }, { "slug": "dropbox", "name": "Dropbox", "company": "Dropbox", "title": "Dropbox Brand Guidelines", "url": "https://brand.dropbox.com/", "format": "Website (brand.dropbox.com), with a separate legal page on using the name and logo at dropbox.com/branding", "formatShort": "Website and a legal page", "sector": "Cloud file storage and sharing", "parts": [ "positioning", "voice", "logo", "colour", "typography", "imagery", "illustration", "words" ], "dateShown": "None", "dateDetail": "No date or version on brand.dropbox.com. The legal branding page says the guidelines 'may be updated periodically' but shows no date.", "files": "A shared folder of partner guidelines and logos", "filesDetail": "A public shared Dropbox folder, 'Brand partner toolkit', holds a 'Dropbox Partner Guidelines' folder and a 'Logos' folder, with a Download button. No font files: the typeface DB Sharp Grotesk is custom.", "contact": "brand@dropbox.com, given on the legal branding page for questions about the guidelines.", "checked": "2026-11-11", "example": true }, { "slug": "github", "name": "GitHub", "company": "GitHub", "title": "GitHub Brand Toolkit", "url": "https://brand.github.com/", "format": "Website, with a downloadable PDF and Figma files", "formatShort": "Website, PDF and Figma files", "sector": "Software development platform", "parts": [ "logo", "colour", "typography", "illustration", "voice", "words", "layout" ], "dateShown": "None on the pages. The PDF has 2026 in its name", "dateDetail": "No date on the web pages; footer says © 2026 GitHub, Inc.; the PDF download is named GitHub-BrandGuidelines-2026.pdf", "files": "A logo zip (SVG, PNG, PDF), the Mona Sans fonts, a PDF, and Figma files", "filesDetail": "Logo ZIP (GitHub_Logos.zip) with SVG, PNG and PDF files, some with clear space built in; Mona Sans and Mona Sans Mono from the github/mona-sans repository; a brand guidelines PDF; the full palette and guidelines in Figma; a PowerPoint template marked for GitHub staff only", "contact": "The logo page says to contact GitHub (links to github.com/contact) about authorised uses; contractors are told to ask their point of contact, and staff the #brand-marketing-design team", "checked": "2026-11-11", "example": true }, { "slug": "experian", "name": "Experian", "company": "Experian", "title": "Experian Brand Central: Generative AI guidelines", "url": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "format": "Website", "formatShort": "Website", "sector": "Credit reporting and data services", "parts": [ "positioning", "logo", "colour", "typography", "imagery", "voice", "ai" ], "dateShown": "None", "dateDetail": "No date or version on the page; footer says ©2026 Experian Technology Ltd.", "files": "None in public. Brand assets need a sign-in", "filesDetail": "None on the public pages. Logos, colour swatches, the Roboto font, images and templates are on the Brand Asset Hub, which needs a sign-in. External logo use needs an approval request.", "contact": "An 'Ask the Brand Team' email link (globalbrand@exchange.experian.com) at the top of the page", "checked": "2026-11-11", "example": true }, { "slug": "arizona-state-university", "name": "Arizona State University", "company": "Arizona State University", "title": "AI guidelines", "url": "https://brandguide.asu.edu/elements-guidelines/ai-guidelines", "format": "Website", "formatShort": "Website", "sector": "Public university", "parts": [ "ai" ], "dateShown": "No date or version; the page says the brand team, Enterprise Technology and the Office of General Counsel will keep updating it", "dateDetail": "No date or version; the page says the brand team, Enterprise Technology and the Office of General Counsel will keep updating it", "files": "None", "filesDetail": "None", "contact": "Not stated", "checked": "2026-11-11", "example": false }, { "slug": "customer-io", "name": "Customer.io", "company": "Customer.io", "title": "AI guidelines", "url": "https://brand.customer.io/docs/ai-usage-guidelines", "format": "Website", "formatShort": "Website", "sector": "Customer messaging software", "parts": [ "ai" ], "dateShown": "No date or version", "dateDetail": "No date or version", "files": "None", "filesDetail": "None", "contact": "Not stated", "checked": "2026-11-11", "example": false }, { "slug": "zeiss", "name": "ZEISS", "company": "ZEISS", "title": "Generative AI (Imagery)", "url": "https://brand.zeiss.com/en/brand-design-elements/imagery/generative-ai", "format": "Website", "formatShort": "Website", "sector": "Optics and optoelectronics manufacturer", "parts": [ "ai" ], "dateShown": "No date or version", "dateDetail": "No date or version", "files": "None", "filesDetail": "None", "contact": "Not stated", "checked": "2026-11-11", "example": false }, { "slug": "care", "name": "CARE", "company": "CARE", "title": "AI guidance for brand standards", "url": "https://brand.care.org/brand-standards/ai-guidance/", "format": "Website", "formatShort": "Website", "sector": "Humanitarian aid organization", "parts": [ "ai" ], "dateShown": "No date on the page; page metadata gives 2026-03-05 as last modified; footer says © 2026", "dateDetail": "No date on the page; page metadata gives 2026-03-05 as last modified; footer says © 2026", "files": "None", "filesDetail": "None", "contact": "Not stated", "checked": "2026-11-11", "example": false }, { "slug": "utah-state-university", "name": "Utah State University", "company": "Utah State University", "title": "AI Branding Guidelines", "url": "https://www.usu.edu/brand/standards/ai/branding-guidelines", "format": "Website", "formatShort": "Website", "sector": "Public university", "parts": [ "ai" ], "dateShown": "No date or version; the page says University Marketing & Communications will review AI policies periodically", "dateDetail": "No date or version; the page says University Marketing & Communications will review AI policies periodically", "files": "None", "filesDetail": "None", "contact": "Not stated", "checked": "2026-11-11", "example": false } ], "records": [ { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "excerpt", "part": "voice", "heading": "Voice", "marks": [ "limits" ], "note": "Each trait comes with the line it must not cross.", "value": "Our sense of humor is straight-faced, subtle, and a touch eccentric. We’re weird but not inappropriate, smart but not snobbish. We prefer winking to shouting.", "source": "https://styleguide.mailchimp.com/voice-and-tone/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "excerpt", "part": "voice", "heading": "Voice", "marks": [ "why" ], "note": "Names two things to cut and says why: readers are there to work.", "value": "Because businesses come to Mailchimp to get to work, we avoid distractions like fluffy metaphors and cheap plays to emotion.", "source": "https://styleguide.mailchimp.com/voice-and-tone/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "excerpt", "part": "voice", "heading": "Tone", "marks": [ "limits" ], "note": "Sets the order when tone and clarity conflict: clarity wins.", "value": "Mailchimp’s tone is usually informal, but it’s always more important to be clear than entertaining. When you’re writing, consider the reader’s state of mind.", "source": "https://styleguide.mailchimp.com/voice-and-tone/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "excerpt", "part": "voice", "heading": "Use plain language", "marks": [ "why", "limits" ], "note": "Shows tone shifting for one kind of content, and how far it shifts.", "value": "Legal content is serious business, so the tone is slightly more formal than most of our content. That said, we want all of our users to be able to understand our legal content.", "source": "https://styleguide.mailchimp.com/writing-legal-content/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "excerpt", "part": "words", "heading": "Active voice", "marks": [ "shown" ], "note": "The same sentence written both ways, so the rule needs no explaining.", "value": "Yes: Marti logged into the account. No: The account was logged into by Marti.", "source": "https://styleguide.mailchimp.com/grammar-and-mechanics/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "excerpt", "part": "words", "heading": "Standardized spellings", "marks": [ "exact" ], "note": "One spelling and two rules a person or a script can check.", "value": "email (never hyphenate, never capitalize unless it begins a sentence)", "source": "https://styleguide.mailchimp.com/word-list/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "excerpt", "part": "words", "heading": "Words to avoid", "marks": [ "exact", "limits" ], "note": "Bans the words and says the one case where they are fine.", "value": "ninja, rockstar, wizard, unicorn (unless referring to a literal ninja, rockstar, wizard, or unicorn)", "source": "https://styleguide.mailchimp.com/word-list/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "excerpt", "part": "words", "heading": "Writing about Mailchimp", "marks": [ "exact" ], "note": "Gives the current spelling of the name and the old one to correct.", "value": "Mailchimp is one word, spelled with a big M and a little c. It used to have a big M and a big C, but the times have changed.", "source": "https://styleguide.mailchimp.com/writing-about-mailchimp/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "leaves-out", "value": "The two voice lists do not agree. The TL;DR page calls the voice human, familiar, friendly, and straightforward. The Voice and Tone page names four other traits.", "source": "https://styleguide.mailchimp.com/tldr/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "leaves-out", "value": "Tone by situation gets one paragraph on the Voice and Tone page, with no example lines for particular situations.", "source": "https://styleguide.mailchimp.com/voice-and-tone/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "license", "value": "Free to use and adapt under Creative Commons Attribution-NonCommercial 4.0. The home page says “All we ask is that you credit Mailchimp.”", "source": "https://styleguide.mailchimp.com/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "audience", "value": "Written for Mailchimp staff and offered to others: “This style guide was created for Mailchimp employees, but we hope it’s helpful for other content and communications teams too.”", "source": "https://styleguide.mailchimp.com/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "source", "value": "The guide's source is public at github.com/mailchimp/content-style-guide; the latest commit is dated 4 May 2022.", "source": "https://github.com/mailchimp/content-style-guide", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "fallback", "value": "For words not on its list it defers to AP style: “If it’s not on this list, defer to the AP Style Guide.”", "source": "https://styleguide.mailchimp.com/word-list/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "summary page", "value": "A TL;DR page puts the most important rules from every section on one page.", "source": "https://styleguide.mailchimp.com/tldr/", "checked": "2026-11-11" }, { "subject": "Mailchimp Content Style Guide", "guide": "mailchimp", "field": "translation", "value": "The translation section overrides the rest of the guide where they conflict: “If you’re writing something to be translated, the guidelines in this section should take precedence.”", "source": "https://styleguide.mailchimp.com/writing-for-translation/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "excerpt", "part": "voice", "heading": "Use the right tone", "marks": [ "limits", "why" ], "note": "Says why friendliness is held back, then sets the opposite limit: still human.", "value": "incisive (friendliness can lead to a lack of precision and unnecessary words) – but remain human (not a faceless machine)", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/writing-guidelines/right-tone/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "excerpt", "part": "voice", "heading": "Use the right tone", "marks": [ "limits" ], "note": "Gives the writer someone to picture, and keeps the casual tone in check.", "value": "Write conversationally. Picture your audience and write as if you were talking to them one-to-one, but with the authority of someone who can actively help.", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/writing-guidelines/right-tone/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "excerpt", "part": "words", "heading": "Know about words to avoid", "marks": [ "exact" ], "note": "Three word swaps a writer or a checker can apply directly.", "value": "Do not use formal or long words when easy or short ones will do. Use ‘buy’ instead of ‘purchase’, ‘help’ instead of ‘assist’, and ‘about’ instead of ‘approximately’.", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/writing-guidelines/clear-language/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "excerpt", "part": "words", "heading": "Words to avoid", "marks": [ "exact", "limits" ], "note": "Gives replacements and says which things can still be delivered.", "value": "deliver, use ‘make’, ‘create’, ‘provide’ or a more specific term (pizzas, post and services are delivered - not abstract concepts like improvements)", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/style-guides/a-to-z-style-guide/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "excerpt", "part": "words", "heading": "Be careful with contractions", "marks": [ "exact", "why" ], "note": "Splits one rule into allowed and banned forms, with the reader problem behind it.", "value": "Use contractions like ‘you’ll’, but avoid negative contractions like ‘can’t’ or ‘don’t’. Many users find negative contractions hard to read, or misread them as the opposite of what they say.", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/writing-guidelines/clear-language/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "excerpt", "part": "words", "heading": "Make requirements clear", "marks": [ "exact", "limits" ], "note": "Picks the word by how serious the requirement is. ‘Must’ and ‘can’ get their own rules.", "value": "If a requirement is legal, but it’s administrative or part of a process that will not have criminal repercussions, then use ‘need’.", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/writing-guidelines/clear-language/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "excerpt", "part": "words", "heading": "Dates", "marks": [ "exact", "shown" ], "note": "Right and wrong forms side by side. The What’s new page dates this change.", "value": "do not use ordinal numbers for the day - for example: 2 June and not 2nd June", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/style-guides/a-to-z-style-guide/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "excerpt", "part": "words", "heading": "What happens next", "marks": [ "dated" ], "note": "Says who decides changes to the guide and how often they meet.", "value": "All suggestions are reviewed once a month by content designers and technical writers at the Government Digital Service (GDS).", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/style-guides/how-to-use/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "leaves-out", "value": "Pages show no last-updated date. To see when a rule changed you have to find it on the separate What’s new page.", "source": "https://guidance.publishing.service.gov.uk/about-the-guidance/whats-new", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "leaves-out", "value": "The A to Z entry for ‘click’ starts with “Don’t”, a negative contraction that the same A to Z’s ‘contractions’ entry says to avoid.", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/style-guides/a-to-z-style-guide/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "moved", "value": "The old addresses (www.gov.uk/guidance/style-guide and its A to Z) now redirect to guidance.publishing.service.gov.uk.", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/style-guides/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "license", "value": "Footer: “All content is available under the Open Government Licence v3.0, except where otherwise stated”", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/style-guides/a-to-z-style-guide/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "scope", "value": "“This style guide applies to all content published on GOV.UK.”", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/style-guides/how-to-use/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "fallback", "value": "If a word is not in the A to Z, it says to check the Guardian style guide, your organisation’s style guide, then other government style guides.", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/style-guides/how-to-use/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "reason for plain English", "value": "Gives literacy data as the reason, for example “1 in 6 adults in England have very poor literacy skills”.", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/writing-guidelines/clear-language/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "length limits", "value": "“Paragraphs should have no more than 5 sentences each.” and “Try to split up sentences that are over 25 words long.”", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/writing-guidelines/clear-language/", "checked": "2026-11-11" }, { "subject": "GOV.UK style guides and writing guidelines", "guide": "gov-uk", "field": "status", "value": "The guidance site is marked “Beta”.", "source": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "excerpt", "part": "voice", "heading": "Three voice principles", "marks": [ "limits" ], "note": "Names the trait, then caps the fun at ‘occasionally’.", "value": "Warm and relaxed—We’re natural. Less formal, more grounded in real, everyday conversations. Occasionally, we’re fun. (We know when to celebrate.)", "source": "https://learn.microsoft.com/en-us/style-guide/brand-voice-above-all-simple-human", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "excerpt", "part": "voice", "heading": "What do we mean by voice?", "marks": [ "limits" ], "note": "Separates fixed voice from changing tone and names the range, but gives no cases.", "value": "Though our voice is constant regardless of who we’re talking to or what we’re saying, we adapt our tone—from serious to empathetic to lighthearted—to fit the context and the customer's state of mind.", "source": "https://learn.microsoft.com/en-us/style-guide/brand-voice-above-all-simple-human", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "excerpt", "part": "voice", "heading": "Write like you speak", "marks": [ "shown" ], "note": "A before and after for an error message. The new message tells the user what to enter.", "value": "Replace this: Invalid ID With this: You need an ID that looks like this: someone@example.com", "source": "https://learn.microsoft.com/en-us/style-guide/top-10-tips-style-voice", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "excerpt", "part": "words", "heading": "click", "marks": [ "exact", "why", "limits" ], "note": "Gives the replacement, the reason, and the one case where the old word is fine.", "value": "Avoid this verb, which is specific to using a mouse. Instead, use verbs that work with multiple devices, such as select. It's OK to use click when you need to describe mouse actions specifically.", "source": "https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/click", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "excerpt", "part": "words", "heading": "whitelist", "marks": [ "exact", "dated" ], "note": "A banned word with two replacements, on a page dated 01/15/2026. No reason given.", "value": "Never use whitelist. Use allow list instead. For more specific usage, safe senders list can be used.", "source": "https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/w/whitelist", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "excerpt", "part": "words", "heading": "Bias-free communication", "marks": [ "exact", "limits" ], "note": "Sets an order: rewrite first, singular ‘they’ second. Bans he/she outright.", "value": "If you can't write around the problem, it's OK to use a plural pronoun (they, their, or them) in generic references to a single person. Don't use constructions like he/she and s/he.", "source": "https://learn.microsoft.com/en-us/style-guide/bias-free-communication", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "excerpt", "part": "words", "heading": "Tips for all global content", "marks": [ "why" ], "note": "The reason counts software as a reader, not only people.", "value": "Include articles, such as the. Articles help readers and translation software identify the nouns and modifiers in a sentence.", "source": "https://learn.microsoft.com/en-us/style-guide/global-communications/writing-tips", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "leaves-out", "value": "The brand voice page lists its three voice principles with no example sentences. The before and after examples are on the separate Top 10 tips page.", "source": "https://learn.microsoft.com/en-us/style-guide/brand-voice-above-all-simple-human", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "leaves-out", "value": "The brand voice page says tone moves from serious to lighthearted but does not say which tone fits which situation.", "source": "https://learn.microsoft.com/en-us/style-guide/brand-voice-above-all-simple-human", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "license", "value": "No open licence stated. The welcome page says “© 2024 Microsoft. All rights reserved.”", "source": "https://learn.microsoft.com/en-us/style-guide/welcome/", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "audience", "value": "“If you write about computer technology, this guide is for you.”", "source": "https://learn.microsoft.com/en-us/style-guide/welcome/", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "voice in one line", "value": "The welcome page sums up the voice as “warm and relaxed, crisp and clear, and ready to lend a hand.”", "source": "https://learn.microsoft.com/en-us/style-guide/welcome/", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "page dates", "value": "Dates differ by page: bias-free communication 04/18/2024, global writing tips 06/14/2023, use simple words 06/24/2022, click entry 06/24/2022.", "source": "https://learn.microsoft.com/en-us/style-guide/bias-free-communication", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "images", "value": "The bias-free page also covers pictures: “In text and images, represent diverse perspectives and circumstances.”", "source": "https://learn.microsoft.com/en-us/style-guide/bias-free-communication", "checked": "2026-11-11" }, { "subject": "Microsoft Writing Style Guide", "guide": "microsoft", "field": "machine translation", "value": "Asks for one term per concept: “Use one word for a concept, and use it consistently.”", "source": "https://learn.microsoft.com/en-us/style-guide/global-communications/writing-tips", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "excerpt", "part": "voice", "heading": "Tone of voice", "marks": [ "exact", "limits" ], "note": "Gives a test a writer can run: read it aloud as if to one person.", "value": "If you are writing to patients and the public, make sure your style is both personal and direct. Your written communication should be capable of being spoken out loud and sound as if it is being addressed to an individual.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/tone-of-voice/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "excerpt", "part": "logo", "heading": "Minimum clear space limit for digital", "marks": [ "exact", "limits" ], "note": "Sets a smaller clear space for screens than for print, measured in logo heights so it scales.", "value": "For digital applications, the exclusion area is equivalent to half the height of the NHS logo. This area must always be kept clear.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/nhs-logo/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "excerpt", "part": "logo", "heading": "White out of colours other than NHS Blue", "marks": [ "shown", "why" ], "note": "States the rule and the reason, beside pictures of acceptable and unacceptable backgrounds.", "value": "The NHS logo cannot be reversed out of any colour other than NHS Blue. This is because NHS Blue is the colour that the public expect, and recognise, to represent the NHS.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/nhs-logo/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "excerpt", "part": "colour", "heading": "NHS Blue", "marks": [ "exact" ], "note": "One color in five systems, with RAL for paint and signs. On the page, the values are on separate lines.", "value": "Pantone: 300 CMYK: 99/50/0/0 RGB: 0/94/184 #005EB8 RAL: 5017", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/colours/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "excerpt", "part": "colour", "heading": "Colours", "marks": [ "why" ], "note": "Grounds the blue and white rule in a survey figure rather than taste.", "value": "Our research shows that patients and the public strongly associate the NHS with the colours blue and white. 87% of people spontaneously recall these two colours when asked about the NHS Identity.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/colours/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "excerpt", "part": "typography", "heading": "Fonts", "marks": [ "exact", "limits" ], "note": "Names both fonts and closes the special-audience exception before anyone asks for it.", "value": "The core NHS font is Frutiger and the secondary font is Arial. These fonts should be used for all NHS communications. No other fonts should be used, even if your NHS communications are aimed at a specific target audience (e.g. children).", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/fonts/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "excerpt", "part": "imagery", "heading": "Imagery", "marks": [ "exact" ], "note": "Says who to photograph and adds the consent step, but the page shows no example photos.", "value": "Where possible, photography should feature real NHS patients and staff. Ensure the appropriate consent is obtained and records are kept.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/imagery/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "excerpt", "part": "layout", "heading": "3. Size and positioning", "marks": [ "limits", "exact" ], "note": "Covers the formats the size table leaves out, with a worked example.", "value": "Any other formats should be sized proportionally, or should replicate the size and margin of the closest format shown here. For example, a square A4 format (210mm x 210mm) should use the size and margin guidelines for A4.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/nhs-logo/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "leaves-out", "value": "The Tone of voice and Imagery pages have no example sentences or example photos. They are short lists of rules.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/tone-of-voice/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "leaves-out", "value": "No guidance on using AI: the site search returns no results for \"AI\" or \"artificial intelligence\".", "source": "https://www.england.nhs.uk/nhsidentity/?s=artificial+intelligence", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "owner", "value": "The footer says NHS England manages and develops the NHS Identity on behalf of the Department of Health.", "source": "https://www.england.nhs.uk/nhsidentity/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "license", "value": "The footer links the Open Government Licence v3.0.", "source": "https://www.england.nhs.uk/nhsidentity/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "trade mark", "value": "The NHS logo is a UK trade mark owned by the Secretary of State for Health and Social Care, and the guide says not to recreate it: only original artwork files should be used.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/nhs-logo/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "logo clear space, print", "value": "Equal to the full height of the NHS logo; for digital, half the height.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/nhs-logo/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "logo minimum size", "value": "30px high in digital applications; favicons can be as small as 15px square.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/nhs-logo/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "logo size and margin by format", "value": "A4 10mm, A3 15mm, A2 20mm, A5 and A6 8mm, business card 7mm. Desktop logo 40px high with 30px margin, tablet 35px and 20px, mobile 30px and 15px. Logo sits top right except in digital.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/nhs-logo/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "colour palette", "value": "NHS Blue (Pantone 300, #005EB8) and white dominate, then four levels in decreasing emphasis: NHS blues, neutrals, support greens, highlights. The page says all palette colours offer at least an AA accessibility rating.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/colours/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "tints", "value": "Type and NHS logos always in 100% solid colour; the logo is only reversed out of 100% NHS Blue, never a tint.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/colours/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "fonts", "value": "Frutiger 65 Bold for titles, 55 Roman for body copy, 45 Light for large titling; Arial when Frutiger is not available. Frutiger Italic and app use of 45 Light need a separate licence.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/fonts/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "font files", "value": "NHS organisations in England apply to NHS England to become sub-licence holders; the page links the NHS Digital Service Manual page on the NHS Frutiger font.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/fonts/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "naming", "value": "Names are written out in full, without acronyms, abbreviations or symbols such as '&', except St for Saint and NHS for National Health Service.", "source": "https://www.england.nhs.uk/nhsidentity/identity-guidelines/naming-principles/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "principles", "value": "Six principles; Principle 1 says the interests and needs of patients and the public should always be considered first.", "source": "https://www.england.nhs.uk/nhsidentity/nhs-identity-principles/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "research", "value": "98% prompted awareness of the NHS lozenge and 87% spontaneous awareness of the blue and white colours (public research, 2015).", "source": "https://www.england.nhs.uk/nhsidentity/why-its-important/", "checked": "2026-11-11" }, { "subject": "NHS Identity Guidelines", "guide": "nhs", "field": "access", "value": "The site sits behind an AWS bot challenge: a plain curl gets an empty 202 response; a headless browser gets the page.", "source": "https://www.england.nhs.uk/nhsidentity/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "excerpt", "part": "logo", "heading": "Clear space", "marks": [ "exact" ], "note": "Clear space equals the logo's own height, which anyone can measure.", "value": "Keep the logo separated from other visual elements by a distance equal to its height. This distance is considered the minimum uninterrupted space surrounding the logo.", "source": "https://www.ibm.com/design/language/ibm-logos/8-bar/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "excerpt", "part": "colour", "heading": "Specifications", "marks": [ "exact" ], "note": "Says which values are for screens and which are for print.", "value": "Each of the 10-color families have been divided into 10 swatches ranging from light to dark. RGB and HEX values are provided for digital applications along with Pantone® and CMYK values for print.", "source": "https://www.ibm.com/design/language/color/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "excerpt", "part": "colour", "heading": "Combinations to avoid", "marks": [ "limits" ], "note": "Bans certain pairings and names the one use where they are still allowed.", "value": "The following color combinations have been eliminated from the color families and should be avoided unless required for specific applications, such as data visualization.", "source": "https://www.ibm.com/design/language/color/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "excerpt", "part": "typography", "heading": "Where else to get Plex®", "marks": [ "file", "why" ], "note": "Names the source for current font files and why the other copies can lag.", "value": "However, the fonts in these libraries may not have the latest versions, so we always recommend going to the IBM Plex GitHub repo.", "source": "https://www.ibm.com/design/language/typography/typeface/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "excerpt", "part": "typography", "heading": "Case", "marks": [ "exact", "limits" ], "note": "A default, the named exceptions and what to avoid, in three sentences.", "value": "Write content in sentence case. Title case can be used in proper titles, product names and service names. Avoid the use of all uppercase or “all caps” in your typography, especially for paragraphs or text.", "source": "https://www.ibm.com/design/language/typography/type-basics/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "excerpt", "part": "imagery", "heading": "Depth-of-field", "marks": [ "why", "shown" ], "note": "Rule and reason together, with a photo to avoid shown beside it.", "value": "Everything should be in sharp focus. This crisp approach reinforces a deep interest in everything, and an emphasis on context and detail.", "source": "https://www.ibm.com/design/language/photography/tips-and-techniques/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "excerpt", "part": "illustration", "heading": "Strokes", "marks": [ "exact", "limits" ], "note": "Gives the stroke width and says exactly when it can be different.", "value": "Use a 2px stroke for all icons to maintain uniformity. Exceptions may be made only for more complex icons or those with unusually dense line work.", "source": "https://www.ibm.com/design/language/iconography/ui-icons/design/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "excerpt", "part": "layout", "heading": "Spatial relationships", "marks": [ "exact" ], "note": "A closed list of spacing multiples that a person or a tool can check.", "value": "All spacing between elements can be defined by the base unit. Use the following multiples of your base unit to construct your layout: 1x, 2x, 3x, 4x, 6x, 8x, 10x, 12x.", "source": "https://www.ibm.com/design/language/2x-grid/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "leaves-out", "value": "No voice, tone or writing guidance. The FAQ says brand definition and high-level guidance sit in the separate IBM Brand Center.", "source": "https://www.ibm.com/design/language/help/faq/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "leaves-out", "value": "Logo files are not public: the logo request links on the 8-bar page say \"(IBM ID required)\".", "source": "https://www.ibm.com/design/language/ibm-logos/8-bar/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "font", "value": "IBM Plex is the corporate typeface: four subfamilies (Sans, Mono, Serif, Condensed), eight weights, roman and italic.", "source": "https://www.ibm.com/design/language/typography/typeface/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "font files", "value": "Download from github.com/IBM/plex/releases/latest; also on Google Fonts and Adobe Fonts, which the page says may not have the latest versions. The page says the Open Font License (OFL) is in the downloadable font files.", "source": "https://www.ibm.com/design/language/typography/typeface/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "colour file", "value": "IBM color palette (.ase and .clr) links to IBM_Colors.zip in the carbon-design-system/carbon GitHub repository.", "source": "https://www.ibm.com/design/language/color/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "colour values", "value": "Ten colour families of ten grades each; for example Blue 60 is 0f62fe and Blue 70 is 0043ce in the HEX table.", "source": "https://www.ibm.com/design/language/color/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "logo colour contrast", "value": "Use a minimum of five \"steps\" between foreground and background colour for the 8-bar logo, and only blue and gray family colours on the logo.", "source": "https://www.ibm.com/design/language/ibm-logos/8-bar/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "logo history", "value": "Designed by Paul Rand; the basic design has remained unchanged since 1972.", "source": "https://www.ibm.com/design/language/ibm-logos/8-bar/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "icon grid", "value": "UI icons are drawn on a 32px x 32px grid with 2px padding, 2px stroke and 2px corner radius.", "source": "https://www.ibm.com/design/language/iconography/ui-icons/design/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "grid", "value": "The 2x Grid divides space into 2, 4, 8, 16, 32 or 64 columns; the 8px mini unit is used for software and web.", "source": "https://www.ibm.com/design/language/2x-grid/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "source", "value": "Each page has an \"Edit this page on GitHub\" link to its source in the carbon-design-system/design-language-website repository.", "source": "https://www.ibm.com/design/language/typography/typeface/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "change log", "value": "The What's new page says it lists all major updates, changes, rollouts and release dates.", "source": "https://www.ibm.com/design/language/whats-new/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "positioning", "value": "The Principles page offers questions as tests, for example: \"If you covered up our logo or name, would you identify an execution as being designed by IBM?\"", "source": "https://www.ibm.com/design/language/philosophy/principles/", "checked": "2026-11-11" }, { "subject": "IBM Design Language", "guide": "ibm", "field": "access", "value": "Pages are server-rendered: a plain curl returns the full guideline text.", "source": "https://www.ibm.com/design/language/", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "excerpt", "part": "positioning", "heading": "Promise", "marks": [ "exact", "limits" ], "note": "Gives the exact sign-off line and says where it works best.", "value": "Our brand promise can be used in external materials, but it works most effectively as a sign off “Reclaim the internet with us”", "source": "https://brand.mozilla.com/document/240#/-/who-we-are", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "excerpt", "part": "voice", "heading": "Welcoming", "marks": [ "limits", "why" ], "note": "Says what humor is for, and sets a clear limit on who it can target.", "value": "We may use humor to capture attention and aid understanding, but we never punch down.", "source": "https://brand.mozilla.com/document/240#/-/voice-tone", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "excerpt", "part": "words", "heading": "Language preferences", "marks": [ "exact" ], "note": "A single word swap with the capitalisation settled too, easy for a person or tool to check.", "value": "Use “internet” instead of “web” (and no need to capitalize “internet”)", "source": "https://brand.mozilla.com/document/240#/-/voice-tone", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "excerpt", "part": "logo", "heading": "Clearspace and sizing", "marks": [ "exact", "limits" ], "note": "Clear space is measured from a letter in the wordmark, with a separate version for small sizes.", "value": "Maintain adequate space around the lockup using “x” as your guide — where “x” equals the height of the lowercase “z” in Mozilla. For sizes 48px and smaller, use our specially optimized small-scale version.", "source": "https://brand.mozilla.com/document/231#/-/logos", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "excerpt", "part": "colour", "heading": "Usage", "marks": [ "exact" ], "note": "Gives proportions as percentages, not only a list of colors.", "value": "Use mostly Black and White, with a pop of Green (approximately 45% Black, 45% White and 10% Green)", "source": "https://brand.mozilla.com/document/231#/-/color", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "excerpt", "part": "typography", "heading": "Spacing and alignment", "marks": [ "exact" ], "note": "Line spacing as a percentage for each level of text.", "value": "Line spacing: XL headlines and headlines (90%), subheads (110%), body (125%), small body (140%)", "source": "https://brand.mozilla.com/document/231#/-/typography-1", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "excerpt", "part": "imagery", "heading": "Principles", "marks": [ "limits" ], "note": "Says what the trait does not require as well as what it does.", "value": "Optimistic: Images depicting positive interactions between people and tech. People don’t necessarily have to be smiling, but body language should indicate ease, familiarity or camaraderie, regardless if it's one person or a small group being shown.", "source": "https://brand.mozilla.com/document/231#/-/photography", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "excerpt", "part": "illustration", "heading": "Building", "marks": [ "exact", "why" ], "note": "Grid size and stroke weight, with the reason for both.", "value": "New icons should be designed on a 16×16 grid, using a 1.5pt stroke. This ensures scalability across different sizes and resolutions.", "source": "https://brand.mozilla.com/document/231#/-/icons", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "leaves-out", "value": "The guide needs JavaScript: a plain fetch of brand.mozilla.com returns only the title \"Mozilla Brand\", so a tool without a browser sees none of the rules.", "source": "https://brand.mozilla.com/", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "leaves-out", "value": "The templates are not open to outsiders: the slide and letterhead templates open from a Mozilla Google account, and stock photos need Mozilla SSO.", "source": "https://brand.mozilla.com/document/241#/-/brand-starter-pack", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "address", "value": "brand.mozilla.org redirects to brand.mozilla.com. mozilla.design shows a \"Mozilla Brand Portal\" page linking to the Mozilla, Mozilla Foundation and Firefox brand guidelines; a plain curl of mozilla.design is blocked by a Cloudflare page.", "source": "https://mozilla.design/", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "fonts", "value": "Mozilla Headline (display, 24pt and up) and Mozilla Text (body copy); the guide says the type family is open source. Zilla Slab is not mentioned on the Typography page.", "source": "https://brand.mozilla.com/document/231#/-/typography-1", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "type sizes", "value": "XL headlines Mozilla Headline 61pt+, headlines 24pt+, subheads Mozilla Text 19pt-23pt, body 13pt-18pt, small body 10pt-12pt; left alignment and sentence case for all text.", "source": "https://brand.mozilla.com/document/231#/-/typography-1", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "colour values", "value": "Green is RGB 0, 210, 48, #00D230, CMYK 66, 0, 90, 0, PMS 2270 C. Black is #161616 and Strong black #000000.", "source": "https://brand.mozilla.com/document/231#/-/color", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "colour contrast", "value": "Accessible pairs are listed with WCAG and APCA scores, for example Strong Black on White \"WCAG AAA: 20.1:1\" and \"APCA: 103.0\".", "source": "https://brand.mozilla.com/document/231#/-/color", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "tertiary colours", "value": "The tertiary palette of 16 colours is for data visualisation only, not brand communications.", "source": "https://brand.mozilla.com/document/231#/-/color", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "logo minimum size", "value": "Primary lockup: digital 20px height, print 0.15\" / 3.8mm. Wordmark: digital 12px, print 0.10\" / 2.4mm.", "source": "https://brand.mozilla.com/document/231#/-/logos", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "logo placement", "value": "Logos are anchored to a corner; the primary lockup prefers top and bottom-right corners.", "source": "https://brand.mozilla.com/document/231#/-/logos", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "tone by situation", "value": "\"How we adapt our voice\" splits writing into Governments (\"more serious for a professional audience\") and Grassroots (\"more expressive for a dynamic community\").", "source": "https://brand.mozilla.com/document/240#/-/voice-tone", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "style rules", "value": "Sentence case for most things, including headlines, subheadings, CTAs and buttons; avoid the Oxford comma unless needed for clarity; dates as YYYY-MM-DD; American English spelling.", "source": "https://brand.mozilla.com/document/240#/-/voice-tone", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "voice checklist", "value": "A five-question checklist to run before publishing, and an accessibility checklist with an example sentence for each item.", "source": "https://brand.mozilla.com/document/240#/-/voice-tone", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "positioning", "value": "\"Mozilla is the people’s platform, where everyone can control their internet.\"", "source": "https://brand.mozilla.com/document/240#/-/who-we-are", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "audiences", "value": "Key audiences named: developers, users, policymakers and communities.", "source": "https://brand.mozilla.com/document/241#/-/about-mozilla-s-brand", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "accessibility page", "value": "A separate Accessibility page covers typography, colour, language, alt text (125 characters or less), video, touch targets (minimum 44×44 pixels), testing and data visualisation.", "source": "https://brand.mozilla.com/document/241#/-/accessibility", "checked": "2026-11-11" }, { "subject": "Mozilla Brand Guidelines", "guide": "mozilla", "field": "AI", "value": "None of the 11 guideline pages checked gives rules for using AI; the only mention is \"explaining our point of view on AI\" in the voice traits.", "source": "https://brand.mozilla.com/document/240#/-/voice-tone", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "excerpt", "part": "logo", "heading": "Attribute with the Spotify logo", "marks": [ "why" ], "note": "Gives the reason the logo is required: licensing, not taste.", "value": "To comply with our licensing agreements, you must always attribute content from Spotify with the logo.", "source": "https://developer.spotify.com/documentation/design#attribution", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "excerpt", "part": "logo", "heading": "Using our logo", "marks": [ "file" ], "note": "Download buttons for the full logo and icon sit right below, as zips of SVG, EPS, PDF, AI and PNG.", "value": "Our full logo is the combination of our logo icon and the wordmark.", "source": "https://developer.spotify.com/documentation/design#using-our-logo", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "excerpt", "part": "logo", "heading": "Using the icon", "marks": [ "limits" ], "note": "Says which part can stand alone and which never can.", "value": "While the icon can exist without the wordmark, the wordmark should never exist without the icon.", "source": "https://developer.spotify.com/documentation/design#using-our-logo", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "excerpt", "part": "logo", "heading": "Legibility", "marks": [ "exact" ], "note": "Clear space is a ratio of the icon, so it holds at any size.", "value": "The exclusion zone is equal to half the height of the icon (marked as × in the diagram).", "source": "https://developer.spotify.com/documentation/design#using-our-logo", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "excerpt", "part": "logo", "heading": "Minimum size", "marks": [ "exact" ], "note": "One limit for screens, one for print. The icon gets its own: 21px or 6mm.", "value": "The Spotify logo should never be smaller than 70px in digital or 20mm in print.", "source": "https://developer.spotify.com/documentation/design#using-our-logo", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "excerpt", "part": "logo", "heading": "Logo misuse", "marks": [ "shown" ], "note": "One of six don'ts, each with a picture of the mistake.", "value": "Don't place the logo in a busy area, or in low-contrast areas where legibility is compromised", "source": "https://developer.spotify.com/documentation/design#using-our-logo", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "excerpt", "part": "colour", "heading": "Playing views", "marks": [ "exact" ], "note": "The only color code in the page text. The palette image gives black as #121212 instead.", "value": "Extract artwork color for background (Android Palette). If not possible, use Spotify color #191414.", "source": "https://developer.spotify.com/documentation/design#playing-views", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "excerpt", "part": "words", "heading": "How to link to Spotify", "marks": [ "exact" ], "note": "Lists the exact link labels allowed, plus GET SPOTIFY FREE when the app is missing.", "value": "If the Spotify app is installed then use any of the following text strings: OPEN SPOTIFY, PLAY ON SPOTIFY or LISTEN ON SPOTIFY", "source": "https://developer.spotify.com/documentation/design#linking-to-spotify", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "leaves-out", "value": "Spotify Green's HEX, RGB and CMYK values appear only inside an image with empty alt text, so a reader or agent working from text gets no values.", "source": "https://developer.spotify.com/documentation/design#using-our-colors", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "leaves-out", "value": "No voice and tone guidance. The only set wording is link labels, like-button messages, and one upgrade message.", "source": "https://developer.spotify.com/documentation/design", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "colourValues", "value": "The palette image (colors.svg, alt text empty) shows Green HEX #1ED760, RGB 30/215/96, CMYK 86/0/80/0; White #FFFFFF; Black #121212, RGB 18/18/18. No Pantone value is shown.", "source": "https://developer-assets.spotifycdn.com/images/guidelines/design/colors.svg", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "logoColour", "value": "Green logo only on black or white backgrounds; black logo on light backgrounds; white logo on dark backgrounds; otherwise a monochrome logo.", "source": "https://developer.spotify.com/documentation/design#using-our-logo", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "fonts", "value": "No brand font for developers. It recommends the platform's default sans-serif, then Helvetica Neue, Helvetica, Arial.", "source": "https://developer.spotify.com/documentation/design#fonts", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "artwork", "value": "Album artwork must not be cropped, overlaid or distorted; corners rounded 4px on small and medium devices, 8px on large ones.", "source": "https://developer.spotify.com/documentation/design#using-our-content", "checked": "2026-11-11" }, { "subject": "Design & Branding Guidelines (Spotify for Developers)", "guide": "spotify", "field": "terms", "value": "Using the resources means accepting the Spotify Developer Terms of Service.", "source": "https://developer.spotify.com/documentation/design#introduction", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "excerpt", "part": "voice", "heading": "Delight with unexpectedly pleasing experiences", "marks": [ "limits" ], "note": "Says what delight is not, so nobody reads it as permission to joke.", "value": "Delight means little flourishes, not humor or being cheeky.", "source": "https://atlassian.design/foundations/content/voice-tone", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "excerpt", "part": "voice", "heading": "Delight with unexpectedly pleasing experiences", "marks": [ "why" ], "note": "Gives the reason to hold back: repeated messages wear thin.", "value": "Think about the timing and how frequently a user will see this. Once may amuse, but a dozen times may annoy.", "source": "https://atlassian.design/foundations/content/voice-tone", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "excerpt", "part": "voice", "heading": "When to be less bold", "marks": [ "limits" ], "note": "Ties each trait to the reader's mood, with a list of when to turn it down.", "value": "Person is feeling: apprehension, confusion, annoyance, fear, anger.", "source": "https://atlassian.design/foundations/content/voice-tone", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "excerpt", "part": "words", "heading": "UI elements", "marks": [ "exact", "why", "shown" ], "note": "Names the word to use, says why, and pairs it with a do and a do not.", "value": "Avoid using a > symbol where possible, as it is read out as “greater than” by assistive technologies, leading to confusion. Use ‘then’ instead.", "source": "https://atlassian.design/foundations/content/language-and-grammar#ui-elements", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "excerpt", "part": "words", "heading": "Abbreviations", "marks": [ "exact", "why" ], "note": "Lists the banned forms by name and gives two reasons: translation and screen readers.", "value": "Don’t use 'e.g.', ‘i.e.’, ‘etc.’, or '&' as they're not localization friendly and can be confusing for users of assistive technologies.", "source": "https://atlassian.design/foundations/content/language-and-grammar#abbreviations", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "excerpt", "part": "logo", "heading": "Atlassian app strapline", "marks": [ "exact" ], "note": "A minimum width in pixels that anyone can check.", "value": "Always centre the app names under the logo and don’t scale the logo below 280px wide.", "source": "https://atlassian.design/foundations/logos", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "excerpt", "part": "logo", "heading": "Minimum clearance — Atlassian logo", "marks": [ "exact" ], "note": "Clear space measured from a letter in the logo itself, so it scales with the logo.", "value": "Use the capital \"A\" of the Atlassian wordmark to define the minimum clearance around the logo.", "source": "https://atlassian.design/foundations/logos", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "excerpt", "part": "logo", "heading": "Download the logos", "marks": [ "file" ], "note": "Each logo downloads as a zip of SVG and PNG files, not a picture on the page.", "value": "Each downloadable file includes variations of color and layout in approved formats and the below elements combined together:", "source": "https://atlassian.design/foundations/logos", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "leaves-out", "value": "The voice page covers only interface text. The voice guidance for marketing is a link to Brand Voice and Tone (Atlassians only).", "source": "https://atlassian.design/foundations/content/voice-tone", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "leaves-out", "value": "The word list and glossary are internal: the style page points to go/vocab (Atlassians only).", "source": "https://atlassian.design/foundations/content/language-and-grammar", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "voiceTraits", "value": "Three traits: Bold, Optimistic, Practical with a wink; each has 'when to be more' and 'when to be less' lists.", "source": "https://atlassian.design/foundations/content/voice-tone", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "spelling", "value": "US English in interface text and code, checked against Merriam-Webster; shown with color, organization, labeled versus colour, organisation, labelled.", "source": "https://atlassian.design/foundations/content/language-and-grammar#spelling-words", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "brandFont", "value": "Brand font Charlie Sans is for marketing; only authenticated users can download it. App fonts are Atlassian Sans and Atlassian Mono, in TTF through Atlassian Mosaic.", "source": "https://atlassian.design/foundations/typography", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "colourContrast", "value": "Colour page sets contrast to the Web Content Accessibility Guidelines (WCAG) AA level: 3:1 for essential interface parts and text 24px or larger, 4.5:1 for smaller text. Values come from design tokens.", "source": "https://atlassian.design/foundations/color", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "logoMisuse", "value": "Logo don'ts: unapproved colour combinations, drop shadows, complex backgrounds, outlines; logos come in Brand, inverse and neutral colour options.", "source": "https://atlassian.design/foundations/logos", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "brandKit", "value": "The footer's Brand kit link opens Atlassian Mosaic, which shows a login form; it lists an Atlassian Brand Book there. Not checked behind the login.", "source": "https://orangedam.atlassian.com/", "checked": "2026-11-11" }, { "subject": "Atlassian Design System: Content and Logos foundations", "guide": "atlassian", "field": "agentFiles", "value": "The site publishes llms.txt and llms-content.txt, a plain-text copy of the content standards for AI tools.", "source": "https://atlassian.design/llms-content.txt", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "excerpt", "part": "voice", "heading": "Be real, but not too tough or overly familiar", "marks": [ "limits" ], "note": "Each voice trait is paired with the ways it goes too far, here and in the heading.", "value": "Use business casual language. Be plain-spoken, not pretentious or overly playful.", "source": "https://shopify.dev/docs/apps/design/content/voice-and-tone", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "excerpt", "part": "voice", "heading": "Adapting your tone to the situation", "marks": [ "why" ], "note": "Explains why tone follows the situation, not guessed feelings, then covers eight situations.", "value": "In reality you never know a merchant’s emotional state. Even when things seem the most positive, you can’t be sure.", "source": "https://shopify.dev/docs/apps/design/content/voice-and-tone", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "excerpt", "part": "voice", "heading": "Acknowledging effort, progress, or completion", "marks": [ "shown", "why" ], "note": "A do not, with the wrong sentence written out and the reason that it does not work.", "value": "Assume merchants are excited or celebrating. They might be annoyed if the process was long or the benefits aren’t clear, such as “Congrats! You set up your single login for Shopify.”", "source": "https://shopify.dev/docs/apps/design/content/voice-and-tone", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "excerpt", "part": "words", "heading": "Be dynamic, but not scattered or impulsive", "marks": [ "exact" ], "note": "Names the words to avoid instead of describing a quality.", "value": "Avoid words that generalize success, such as “every,” “all,” and “most.”", "source": "https://shopify.dev/docs/apps/design/content/voice-and-tone", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "excerpt", "part": "words", "heading": "Use plain language", "marks": [ "exact" ], "note": "Turns 'plain language' into a reading level someone can measure.", "value": "Use clear terms that are easily understood. As a benchmark, aim for a United States grade 7 reading level.", "source": "https://shopify.dev/docs/apps/design/content", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "excerpt", "part": "words", "heading": "Ampersands", "marks": [ "exact", "why", "shown" ], "note": "Rule, reason and fix in three sentences, then 'Zones and rates' against 'Zones & rates'.", "value": "Don’t use ampersands. They attract attention to the least important part of the sentence. Spell out the word “and.”", "source": "https://shopify.dev/docs/apps/design/content/grammar-and-mechanics#ampersands", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "excerpt", "part": "words", "heading": "Exclamation marks", "marks": [ "exact", "shown" ], "note": "Sets a limit that you can count, one per page, with a do and a do not.", "value": "Avoid exclamation marks. Use them only for genuinely exciting things, and limit yourself to one exclamation mark per page.", "source": "https://shopify.dev/docs/apps/design/content/grammar-and-mechanics#exclamation-marks", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "excerpt", "part": "words", "heading": "Links", "marks": [ "why" ], "note": "Gives the reason before the rules, including never using 'click here' as link text.", "value": "Avoid links where you can. Links add clutter and make your app feel less like software and more like an old-fashioned webpage.", "source": "https://shopify.dev/docs/apps/design/content/grammar-and-mechanics#links", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "leaves-out", "value": "No logo, color, or typography rules here. The pages cover only how app text reads.", "source": "https://shopify.dev/docs/apps/design/content", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "leaves-out", "value": "No positioning statement. The nearest is one line under the Shopify voice about a company 'built by real people'.", "source": "https://shopify.dev/docs/apps/design/content/voice-and-tone", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "polarisRedirect", "value": "polaris.shopify.com and polaris-react.shopify.com, including /content/voice-and-tone, now redirect to the Polaris web components reference at shopify.dev/docs/api/polaris. The content guidance now sits in Shopify's app design guidelines.", "source": "https://shopify.dev/docs/api/polaris", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "spelling", "value": "American English and American spelling for merchant-facing text, checked against Merriam-Webster; shown with Color, Center, Canceled against Colour, Centre, Cancelled.", "source": "https://shopify.dev/docs/apps/design/content/grammar-and-mechanics#spelling", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "voiceTraits", "value": "Four voice guidelines, each named with its limits: be real, proactive, dynamic, and guide without handholding.", "source": "https://shopify.dev/docs/apps/design/content/voice-and-tone", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "errorWords", "value": "As a don't for simple errors it lists words to avoid: bad request, forbidden, fatal, expectation failed, unresolved, invalid.", "source": "https://shopify.dev/docs/apps/design/content/voice-and-tone", "checked": "2026-11-11" }, { "subject": "App design guidelines: Content (successor to the Polaris content guidelines)", "guide": "shopify", "field": "spellingSpecialCases", "value": "Never hyphenate 'ecommerce' and 'email'.", "source": "https://shopify.dev/docs/apps/design/content/grammar-and-mechanics#hyphens", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "excerpt", "part": "positioning", "heading": "Our design strategy prompts humanity, clarity, action, & delight", "marks": [ "limits" ], "note": "Says what clarity is not before saying what it is.", "value": "Clarity isn’t simply about reduction. It’s about surfacing what matters, cutting out what doesn’t, and reducing complexity.", "source": "https://brand.dropbox.com/framework", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "excerpt", "part": "voice", "heading": "Our tone of voice is simple, helpful, human, & magic", "marks": [ "why" ], "note": "Short commands with a reason attached. The sample lines nearby show right examples but no wrong ones.", "value": "Stay real and relatable. Write the way you talk. Avoid jargon. Remember that actual people will be reading your words.", "source": "https://brand.dropbox.com/voice-and-tone", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "excerpt", "part": "logo", "heading": "Trademarks and Brand Usage", "marks": [ "exact" ], "note": "Names nine banned changes in words that an agent can check. No pictures show them.", "value": "please don’t edit, change, distort, recolor, rotate, deconstruct, stretch, reconfigure, or otherwise modify them in any way.", "source": "https://www.dropbox.com/branding", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "excerpt", "part": "words", "heading": "Trademarks and Brand Usage", "marks": [ "exact", "limits" ], "note": "Says how the name can work in a sentence, not only how to spell it.", "value": "Always use our word marks as proper (i.e., capitalized) adjectives, not a noun or a verb.", "source": "https://www.dropbox.com/branding", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "excerpt", "part": "typography", "heading": "And DB Sharp Grotesk was created", "marks": [ "exact", "why" ], "note": "Names the typeface and why its weight varies. No sizes, weights or font file are given.", "value": "With Sharp Grotesk Variable, we have more control over the look of the type, and can adjust the weight of our type to align better optically on light vs dark backgrounds.", "source": "https://brand.dropbox.com/typography", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "excerpt", "part": "colour", "heading": "Matching color to imagery", "marks": [ "why" ], "note": "A purpose with no rule attached. The color codes appear only after JavaScript runs.", "value": "We use color to create harmony and focus. Utilizing color with careful intentionality not only strengthens visual identity but also enhances user experience, guiding users and reinforcing the brand.", "source": "https://brand.dropbox.com/color", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "excerpt", "part": "imagery", "heading": "Photography", "marks": [ "limits" ], "note": "Says when to pick photography over the other three image types. It says nothing on what to avoid.", "value": "Best for real-world examples. Use photography to tell customer stories and contextualize Dropbox products value in actual scenarios.", "source": "https://brand.dropbox.com/imagery", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "excerpt", "part": "illustration", "heading": "Illustration", "marks": [ "limits" ], "note": "Ties illustration to specific jobs, error messages included. No style rules or source files.", "value": "Best for explaining abstract, complex, or dry concepts. Use simple, charming scenes and metaphors for product or service descriptions and onboarding flows, or to soften the impact of an error message.", "source": "https://brand.dropbox.com/imagery", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "leaves-out", "value": "The color codes for 19 named colors and 20 grays appear only after JavaScript runs. The HTML that the server sends has only the names. No RGB, CMYK, or Pantone values.", "source": "https://brand.dropbox.com/color", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "leaves-out", "value": "The logo page describes the two versions but gives no minimum size, clear space or misuse examples.", "source": "https://brand.dropbox.com/logo", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "coreColours", "value": "Core colours on the rendered page: Dropbox Blue #0061FE, Coconut #F7F5F2, Graphite #1E1919; plus 16 accent colours and greys from 1000 (#1A1918) to 50 (#F7F6F5).", "source": "https://brand.dropbox.com/color", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "logoVersions", "value": "Two versions: the full logo (glyph and word mark) for partnerships and video, and the Tab (glyph within a plane) that page layout starts from.", "source": "https://brand.dropbox.com/logo", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "iconSizes", "value": "Three icon sizes: Spot Icons 120 x 120px, Pictograms 64 x 64px, UI Icons 24 x 24px.", "source": "https://brand.dropbox.com/iconography", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "voiceTraits", "value": "Tone of voice is simple, helpful, human, and magic, each with one short paragraph.", "source": "https://brand.dropbox.com/voice-and-tone", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "disclaimer", "value": "Printed educational materials should carry a line such as \"(Title) is not affiliated with or otherwise sponsored by Dropbox, Inc.\"", "source": "https://www.dropbox.com/branding", "checked": "2026-11-11" }, { "subject": "Dropbox Brand Guidelines", "guide": "dropbox", "field": "partnerToolkit", "value": "The site's Brand Partner Toolkit link opens a public shared folder; it was not opened further.", "source": "https://www.dropbox.com/scl/fo/6qjduc7j5ujf09f75w1p7/AFc217w49gnfwVNr64Bd1_A?rlkey=tkqw8jcoi7f24voc6577vakky&st=2l9cr2v5&dl=0", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "excerpt", "part": "logo", "heading": "Invertocat", "marks": [ "limits" ], "note": "Says where the mark can appear on its own. Everywhere else, the lockup with the wordmark is the default.", "value": "The standalone invertocat may be used in GitHub-owned environments or where the brand is already clearly established.", "source": "https://brand.github.com/foundations/logo", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "excerpt", "part": "logo", "heading": "Color", "marks": [ "exact", "why" ], "note": "Lists the allowed logo colors and gives a fallback. It does not say which cases allow gray or green.", "value": "The Invertocat and our wordmark should only appear in white, black, or in few cases grey or green. Like text, the logo should be legible and pass accessibility requirements in all settings. When in doubt, use the highest contrast option.", "source": "https://brand.github.com/foundations/logo", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "excerpt", "part": "words", "heading": "Wordmark lockup", "marks": [ "exact" ], "note": "A spelling rule anyone can check, placed next to the logo it matches.", "value": "GitHub is always one word with a capitalized G and H. When referring to GitHub the product, company, or service, keep it simple—GitHub.", "source": "https://brand.github.com/foundations/logo", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "excerpt", "part": "colour", "heading": "Primary palette", "marks": [ "why" ], "note": "Says that green leads and neutrals support it, and why. It gives no ratio, but example images show the balance.", "value": "In most brand applications, green should be the key player. We use neutrals, black, and white to ground it and create focus.", "source": "https://brand.github.com/foundations/color", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "excerpt", "part": "colour", "heading": "Text and color contrast", "marks": [ "exact" ], "note": "Names a contrast level from the Web Content Accessibility Guidelines that a reviewer can test.", "value": "Always ensure that all text has a minimum contrast ratio of WCAG AA.", "source": "https://brand.github.com/foundations/accessibility", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "excerpt", "part": "typography", "heading": "Mona Sans", "marks": [ "exact", "file" ], "note": "Names the typeface, and the page's download buttons link to its open source repository.", "value": "Our typographic approach centers around Mona Sans, an open source super family with an optical size, 5 widths, italics, and a mono companion. Mona Sans is always improving and expanding, so make sure you’re always using the latest version.", "source": "https://brand.github.com/foundations/typography", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "excerpt", "part": "typography", "heading": "Usage", "marks": [ "limits", "why" ], "note": "Says which styles of the font are off limits and what they are kept for.", "value": "Don’t use the other width styles available in Mona Sans. These are reserved for special events like Universe.", "source": "https://brand.github.com/foundations/typography", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "excerpt", "part": "voice", "heading": "Nerdy", "marks": [ "limits" ], "note": "Says what the trait is not, then lists separate rules for copy, design and events under it.", "value": "We bring Nerdy to the brand by walking the walk, but not in an overtly showy way. We don’t sweat the details, we relish in it.", "source": "https://brand.github.com/brand-identity/attributes", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "leaves-out", "value": "The Voice and tone page only links to a separate guide in a GitHub repository, and that link returns 404 to the public.", "source": "https://brand.github.com/brand-identity/voice-and-tone", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "leaves-out", "value": "The logo page gives no clear space or minimum size in words. Clear space exists only inside some of the downloadable logo files.", "source": "https://brand.github.com/foundations/logo", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "primaryColour", "value": "GitHub Green: #0FBF3E, RGB 15/191/62, CMYK 92/0/67/25, Pantone 360", "source": "https://brand.github.com/foundations/color", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "fonts", "value": "The typography page names Mona Sans and Mona Sans Mono. It does not mention Hubot Sans.", "source": "https://brand.github.com/foundations/typography", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "logoFiles", "value": "GitHub_Logos.zip (about 500 KB) holds SVG, PNG and PDF versions of the Invertocat, the GitHub lockup and the Copilot marks, in black and white, with and without clear space", "source": "https://brand.github.com/GitHub_Logos.zip", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "trademarkUse", "value": "The logo page says no adaptation or use of GitHub's registered trademarks is allowed without GitHub's express written permission, and lists permitted uses such as linking to GitHub", "source": "https://brand.github.com/foundations/logo", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "retiredAssets", "value": "The Copilot page says the Copilot mascot head was retired in early 2026 and must not be used", "source": "https://brand.github.com/brand-identity/copilot", "checked": "2026-11-11" }, { "subject": "GitHub Brand Toolkit", "guide": "github", "field": "sourceRepository", "value": "Every page has an 'Edit this page' link to github.com/github/brand.github.com; that repository returns 404 to the public", "source": "https://brand.github.com/foundations/logo", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "excerpt", "part": "imagery", "heading": "1. Keep Experian unmistakably Experian", "marks": [ "limits" ], "note": "Holds AI images to the existing photography rules instead of writing a second set.", "value": "Ensure AI-generated images and videos follow Experian photography standards and are photorealistic", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "excerpt", "part": "voice", "heading": "1. Keep Experian unmistakably Experian", "marks": [ "exact" ], "note": "Names the voice persona that AI-written scripts must follow. The persona has its own page in the guide.", "value": "Develop audio scripts or marketing materials using our Expedition Leader brand voice principles, ensuring delivery sounds natural and regionally appropriate", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "excerpt", "part": "ai", "heading": "2. You are responsible for the output", "marks": [ "limits" ], "note": "Puts responsibility on the person who made or commissioned the content, not on the tool.", "value": "GenAI is a tool to support the creation of our work, it does not replace our judgment. If you create or commission GenAI content, you are responsible for ensuring it is accurate, appropriate, and on brand before it is used.", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "excerpt", "part": "ai", "heading": "3. Use only owned or properly licensed content", "marks": [ "shown" ], "note": "Listed under 'Do not', with a real example of a prompt that breaks the rule.", "value": "Prompt for copyrighted styles, characters, or distinctive brand aesthetics (for example, “in the style of Pixar”)", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "excerpt", "part": "ai", "heading": "4. Respect image rights, consent, and likeness", "marks": [ "exact", "limits" ], "note": "Says consent must be written and that it covers employees too, not only the public.", "value": "Obtain written consent before using the image or likeness of any identifiable person (including employees, clients, or members of the public)", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "excerpt", "part": "ai", "heading": "5. Protect confidential and sensitive information", "marks": [ "limits" ], "note": "Listed under 'Do not'. Says the ban still applies inside approved tools.", "value": "Include personal or regulated data (for example financial or health data) in prompts or uploads, even when using enterprise‑approved AI tools", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "excerpt", "part": "ai", "heading": "6. Be clear, honest, and transparent", "marks": [ "limits" ], "note": "Says when to disclose, with an example. A separate rule says not to add disclaimers by default.", "value": "Disclose use of GenAI where it could influence customer understanding, regulatory interpretation, or trust, for example, when depicting scenarios that may reasonably be interpreted as real", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "excerpt", "part": "ai", "heading": "7. Use enterprise-approved GenAI tools", "marks": [ "limits" ], "note": "Clear rule, but the list of approved tools is on an internal SharePoint page.", "value": "Always use enterprise GenAI tools approved for use and follow the acceptable use standards. Public or non-approved tools must never be used for asset creation intended for external use.", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "leaves-out", "value": "Does not name the approved tools. The page links to an internal SharePoint site for that list.", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "leaves-out", "value": "Shows no date or version, so a reader cannot tell when the rules last changed.", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "scope", "value": "The page covers content created or modified with generative AI, including text, imagery, video and audio, in seven numbered points, each with a Do and a Do not list", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "relatedPolicies", "value": "The page says the seven points are in line with Experian's brand identity guidelines, its Global AI Policy and its Global External Communications Policy", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "publicTools", "value": "The overview says public AI tools must not be used to create or modify content for Experian work", "source": "https://www.experian.com/brand-central/brand-guidelines/genai-guidance", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "aiInPhotography", "value": "The photography page suggests extending a photo that is too small with Photoshop's Generative Fill tool, as an alternative to a gradient overlay", "source": "https://www.experian.com/brand-central/brand-identity/photography", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "assetHub", "value": "The Brand Asset Hub (experian.mediavalet.com) shows a sign-in page to visitors", "source": "https://experian.mediavalet.com/", "checked": "2026-11-11" }, { "subject": "Experian Brand Central: Generative AI guidelines", "guide": "experian", "field": "logoApproval", "value": "The logo request page says all external usage of the brand marks must be pre-approved, with separate request forms for the UK and Ireland and for other regions", "source": "https://www.experian.com/brand-central/logo-request", "checked": "2026-11-11" }, { "subject": "AI guidelines", "guide": "arizona-state-university", "field": "excerpt", "part": "ai", "heading": "Using AI to make new creative", "marks": [ "limits" ], "note": "Covers every kind of mark, not only the main logo, and rules out editing as well as creating.", "value": "AI may not be used to create, recreate or alter any ASU identity marks, spirit graphics or trademarked materials.", "source": "https://brandguide.asu.edu/elements-guidelines/ai-guidelines", "checked": "2026-11-11" }, { "subject": "AI guidelines", "guide": "arizona-state-university", "field": "excerpt", "part": "ai", "heading": "Protecting personal data and university intellectual property", "marks": [ "limits" ], "note": "Names the people covered and the kind of output that is banned.", "value": "AI cannot be used to generate photorealistic images or videos of students, faculty or staff.", "source": "https://brandguide.asu.edu/elements-guidelines/ai-guidelines", "checked": "2026-11-11" }, { "subject": "AI guidelines", "guide": "arizona-state-university", "field": "excerpt", "part": "ai", "heading": "Captions and credits", "marks": [ "exact", "shown" ], "note": "Gives the credit wording with an example line to copy.", "value": "When an image has been generated by AI, we will credit it as an AI-generated image and include the name of the creator who used the AI to make it. Example: AI-generated image courtesy The Design School.", "source": "https://brandguide.asu.edu/elements-guidelines/ai-guidelines", "checked": "2026-11-11" }, { "subject": "AI guidelines", "guide": "customer-io", "field": "excerpt", "part": "ai", "heading": "Logo usage", "marks": [ "why", "file" ], "note": "Sends people to the real logo files and says why AI copies of the logo fail.", "value": "Always source logo and brand mark files from the Brand Guidelines microsite, as AI recreations can introduce subtle inconsistencies that will render the logo off-brand.", "source": "https://brand.customer.io/docs/ai-usage-guidelines", "checked": "2026-11-11" }, { "subject": "AI guidelines", "guide": "customer-io", "field": "excerpt", "part": "ai", "heading": "Tool & platform approval", "marks": [ "exact", "limits" ], "note": "Names the tools and draws the line between trying ideas and publishing.", "value": "Consumer AI generators (e.g., DALL·E, Midjourney, Sora) are great for exploration, but loop in Brand before using their output as official assets.", "source": "https://brand.customer.io/docs/ai-usage-guidelines", "checked": "2026-11-11" }, { "subject": "AI guidelines", "guide": "customer-io", "field": "excerpt", "part": "ai", "heading": "Brand workflows", "marks": [ "why" ], "note": "Asks for disclosure to internal reviewers and gives the reason.", "value": "When submitting AI-assisted work, note how AI was used so reviewers can give faster, better feedback.", "source": "https://brand.customer.io/docs/ai-usage-guidelines", "checked": "2026-11-11" }, { "subject": "Generative AI (Imagery)", "guide": "zeiss", "field": "excerpt", "part": "ai", "heading": "Labeling", "marks": [ "exact" ], "note": "Makes labels required and names the two places a label can go.", "value": "Assets created with artificial intelligence must be labeled either in the image description and footnote or directly on the asset itself.", "source": "https://brand.zeiss.com/en/brand-design-elements/imagery/generative-ai", "checked": "2026-11-11" }, { "subject": "Generative AI (Imagery)", "guide": "zeiss", "field": "excerpt", "part": "ai", "heading": "Don’ts", "marks": [ "limits" ], "note": "Names specific looks to avoid when AI images show people.", "value": "Flawless skin, staged studio perfection, or artificial beauty standards", "source": "https://brand.zeiss.com/en/brand-design-elements/imagery/generative-ai", "checked": "2026-11-11" }, { "subject": "Generative AI (Imagery)", "guide": "zeiss", "field": "excerpt", "part": "ai", "heading": "On-brand style", "marks": [ "dated" ], "note": "Names who to ask, and the team name links to the email address brand@zeiss.com.", "value": "Reach out to the ZEISS Brand Team if you are unsure.", "source": "https://brand.zeiss.com/en/brand-design-elements/imagery/generative-ai", "checked": "2026-11-11" }, { "subject": "AI guidance for brand standards", "guide": "care", "field": "excerpt", "part": "ai", "heading": "AI guidance for brand standards", "marks": [ "why" ], "note": "Gives the reason before the rules, so the yes and no lists read as one idea.", "value": "While generative AI can support creative development, it can also erode trust if used in ways that misrepresent reality.", "source": "https://brand.care.org/brand-standards/ai-guidance/", "checked": "2026-11-11" }, { "subject": "AI guidance for brand standards", "guide": "care", "field": "excerpt", "part": "ai", "heading": "NO 3. Do not use AI-generated people to represent real individuals.", "marks": [ "limits" ], "note": "Names the groups that AI people must never stand in for.", "value": "AI-generated individuals should never stand in for program participants, communities, or partners.", "source": "https://brand.care.org/brand-standards/ai-guidance/", "checked": "2026-11-11" }, { "subject": "AI guidance for brand standards", "guide": "care", "field": "excerpt", "part": "ai", "heading": "YES: Appropriate uses of AI", "marks": [ "dated" ], "note": "Ends the rules with an email address for questions.", "value": "If you have questions about whether AI-generated content meets CARE brand standards, please contact brandsupport@care.org.", "source": "https://brand.care.org/brand-standards/ai-guidance/", "checked": "2026-11-11" }, { "subject": "AI Branding Guidelines", "guide": "utah-state-university", "field": "excerpt", "part": "ai", "heading": "Adherence to Brand Standards and Legal Compliance", "marks": [ "limits" ], "note": "Includes upscaling, so even enlarging a logo with AI is not allowed.", "value": "Do not use AI tools to create, recreate, upscale or alter any university logos, spirit marks, or trademarked works.", "source": "https://www.usu.edu/brand/standards/ai/best-practices", "checked": "2026-11-11" }, { "subject": "AI Branding Guidelines", "guide": "utah-state-university", "field": "excerpt", "part": "ai", "heading": "Controls", "marks": [ "limits" ], "note": "Disclosure here is to the project team. Public citation is required only when policy says so.", "value": "When possible, disclose the use of GenAI in creating or assisting with the creation of assets to all team members involved with a project.", "source": "https://www.usu.edu/brand/standards/ai/branding-guidelines", "checked": "2026-11-11" }, { "subject": "AI Branding Guidelines", "guide": "utah-state-university", "field": "excerpt", "part": "ai", "heading": "AI Branding Guidelines", "marks": [ "dated" ], "note": "Says who reviews the rules (University Marketing & Communications) but gives no date or schedule.", "value": "As an evolving technology, GenAI usage guidelines, standards and policies are subject to ongoing updates. To maintain best practices, UMAC will periodically review AI policies from both the State of Utah and internal university stakeholders.", "source": "https://www.usu.edu/brand/standards/ai/branding-guidelines", "checked": "2026-11-11" }, { "subject": "Claude Projects", "field": "whatItIs", "value": "Projects are self-contained workspaces with their own chat histories and knowledge bases. Within a project you can upload documents, provide context and have focused chats with Claude.", "source": "https://support.claude.com/en/articles/9517075-what-are-projects", "checked": "2026-11-11" }, { "subject": "Claude Projects", "field": "availability", "value": "Projects are available to all users, including free accounts. Free users can create a maximum of five projects.", "source": "https://support.claude.com/en/articles/9517075-what-are-projects", "checked": "2026-11-11" }, { "subject": "Claude Projects", "field": "projectKnowledge", "value": "You can upload documents, text files or code to a project's knowledge base. Anything uploaded there is used across all chats in that project.", "source": "https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects", "checked": "2026-11-11" }, { "subject": "Claude Projects", "field": "projectInstructions", "value": "Each project can have project instructions, set with 'Set project instructions'. Claude uses them for all chats within the project.", "source": "https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects", "checked": "2026-11-11" }, { "subject": "Claude Projects", "field": "contextBetweenChats", "value": "Context is not shared across chats within a project unless the information is added to the project knowledge base.", "source": "https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects", "checked": "2026-11-11" }, { "subject": "Claude Projects", "field": "fileLimits", "value": "Project files: 30MB per file. Number of files: unlimited, but total content must fit within Claude's context window. Text extraction only, except for multimodal PDFs.", "source": "https://support.claude.com/en/articles/8241126-upload-files-to-claude", "checked": "2026-11-11" }, { "subject": "Claude Projects", "field": "largerKnowledge", "value": "On paid plans (Pro, Max, Ultra, Team, Enterprise), when project knowledge approaches the context window limit, Claude switches on retrieval augmented generation (RAG), which expands a project's capacity by up to 10 times.", "source": "https://support.claude.com/en/articles/11473015-retrieval-augmented-generation-rag-for-projects", "checked": "2026-11-11" }, { "subject": "Claude Projects", "field": "sharing", "value": "On Team and Enterprise plans, projects can be shared with members of the organisation, with 'Can view' or 'Can edit' permission.", "source": "https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects", "checked": "2026-11-11" }, { "subject": "ChatGPT Projects", "field": "whatItIs", "value": "Projects keep related chats, files and instructions together, and ChatGPT can use that context for ongoing work.", "source": "https://help.openai.com/en/articles/10169521-projects-in-chatgpt", "checked": "2026-11-11" }, { "subject": "ChatGPT Projects", "field": "files", "value": "You can add reference material by uploading PDFs, spreadsheets, docs or images, or by pasting text.", "source": "https://help.openai.com/en/articles/10169521-projects-in-chatgpt", "checked": "2026-11-11" }, { "subject": "ChatGPT Projects", "field": "projectInstructions", "value": "Project instructions are added under Project settings. They apply only within that project and override your global custom instructions.", "source": "https://help.openai.com/en/articles/10169521-projects-in-chatgpt", "checked": "2026-11-11" }, { "subject": "ChatGPT Projects", "field": "fileLimits", "value": "Free: 5 files per project. Go and Plus: 25 files per project. Edu, Pro, Business and Enterprise: 40 files per project. Only 10 files can be uploaded at the same time. Users can create an unlimited number of projects.", "source": "https://help.openai.com/en/articles/10169521-projects-in-chatgpt", "checked": "2026-11-11" }, { "subject": "ChatGPT Projects", "field": "fileSize", "value": "Documents and presentations have a maximum size of 512 MB per file. Text and document files are capped at 2 million tokens per file.", "source": "https://help.openai.com/en/articles/8555545-uploading-files-and-audio-to-chatgpt", "checked": "2026-11-11" }, { "subject": "ChatGPT Projects", "field": "sharing", "value": "Projects can be shared, and invitees get chat or edit access. Shared projects use project-only memory and cannot access a member's memories or custom instructions from outside the project.", "source": "https://help.openai.com/en/articles/10169521-projects-in-chatgpt", "checked": "2026-11-11" }, { "subject": "ChatGPT custom GPTs", "field": "instructions", "value": "Instructions define how a GPT behaves: what it should do, how it should respond and what it should avoid. They are applied to every conversation.", "source": "https://help.openai.com/en/articles/8554397-creating-and-editing-gpts", "checked": "2026-11-11" }, { "subject": "ChatGPT custom GPTs", "field": "knowledgeFiles", "value": "You can attach up to 20 files to a GPT as knowledge. Each file can be up to 512 MB.", "source": "https://help.openai.com/en/articles/8554397-creating-and-editing-gpts", "checked": "2026-11-11" }, { "subject": "ChatGPT custom GPTs", "field": "knowledgeVsInstructions", "value": "OpenAI's advice: use knowledge for reference material, not rules or behaviour, and put rules, tone and workflow guidance in instructions.", "source": "https://help.openai.com/en/articles/8554397-creating-and-editing-gpts", "checked": "2026-11-11" }, { "subject": "ChatGPT custom GPTs", "field": "retirement", "value": "OpenAI says it is planning to retire custom GPTs and move creators' workflows to plugins. Standard retirement is scheduled for December 11, 2026. New GPT creation and publishing are not available on personal accounts (Free, Go, Plus and Pro).", "source": "https://help.openai.com/en/articles/8554397-creating-and-editing-gpts", "checked": "2026-11-11" }, { "subject": "ChatGPT plugins and skills", "field": "plugins", "value": "A plugin can include skills that provide instructions and workflow guidance, connected apps, app templates and extensions. A custom GPT's published instructions and knowledge may be migrated into a plugin.", "source": "https://help.openai.com/en/articles/20001256-plugins-in-chatgpt", "checked": "2026-11-11" }, { "subject": "ChatGPT plugins and skills", "field": "skills", "value": "Skills are reusable, shareable workflows that can include instructions, examples and code. They are available to eligible ChatGPT Business, Enterprise, Healthcare and Edu users.", "source": "https://help.openai.com/en/articles/20001066-skills-in-chatgpt", "checked": "2026-11-11" }, { "subject": "Cursor rules", "field": "ruleTypes", "value": "Cursor supports four types of rules: Project Rules (stored in .cursor/rules), User Rules, Team Rules (Team and Enterprise plans) and AGENTS.md, a markdown alternative to .cursor/rules.", "source": "https://cursor.com/docs/rules", "checked": "2026-11-11" }, { "subject": "Cursor rules", "field": "projectRules", "value": "Project rules live in .cursor/rules as .mdc files and are version-controlled. A plain .md file in .cursor/rules is ignored because it has no frontmatter for description, globs and alwaysApply.", "source": "https://cursor.com/docs/rules", "checked": "2026-11-11" }, { "subject": "Cursor rules", "field": "howTheyApply", "value": "When a rule is applied, its contents are included at the start of the model context. A rule can apply to every chat, be pulled in when Agent judges its description relevant, attach when a file matching its glob pattern is in context, or apply only when @-mentioned.", "source": "https://cursor.com/docs/rules", "checked": "2026-11-11" }, { "subject": "Cursor rules", "field": "referencedFiles", "value": "A file mentioned in a rule is not inlined into the prompt. Agent reads it with its tools when it needs it. Anything that must always be in context goes in the rule body.", "source": "https://cursor.com/docs/rules", "checked": "2026-11-11" }, { "subject": "Cursor rules", "field": "size", "value": "The docs advise keeping rules under 500 lines and splitting large rules into several smaller ones. Under 'What to avoid in rules' they list copying entire style guides, and say to use a linter instead.", "source": "https://cursor.com/docs/rules", "checked": "2026-11-11" }, { "subject": "Claude Skills", "field": "whatItIs", "value": "Skills are folders of instructions, scripts and resources that Claude loads dynamically to improve performance on specialised tasks. One of the custom skill examples given is applying brand style guidelines to documents and presentations.", "source": "https://support.claude.com/en/articles/12512176-what-are-skills", "checked": "2026-11-11" }, { "subject": "Claude Skills", "field": "structure", "value": "Every Skill requires a SKILL.md file with YAML frontmatter. The required fields are name and description. A Skill can also bundle other Markdown files, scripts, and resources such as templates.", "source": "https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview", "checked": "2026-11-11" }, { "subject": "Claude Skills", "field": "fieldLimits", "value": "name: maximum 64 characters, lowercase letters, numbers and hyphens only. description: must be non-empty, maximum 1,024 characters, and must say both what the Skill does and when Claude should use it.", "source": "https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview", "checked": "2026-11-11" }, { "subject": "Claude Skills", "field": "loading", "value": "At startup only each Skill's name and description are loaded (about 100 tokens per Skill). The SKILL.md body (under 5k tokens) loads when the Skill is triggered. Bundled files load only when needed.", "source": "https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview", "checked": "2026-11-11" }, { "subject": "Claude Skills", "field": "whereSkillsLive", "value": "In Claude Code, custom Skills are folders in ~/.claude/skills/ (personal) or .claude/skills/ (project). In claude.ai, custom Skills are uploaded as zip files, on Pro, Max, Ultra, Team and Enterprise plans with code execution enabled. They can also be uploaded through the Claude API.", "source": "https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview", "checked": "2026-11-11" }, { "subject": "Claude Skills", "field": "organisationSkills", "value": "On Team and Enterprise plans, organisation Owners can provision skills for all users. They appear in every member's skills list and can be enabled or disabled by default.", "source": "https://support.claude.com/en/articles/12512176-what-are-skills", "checked": "2026-11-11" }, { "subject": "Claude Skills", "field": "openStandard", "value": "The Agent Skills specification is published as an open standard at agentskills.io.", "source": "https://support.claude.com/en/articles/12512176-what-are-skills", "checked": "2026-11-11" }, { "subject": "Frontify", "field": "guidelinesProduct", "value": "Frontify Guidelines publishes brand guidelines online. They can include logos, colors, typography, imagery, voice, templates and usage rules, organised into customizable topics, with around 40+ pre-built content blocks.", "source": "https://www.frontify.com/en/brand-guidelines", "checked": "2026-11-11" }, { "subject": "Frontify", "field": "aiAccess", "value": "The Guidelines page says guidelines are structured data that AI tools can read, that Frontify is an official Claude connector and integrates with Microsoft Copilot, and that the Frontify MCP server connects tools like ChatGPT to guidelines, assets and templates.", "source": "https://www.frontify.com/en/brand-guidelines", "checked": "2026-11-11" }, { "subject": "Frontify", "field": "api", "value": "Frontify has a GraphQL API giving programmatic access to accounts, brands, workspaces, libraries, projects, assets and metadata, and users and permissions. It needs an account with API access enabled and uses OAuth 2.0.", "source": "https://help.frontify.com/en/articles/5402357-getting-started-with-the-frontify-graphql-api", "checked": "2026-11-11" }, { "subject": "Frontify", "field": "otherDeveloperTools", "value": "Frontify also offers webhooks for change notifications and a Brand SDK for building custom content blocks, apps and themes. Documentation is at developer.frontify.com.", "source": "https://www.frontify.com/en/brand-guidelines", "checked": "2026-11-11" }, { "subject": "Frontify", "field": "externalSharing", "value": "Guidelines can be shared with agencies, suppliers and other external collaborators while controlling what they can see. Custom domains and SSO are available.", "source": "https://www.frontify.com/en/brand-guidelines", "checked": "2026-11-11" }, { "subject": "Zeroheight", "field": "whatItIs", "value": "zeroheight is a design systems management platform. You build documentation sites with no-code editing and customizable templates, and it says everything published is ready for AI agents to use.", "source": "https://zeroheight.com/", "checked": "2026-11-11" }, { "subject": "Zeroheight", "field": "brandUse", "value": "The help centre says zeroheight primarily focuses on documenting product design systems but is an option for documenting brand guidelines, and gives a guide for brand teams.", "source": "https://help.zeroheight.com/hc/en-us/articles/36473785280923-Using-zeroheight-for-brand-documentation", "checked": "2026-11-11" }, { "subject": "Zeroheight", "field": "api", "value": "The zeroheight REST API can read documentation (page content as structured data, Markdown or HTML; styleguides, navigation, categories, releases, page statuses; design token exports) and write to it (create and edit pages, upload images and files, publish drafts).", "source": "https://help.zeroheight.com/hc/en-us/articles/35887050539035-Zeroheight-API-Use-the-zeroheight-REST-API", "checked": "2026-11-11" }, { "subject": "Zeroheight", "field": "apiPlans", "value": "The help article says the API isn't available on Free or Starter plans. Its opening line says the API is included on Enterprise plans; its write-access section asks for a plan that includes the API (Professional or Enterprise).", "source": "https://help.zeroheight.com/hc/en-us/articles/35887050539035-Zeroheight-API-Use-the-zeroheight-REST-API", "checked": "2026-11-11" }, { "subject": "Zeroheight", "field": "apiRateLimit", "value": "Every token can make 30 read requests and 30 write requests every 30 seconds.", "source": "https://help.zeroheight.com/hc/en-us/articles/35887050539035-Zeroheight-API-Use-the-zeroheight-REST-API", "checked": "2026-11-11" }, { "subject": "Zeroheight", "field": "mcp", "value": "zeroheight MCP delivers documented components, tokens and guidance to AI tools and agents, and lets agents create and edit page content.", "source": "https://zeroheight.com/mcp/", "checked": "2026-11-11" }, { "subject": "Zeroheight", "field": "access", "value": "A styleguide can be made public, with specific pages locked behind SSO or a password on Professional and Enterprise plans. Viewers can also be invited by email, with access expiring after 30 days.", "source": "https://help.zeroheight.com/hc/en-us/articles/36473785280923-Using-zeroheight-for-brand-documentation", "checked": "2026-11-11" }, { "subject": "Rainbrand", "field": "description", "value": "Rainbrand is the brand layer for agents. It maintains your brand's identity, guidance, and assets as shared context that agents and products can use and update.", "source": "https://docs.rainbrand.com/introduction", "checked": "2026-11-11" }, { "subject": "Rainbrand", "field": "sources-accepted", "value": "A brand can be added from websites, PDFs, social media, logos (SVG, PNG), images, documents (DOCX, TXT), presentations (PPTX), typography files (OTF, TTF, WOFF2), colour palettes and rules, videos, Markdown files, and written direction on voice and positioning.", "source": "https://docs.rainbrand.com/guides/create-brand", "checked": "2026-11-11" }, { "subject": "Rainbrand", "field": "connection", "value": "People connect agents that support remote MCP (Model Context Protocol) to Rainbrand's MCP server at https://mcp.rainbrand.com/mcp; the quickstart covers ChatGPT, Codex, Claude and other agents. Applications and pipelines use the REST API.", "source": "https://docs.rainbrand.com/mcp/getting-started", "checked": "2026-11-11" }, { "subject": "Rainbrand", "field": "brief", "value": "A Brief gives the guidance and assets for a specific task.", "source": "https://docs.rainbrand.com/introduction", "checked": "2026-11-11" }, { "subject": "Rainbrand", "field": "review", "value": "A Review checks an asset against the brand and returns findings to guide revisions. Checks cover colours, typography, logo and copy; each check returns a verdict (pass, fail, uncertain or not applicable) with a short reason and evidence where available.", "source": "https://docs.rainbrand.com/guides/request-review", "checked": "2026-11-11" }, { "subject": "Rainbrand", "field": "brand-skill", "value": "A Brand Skill is a complete, versioned snapshot of a brand's identity, guidance and asset references. It can be retrieved through the API or exported as a folder (ZIP) for agents and tools that work with local files.", "source": "https://docs.rainbrand.com/guides/use-brand-skill", "checked": "2026-11-11" }, { "subject": "Rainbrand", "field": "update", "value": "Guidance and assets are kept current by editing the brand as it changes.", "source": "https://docs.rainbrand.com/getting-started/embed-into-your-product", "checked": "2026-11-11" }, { "subject": "Rainbrand", "field": "embed", "value": "A product can add each customer's brand through the API and give its agents MCP access to the same brand, then request a Brief per task and a Review of the result.", "source": "https://docs.rainbrand.com/getting-started/embed-into-your-product", "checked": "2026-11-11" }, { "subject": "Rainbrand", "field": "pricing", "value": "Plans and included usage are listed on the pricing page.", "source": "https://www.rainbrand.com/pricing", "checked": "2026-11-11" }, { "subject": "Anthropic prompting best practices", "field": "new-employee", "value": "Think of Claude as a brilliant but new employee who lacks context on your norms and workflows. The more precisely you explain what you want, the better the result.", "source": "https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/claude-prompting-best-practices", "checked": "2026-11-11" }, { "subject": "Anthropic prompting best practices", "field": "explain-why", "value": "Providing context or motivation behind your instructions, such as explaining to Claude why such behavior is important, can give Claude more information about your goals and help it deliver more targeted responses.", "source": "https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/claude-prompting-best-practices", "checked": "2026-11-11" }, { "subject": "Rainbrand", "field": "many-brands", "value": "A customer who works across several brands in Claude uses Rainbrand to keep each brand's context ready, so each identity stays distinct from project to project.", "source": "https://www.rainbrand.com/customers/gtm-cofounder", "checked": "2026-11-11" }, { "subject": "Claude plans", "field": "pricing-page", "value": "The vendor's current plans and what each includes are on this page. Plan facts on this site are as of the date checked.", "source": "https://claude.com/pricing", "checked": "2026-11-11" }, { "subject": "ChatGPT plans", "field": "pricing-page", "value": "The vendor's current plans and what each includes are on this page. Plan facts on this site are as of the date checked.", "source": "https://chatgpt.com/pricing", "checked": "2026-11-11" }, { "subject": "Cursor plans", "field": "pricing-page", "value": "The vendor's current plans and what each includes are on this page. Plan facts on this site are as of the date checked.", "source": "https://cursor.com/pricing", "checked": "2026-11-11" }, { "subject": "zeroheight plans", "field": "pricing-page", "value": "The vendor's current plans and what each includes are on this page. Plan facts on this site are as of the date checked.", "source": "https://zeroheight.com/pricing", "checked": "2026-11-11" } ] }