@adobe/design-system-registry 0.0.0-layout-20260209174611

package/AUTHORING.md

@@ -0,0 +1,290 @@
+# Authoring Guide: Spectrum Design System Glossary
+
+This guide explains how to author and maintain glossary terms in the Spectrum Design System Registry.
+
+## Overview
+
+The Design System Registry serves as the single source of truth for Spectrum design terminology. Each term includes:
+
+* **Basic Information**: ID, label, description
+* **Definition**: Structured definition following Spectrum's naming methodology
+* **Platform Variations**: How the term differs across platforms (web, iOS, Android, etc.)
+* **Terminology Metadata**: Classification and naming rationale
+* **Sources**: References to documentation and standards
+* **Governance**: Ownership and review information
+* **Related Terms**: Cross-references to related concepts
+
+## File Structure
+
+Registry files are located in `registry/` and organized by type:
+
+* `sizes.json` - Size scale values (xs, s, m, l, xl, etc.)
+* `states.json` - Interaction states (default, hover, focus, etc.)
+* `variants.json` - Color and style variants (accent, negative, primary, etc.)
+* `anatomy-terms.json` - Component anatomy parts (edge, visual, text, icon, etc.)
+* `components.json` - Spectrum component names
+* `scale-values.json` - Numeric scale values (50, 75, 100, 200, etc.)
+* `categories.json` - Component categories
+* `platforms.json` - Platform names (desktop, mobile, web, iOS, Android)
+
+## Writing Definitions
+
+Follow the [Spectrum Naming and Definition Writing Guide](https://wiki.corp.adobe.com/display/AdobeDesign/Spectrum+Design+System%3A+Naming+and+definition+writing+guide) methodology:
+
+### 1. Superordinate
+
+The higher-level category or class this term belongs to. This provides context for the reader.
+
+**Examples**:
+
+* "interaction state" for states like hover or focus
+* "size value" for size scales
+* "user interface component" for components
+* "design token" for token-related terms
+
+### 2. Description
+
+A clear, concise explanation of what the term is and how it differs from related concepts.
+
+**Good example**:
+
+> "The state when a component receives focus through keyboard navigation, indicating it will respond to keyboard input"
+
+**Bad example**:
+
+> "When you tab to something"
+
+### 3. Essential Characteristics
+
+Key features that distinguish this term from similar concepts. Use bullet points for clarity.
+
+**Example for "keyboard-focus"**:
+
+* Specifically indicates focus achieved through keyboard interaction (Tab, arrow keys)
+* Requires prominent visual indicator for accessibility (WCAG 2.4.7)
+* Different from generic focus to support :focus-visible patterns
+* Critical for keyboard-only users to understand their current position
+
+## JSON Structure
+
+### Basic Entry (Minimum Required)
+
+```json
+{
+  "id": "unique-identifier",
+  "label": "Human Readable Label",
+  "description": "Brief description of the term",
+  "usedIn": ["tokens", "component-schemas"]
+}
+```
+
+### Enhanced Entry (Full Glossary)
+
+```json
+{
+  "id": "keyboard-focus",
+  "label": "Keyboard Focus",
+  "aliases": ["keyboard focus"],
+  "description": "Focused via keyboard navigation",
+  "usedIn": ["tokens", "component-options", "component-schemas"],
+  
+  "definition": {
+    "superordinate": "interaction state",
+    "description": "The state when a component receives focus through keyboard navigation",
+    "essentialCharacteristics": [
+      "Specifically indicates focus achieved through keyboard interaction",
+      "Requires prominent visual indicator for accessibility",
+      "Different from generic focus to support :focus-visible patterns"
+    ]
+  },
+  
+  "platforms": {
+    "web": {
+      "term": "keyboard-focus",
+      "notes": "Often implemented with :focus-visible pseudo-class",
+      "reference": "https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-visible"
+    },
+    "iOS": {
+      "term": "focused",
+      "notes": "UIFocusSystem for keyboard and pointer navigation",
+      "reference": "UIFocusSystem"
+    }
+  },
+  
+  "terminology": {
+    "conceptType": "term",
+    "namingRationale": "Distinguishes keyboard-based focus from programmatic focus",
+    "alternatives": ["tab-focus", "keyboard-navigated"]
+  },
+  
+  "sources": [
+    {
+      "type": "industry-standard",
+      "reference": "WCAG 2.4.7 Focus Visible",
+      "url": "https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html",
+      "date": "2025-01-12"
+    }
+  ],
+  
+  "governance": {
+    "owner": "Spectrum Core Team",
+    "reviewDate": "2025-01-12",
+    "status": "approved"
+  },
+  
+  "relatedTerms": ["focus", "default", "hover"]
+}
+```
+
+## Field Reference
+
+### Required Fields
+
+| Field   | Type   | Description                    |
+| ------- | ------ | ------------------------------ |
+| `id`    | string | Unique identifier (kebab-case) |
+| `label` | string | Human-readable label           |
+
+### Optional Fields
+
+| Field              | Type                  | Description                                                |
+| ------------------ | --------------------- | ---------------------------------------------------------- |
+| `aliases`          | array                 | Alternative names or spellings                             |
+| `description`      | string                | Brief description                                          |
+| `default`          | boolean               | Whether this is the default value                          |
+| `deprecated`       | boolean               | Whether this value is deprecated                           |
+| `usedIn`           | array                 | Where this value is used (tokens, component-schemas, etc.) |
+| `category`         | string                | Category or grouping                                       |
+| `value`            | string/number/boolean | Actual value (if different from id)                        |
+| `documentationUrl` | string                | URL to documentation                                       |
+
+### Enhanced Fields (Glossary)
+
+| Field          | Type   | Description                                                                  |
+| -------------- | ------ | ---------------------------------------------------------------------------- |
+| `definition`   | object | Structured definition (superordinate, description, essentialCharacteristics) |
+| `platforms`    | object | Platform-specific terminology and notes                                      |
+| `terminology`  | object | Classification and naming rationale                                          |
+| `sources`      | array  | References to source documentation                                           |
+| `governance`   | object | Ownership and review metadata                                                |
+| `relatedTerms` | array  | IDs of related terms                                                         |
+
+## Concept Types
+
+From the Spectrum Naming Guide:
+
+* **word**: Fundamental building block with multiple possible meanings
+* **term**: Word or phrase with precise meaning in a specific domain
+* **name**: Identifier that distinguishes one thing from another (proper noun)
+* **concept**: Abstract idea that words/terms/names represent
+
+## Source Types
+
+* **wiki**: Internal Spectrum wiki pages
+* **industry-standard**: W3C, WCAG, platform specifications
+* **platform-standard**: Apple HIG, Material Design, etc.
+* **internal-doc**: Internal Adobe documentation
+* **research**: User research or design research
+
+## Governance Status
+
+* **draft**: Work in progress, not yet reviewed
+* **review**: Under review by stakeholders
+* **approved**: Reviewed and approved for use
+* **deprecated**: No longer recommended (use `replacedBy` field)
+
+## Workflow
+
+### Adding a New Term
+
+1. **Research**: Understand the concept thoroughly
+2. **Write Definition**: Follow the naming guide methodology
+3. **Check References**: Validate against industry standards and platform docs
+4. **Add Entry**: Create JSON entry with all required fields
+5. **Validate**: Run `pnpm validate` to check schema compliance
+6. **Test**: Run `pnpm test` to ensure no regressions
+7. **Create PR**: Submit for review with changeset
+
+### Updating an Existing Term
+
+1. **Load Term**: Find the term in the appropriate registry file
+2. **Update Fields**: Make necessary changes
+3. **Update Governance**: Update `reviewDate` and `owner` if needed
+4. **Validate**: Run validation and tests
+5. **Create PR**: Submit for review with changeset explaining changes
+
+### Deprecating a Term
+
+1. **Set Deprecated**: Add `"deprecated": true`
+2. **Add Replacement**: Set `governance.replacedBy` to new term ID
+3. **Update Status**: Set `governance.status` to `"deprecated"`
+4. **Document Reason**: Add note in PR description
+5. **Create Changeset**: Document the deprecation
+
+## Best Practices
+
+### Naming
+
+* Use kebab-case for IDs
+* Be descriptive but concise
+* Follow industry standards when they exist
+* Avoid metaphorical or fanciful names
+* Name for the action, not the appearance
+
+### Definitions
+
+* Start with the superordinate to set context
+* Explain what it is AND how it differs from similar concepts
+* Use essential characteristics to highlight unique features
+* Write for both humans and AI systems
+* Avoid circular definitions
+
+### Platform Variations
+
+* Document when platforms use different terminology
+* Include platform-specific implementation notes
+* Link to official platform documentation
+* Help designers understand cross-platform differences
+
+### Cross-References
+
+* Link to related terms with `relatedTerms` array
+* Use term IDs, not labels
+* Bi-directional relationships are ideal but not required
+* Help users discover related concepts
+
+## Validation
+
+Run validation before submitting:
+
+```bash
+# Validate all registry files
+pnpm validate
+
+# Run test suite
+pnpm test
+```
+
+The validation script checks:
+
+* JSON schema compliance
+* No duplicate IDs
+* No duplicate aliases
+* Only one default value per registry
+* Valid relatedTerms references
+* Valid governance.replacedBy references
+
+## Questions?
+
+For questions or feedback:
+
+* Slack: #spectrum\_dna
+* Content Strategists: Jess Sattell, Kari Brookmyer
+* GitHub: [Spectrum Design Data Discussions](https://github.com/adobe/spectrum-design-data/discussions)
+
+## Related Resources
+
+* [Spectrum Naming and Definition Writing Guide](https://wiki.corp.adobe.com/display/AdobeDesign/Spectrum+Design+System%3A+Naming+and+definition+writing+guide)
+* [Spectrum Tokens Wiki](https://wiki.corp.adobe.com/display/AdobeDesign/Spectrum+tokens)
+* [Design System Registry Package README](README.md)
+* [RFC: Spectrum Design System Glossary](https://github.com/adobe/spectrum-design-data/discussions/661)

package/CHANGELOG.md

@@ -0,0 +1,23 @@
+# @adobe/design-system-registry
+
+## 0.0.0-layout-20260209174611
+
+### Patch Changes
+
+- Added layout tokens and updated token terminology
+
+## 1.1.0
+
+### Minor Changes
+
+- [#660](https://github.com/adobe/spectrum-design-data/pull/660) [`4051014`](https://github.com/adobe/spectrum-design-data/commit/4051014951c5c68c01b69be5ee156b4fc8fe98ed) Thanks [@GarthDB](https://github.com/GarthDB)! - Add Design System Registry package providing a single source of truth for
+  terminology used across Spectrum tokens, component schemas, and anatomy.
+  Includes registries for sizes, states, variants, anatomy terms, components,
+  scale values, categories, and platforms with JSON schema validation and
+  comprehensive tests.
+
+## 1.0.0
+
+### Minor Changes
+
+- Initial release of Design System Registry package

package/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+that You distribute, all copyright, patent, trademark, and
+attribution notices from the Source form of the Work,
+excluding those notices that do not pertain to any part of
+the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must
+include a readable copy of the attribution notices contained
+within such NOTICE file, excluding those notices that do not
+pertain to any part of the Derivative Works, in at least one
+of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or,
+within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and
+do not modify the License. You may add Your own attribution
+notices within Derivative Works that You distribute, alongside
+or as an addendum to the NOTICE text from the Work, provided
+that such additional attribution notices cannot be construed
+as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following
+boilerplate notice, with the fields enclosed by brackets "{}"
+replaced with your own identifying information. (Don't include
+the brackets!)  The text should be enclosed in the appropriate
+comment syntax for the file format. We also recommend that a
+file or class name and description of purpose be included on the
+same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+Copyright 2017 Amazon.com, Inc. or its affiliates. All Rights Reserved.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.