public-design-tokens-log@w3.org from September 2021 by date

Tuesday, 28 September 2021

• Re: [community-group] Are token descriptions optional or required? (#62) Christian Martin Nies via GitHub
• Re: [community-group] Are token descriptions optional or required? (#62) Fernando Poe Bellentani via GitHub
• Re: [community-group] Consider using grammarly or hemingway to make language more understandable/inclusive (#66) Christian Martin Nies via GitHub
• Re: [community-group] Are token descriptions optional or required? (#62) Christian Martin Nies via GitHub

Monday, 27 September 2021

• Re: [community-group] Are token descriptions optional or required? (#62) dom1n1k via GitHub
• Re: [community-group] Group & file level properties (#72) Trevor Burnham via GitHub

Sunday, 26 September 2021

• Re: [community-group] The Designer’s Workflow (#43) Alexander Vassbotn Røyne-Helgesen via GitHub
• Re: [community-group] The Designer’s Workflow (#43) Alexander Vassbotn Røyne-Helgesen via GitHub
• Re: [community-group] [RFC] Glossary (#32) Alexander Vassbotn Røyne-Helgesen via GitHub
• Re: [community-group] [RFC] Glossary (#32) Jina Anne via GitHub
• Re: [community-group] [RFC] Glossary (#32) Jina Anne via GitHub
• Closed: [community-group] [RFC] Glossary (#32) Jina Anne via GitHub
• Closed: [community-group] Defining "design token" from a "technical" perspective (#42) Jina Anne via GitHub
• Re: [community-group] Defining "design token" from a "technical" perspective (#42) Jina Anne via GitHub
• Re: [community-group] The Designer’s Workflow (#43) Jina Anne via GitHub
• Re: [community-group] Are token descriptions optional or required? (#62) Jina Anne via GitHub
• Re: [community-group] [RFC] Glossary (#32) Alexander Vassbotn Røyne-Helgesen via GitHub

Saturday, 25 September 2021

• Re: [community-group] [RFC] Design Token authoring tools (#36) Alexander Vassbotn Røyne-Helgesen via GitHub
• Re: [community-group] [RFC] Design Token authoring tools (#36) Alexander Vassbotn Røyne-Helgesen via GitHub
• Re: [community-group] Defining "design token" from a "technical" perspective (#42) Alexander Vassbotn Røyne-Helgesen via GitHub
• Re: [community-group] The Designer’s Workflow (#43) Alexander Vassbotn Røyne-Helgesen via GitHub
• Re: [community-group] The Designer’s Workflow (#43) Nate Baldwin via GitHub
• [community-group] Loosen up the color type (#79) Simon Bächler via GitHub
• Re: [community-group] Group & file level properties (#72) Simon Bächler via GitHub
• Re: [community-group] Group & file level properties (#72) Thomas Gossmann via GitHub
• Re: [community-group] Are token descriptions optional or required? (#62) Thomas Gossmann via GitHub
• Re: [community-group] The Designer’s Workflow (#43) Alexander Vassbotn Røyne-Helgesen via GitHub

Friday, 24 September 2021

• [community-group] Value Definition Syntax for a tokens type (#78) Sofi Valitova via GitHub
• Re: [community-group] Are token descriptions optional or required? (#62) Sofi Valitova via GitHub
• Re: [community-group] Token name case sensitivity (#59) Sofi Valitova via GitHub
• Re: [community-group] Should composites be part of the MVP specification? (#54) Thomas Gossmann via GitHub

Thursday, 23 September 2021

• Re: [community-group] Object vs Array (#55) Ivan Maksimovic via GitHub

Wednesday, 22 September 2021

• Re: [community-group] Group & file level properties (#72) Zhao Lei via GitHub

Tuesday, 21 September 2021

• Re: [community-group] Improve readability of RFC 2119 keywords (MUST, SHOULD…) (#65) David Booth via GitHub
• Re: [community-group] Improve readability of RFC 2119 keywords (#68) David Booth via GitHub
• [community-group] [Format] Disambiguate RFC 2119 keywords where appropriate (#77) Kaelig Deloumeau-Prigent via GitHub

Monday, 20 September 2021

• [community-group] Merged Pull Request: Remove stale roadmap Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Remove stale roadmap (#47) Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Fix/intro grammar (#76) Kevin Powell via GitHub
• [community-group] Closed Pull Request: Fix/intro grammar Kevin Powell via GitHub

Sunday, 19 September 2021

• Re: [community-group] Consider using grammarly or hemingway to make language more understandable/inclusive (#66) Jina Anne via GitHub

Friday, 17 September 2021

• Re: [community-group] Consider using grammarly or hemingway to make language more understandable/inclusive (#66) Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Fix/intro grammar (#76) Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Fix/intro grammar (#76) netlify[bot] via GitHub
• [community-group] Pull Request: Fix/intro grammar Kevin Powell via GitHub
• Re: [community-group] Consider using grammarly or hemingway to make language more understandable/inclusive (#66) Kevin Powell via GitHub
• Closed: [community-group] [Format] Token value - string, number, array, object? (#58) Kevin Powell via GitHub
• [community-group] Merged Pull Request: feat: add specificity to token types. closes #58 Kevin Powell via GitHub

Thursday, 16 September 2021

• Re: [community-group] [Format] Token name character restrictions (#60) James Nash via GitHub
• Re: [community-group] Improve readability of RFC 2119 keywords (#68) Jina Anne via GitHub
• Closed: [community-group] Improve readability of RFC 2119 keywords (MUST, SHOULD…) (#65) Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Improve readability of RFC 2119 keywords (MUST, SHOULD…) (#65) Kaelig Deloumeau-Prigent via GitHub
• [community-group] Merged Pull Request: Improve readability of RFC 2119 keywords Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Improve readability of RFC 2119 keywords (#68) Kaelig Deloumeau-Prigent via GitHub

Tuesday, 14 September 2021

• [community-group] Merged Pull Request: Setup and editing instructions for technical reports James Nash via GitHub
• Re: [community-group] Setup and editing instructions for technical reports (#75) James Nash via GitHub
• [community-group] Merged Pull Request: Add Prettier pre-commit hook (#57 redux) Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] [Format] Object vs Array (#55) James Nash via GitHub
• Re: [community-group] [Format] Object vs Array (#55) James Nash via GitHub
• Re: [community-group] Setup and editing instructions for technical reports (#75) netlify[bot] via GitHub
• [community-group] Pull Request: Setup and editing instructions for technical reports James Nash via GitHub
• Re: [community-group] [Format] Group & file level properties (#72) James Nash via GitHub
• Re: [community-group] Prettier pre-commit hook (#57) Danny Banks via GitHub
• [community-group] Closed Pull Request: Prettier pre-commit hook Danny Banks via GitHub
• Re: [community-group] Improve readability of RFC 2119 keywords (MUST, SHOULD…) (#65) Jina Anne via GitHub
• Re: [community-group] [Format] Token name - reserved words (#61) Jina Anne via GitHub
• Re: [community-group] [Format] Object vs Array (#55) Ivan Maksimovic via GitHub
• [community-group] Merged Pull Request: fix formatting issues in groups and types Kevin Powell via GitHub
• Closed: [community-group] Fix formatting issues (#67) Kevin Powell via GitHub
• Re: [community-group] fix formatting issues in groups and types (#74) netlify[bot] via GitHub
• [community-group] Pull Request: fix formatting issues in groups and types Kevin Powell via GitHub
• [community-group] Merged Pull Request: feat: link #72 to the spec Kevin Powell via GitHub
• Re: [community-group] feat: link #72 to the spec (#73) netlify[bot] via GitHub
• [community-group] Pull Request: feat: link #72 to the spec Kevin Powell via GitHub
• Re: [community-group] [Format] Token types - optional or required (#63) Kevin Powell via GitHub
• Re: [community-group] [Format] Object vs Array (#55) Kevin Powell via GitHub
• [community-group] [Format] Group & file level properties (#72) Kevin Powell via GitHub
• Re: [community-group] [Format] Should composites be part of the MVP specification? (#54) Lukas Oppermann via GitHub
• Re: [community-group] [Format] Should composites be part of the MVP specification? (#54) Kevin Powell via GitHub
• Re: [community-group] feat: add specificity to token types. closes #58 (#71) netlify[bot] via GitHub
• [community-group] Pull Request: feat: add specificity to token types. closes #58 Kevin Powell via GitHub
• Re: [community-group] [Format] Token value - string, number, array, object? (#58) Kevin Powell via GitHub

Monday, 13 September 2021

• Re: [community-group] Add Prettier pre-commit hook (#70) netlify[bot] via GitHub
• [community-group] Pull Request: Add Prettier pre-commit hook Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] [Format] Token value - string, number, array, object? (#58) James Nash via GitHub
• Re: [community-group] Improve readability of RFC 2119 keywords (MUST, SHOULD…) (#65) James Nash via GitHub
• Re: [community-group] [Format] Token name - reserved words (#61) James Nash via GitHub
• Re: [community-group] [Format] Token types - optional or required (#63) James Nash via GitHub
• Re: [community-group] Improve readability of RFC 2119 keywords (MUST, SHOULD…) (#65) Kaelig Deloumeau-Prigent via GitHub
• [community-group] Merged Pull Request: Maintenance: add `validate` script, switch from `yarn` to `npm`, set default formatter for VS Code Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Add `validate` script to check specs are valid (#69) netlify[bot] via GitHub
• [community-group] Pull Request: Add `validate` script to check specs are valid Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Test RFC-2119 styling (#68) netlify[bot] via GitHub
• [community-group] Pull Request: Test RFC-2119 styling Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] [Format] Token name - reserved words (#61) Jina Anne via GitHub
• Re: [community-group] Let's favor `strong` element over all caps for emphasis. (#65) Jina Anne via GitHub
• Re: [community-group] Let's favor `strong` element over all caps for emphasis. (#65) Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] [Format] Token name - reserved words (#61) Kevin Powell via GitHub
• Re: [community-group] Let's favor `strong` element over all caps for emphasis. (#65) James Nash via GitHub

Saturday, 11 September 2021

• [community-group] Merged Pull Request: Add composite types section Kaelig Deloumeau-Prigent via GitHub

Friday, 10 September 2021

• Re: [community-group] [Format] Token types - optional or required (#63) Danny Banks via GitHub

Thursday, 9 September 2021

• Re: [community-group] [Format] Token types - optional or required (#63) Matt Felten via GitHub
• Re: [community-group] [Format] Token types - optional or required (#63) Dale Sande / @anotheruiguy via GitHub
• Re: [community-group] [Format] Token types - optional or required (#63) Jina Anne via GitHub
• Re: [community-group] [Format] Token types - optional or required (#63) Dale Sande / @anotheruiguy via GitHub
• Re: [community-group] [Format] Token types - optional or required (#63) Jina Anne via GitHub
• Re: [community-group] [Format] Token name - reserved words (#61) Dale Sande / @anotheruiguy via GitHub
• Re: [community-group] [Format] Token types - optional or required (#63) Dale Sande / @anotheruiguy via GitHub
• [community-group] Merged Pull Request: Synchronize with latest version of google doc Kevin Powell via GitHub
• Re: [community-group] Synchronize with latest version of google doc (#64) Kevin Powell via GitHub
• [community-group] Fix formatting issues noted on https://github.com/design-tokens/community-group/pull/64 (#67) Kevin Powell via GitHub
• Re: [community-group] [Format] Token name - reserved words (#61) Jina Anne via GitHub
• Re: [community-group] [Format] Token types - optional or required (#63) Jina Anne via GitHub
• Re: [community-group] Synchronize with latest version of google doc (#64) Jina Anne via GitHub
• [community-group] Consider using grammarly or hemingway to make language more understandable/inclusive (#66) Jina Anne via GitHub
• [community-group] Let's favor `strong` element over all caps for emphasis. (#65) Jina Anne via GitHub
• Re: [community-group] [Format] Token types - optional or required (#63) Dale Sande / @anotheruiguy via GitHub
• Re: [community-group] [Format] Token types - optional or required (#63) Matt Felten via GitHub
• Re: [community-group] Synchronize with latest version of google doc (#64) netlify[bot] via GitHub
• [community-group] Pull Request: Synchronize with latest version of google doc Kevin Powell via GitHub
• Re: [community-group] [Format] Token types - optional or required (#63) Nicolas Hoizey via GitHub
• Re: [community-group] [Format] Token name case sensitivity (#59) Matt Felten via GitHub
• [community-group] [Format] Token types - optional or required (#63) Kevin Powell via GitHub
• Re: [community-group] [Format] Are token descriptions optional or required? (#62) Kevin Powell via GitHub
• [community-group] [Format] Are token descriptions optional or required? (#62) Kevin Powell via GitHub
• [community-group] [Format] Token name - reserved words (#61) Kevin Powell via GitHub
• [community-group] [Format] Token name character restrictions (#60) Kevin Powell via GitHub
• [community-group] [Format] Token name case sensitivity (#59) Kevin Powell via GitHub
• [community-group] [Format] Token value - string, number, array, object? (#58) Kevin Powell via GitHub
• Re: [community-group] Prettier pre-commit hook (#57) Kaelig Deloumeau-Prigent via GitHub

Wednesday, 8 September 2021

• Re: [community-group] Prettier pre-commit hook (#57) netlify[bot] via GitHub
• [community-group] Pull Request: Prettier pre-commit hook Danny Banks via GitHub
• [community-group] Closed Pull Request: Adding prettier pre-commit hook Danny Banks via GitHub
• Re: [community-group] Adding prettier pre-commit hook (#56) netlify[bot] via GitHub
• [community-group] Pull Request: Adding prettier pre-commit hook Danny Banks via GitHub
• Closed: [community-group] [RFC] Format specification (#1) Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] [RFC] Format specification (#1) Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] [Format] Object vs Array (#55) James Nash via GitHub
• Re: [community-group] [Format] Should composites be part of the MVP specification? (#54) Lukas Oppermann via GitHub
• Re: [community-group] Add composite types section (#52) Danny Banks via GitHub
• [community-group] [Format] Object vs Array (#55) Danny Banks via GitHub
• [community-group] [Format] Should composites be part of the MVP specification? (#54) Danny Banks via GitHub
• Re: [community-group] Add composite types section (#52) Kaelig Deloumeau-Prigent via GitHub

Tuesday, 7 September 2021

• Re: [community-group] [Format] Type: font name (#53) Lucas Arundell via GitHub
• [community-group] [Format] Type: font name (#53) Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Add composite types section (#52) netlify[bot] via GitHub
• [community-group] Pull Request: Add composite types section Kaelig Deloumeau-Prigent via GitHub
• [community-group] Closed Pull Request: Testing workflow James Nash via GitHub
• [community-group] Merged Pull Request: Renamed vendor attribute to extensions James Nash via GitHub
• Re: [community-group] Renamed vendor attribute to extensions (#51) netlify[bot] via GitHub
• [community-group] Pull Request: Renamed vendor attribute to extensions James Nash via GitHub
• Re: [community-group] Testing workflow (#50) netlify[bot] via GitHub
• [community-group] Pull Request: Testing workflow Kaelig Deloumeau-Prigent via GitHub

Friday, 3 September 2021

• Re: [community-group] [RFC] Format specification (#1) Kevin Powell via GitHub
• Re: [community-group] [RFC] Format specification (#1) Lukas Oppermann via GitHub
• Re: [community-group] [RFC] Format specification (#1) Kevin Powell via GitHub
• Re: [community-group] [RFC] Format specification (#1) Lukas Oppermann via GitHub
• Re: [community-group] [RFC] Format specification (#1) Kevin Powell via GitHub
• Re: [community-group] [RFC] Format specification (#1) Lukas Oppermann via GitHub

Last message date: Tuesday, 28 September 2021 12:13:15 UTC