style-dictionary 3.7.2 → 3.8.0

package/examples/advanced/custom-file-header/node_modules/snake-case/dist.es2015/index.spec.js

@@ -1,23 +0,0 @@
-import { snakeCase } from ".";
-var TEST_CASES = [
-    ["", ""],
-    ["_id", "id"],
-    ["test", "test"],
-    ["test string", "test_string"],
-    ["Test String", "test_string"],
-    ["TestV2", "test_v2"],
-    ["version 1.2.10", "version_1_2_10"],
-    ["version 1.21.0", "version_1_21_0"],
-];
-describe("snake case", function () {
-    var _loop_1 = function (input, result) {
-        it(input + " -> " + result, function () {
-            expect(snakeCase(input)).toEqual(result);
-        });
-    };
-    for (var _i = 0, TEST_CASES_1 = TEST_CASES; _i < TEST_CASES_1.length; _i++) {
-        var _a = TEST_CASES_1[_i], input = _a[0], result = _a[1];
-        _loop_1(input, result);
-    }
-});
-//# sourceMappingURL=index.spec.js.map

package/examples/advanced/custom-file-header/node_modules/snake-case/dist.es2015/index.spec.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.spec.js","sourceRoot":"","sources":["../src/index.spec.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,GAAG,CAAC;AAE9B,IAAM,UAAU,GAAuB;IACrC,CAAC,EAAE,EAAE,EAAE,CAAC;IACR,CAAC,KAAK,EAAE,IAAI,CAAC;IACb,CAAC,MAAM,EAAE,MAAM,CAAC;IAChB,CAAC,aAAa,EAAE,aAAa,CAAC;IAC9B,CAAC,aAAa,EAAE,aAAa,CAAC;IAC9B,CAAC,QAAQ,EAAE,SAAS,CAAC;IACrB,CAAC,gBAAgB,EAAE,gBAAgB,CAAC;IACpC,CAAC,gBAAgB,EAAE,gBAAgB,CAAC;CACrC,CAAC;AAEF,QAAQ,CAAC,YAAY,EAAE;4BACT,KAAK,EAAE,MAAM;QACvB,EAAE,CAAI,KAAK,YAAO,MAAQ,EAAE;YAC1B,MAAM,CAAC,SAAS,CAAC,KAAK,CAAC,CAAC,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;QAC3C,CAAC,CAAC,CAAC;;IAHL,KAA8B,UAAU,EAAV,yBAAU,EAAV,wBAAU,EAAV,IAAU;QAA7B,IAAA,qBAAe,EAAd,KAAK,QAAA,EAAE,MAAM,QAAA;gBAAb,KAAK,EAAE,MAAM;KAIxB;AACH,CAAC,CAAC,CAAC","sourcesContent":["import { snakeCase } from \".\";\n\nconst TEST_CASES: [string, string][] = [\n  [\"\", \"\"],\n  [\"_id\", \"id\"],\n  [\"test\", \"test\"],\n  [\"test string\", \"test_string\"],\n  [\"Test String\", \"test_string\"],\n  [\"TestV2\", \"test_v2\"],\n  [\"version 1.2.10\", \"version_1_2_10\"],\n  [\"version 1.21.0\", \"version_1_21_0\"],\n];\n\ndescribe(\"snake case\", () => {\n  for (const [input, result] of TEST_CASES) {\n    it(`${input} -> ${result}`, () => {\n      expect(snakeCase(input)).toEqual(result);\n    });\n  }\n});\n"]}

package/examples/advanced/custom-file-header/node_modules/snake-case/package.json

@@ -1,90 +0,0 @@
-{
-  "name": "snake-case",
-  "version": "3.0.4",
-  "description": "Transform into a lower case string with underscores between words",
-  "main": "dist/index.js",
-  "typings": "dist/index.d.ts",
-  "module": "dist.es2015/index.js",
-  "sideEffects": false,
-  "jsnext:main": "dist.es2015/index.js",
-  "files": [
-    "dist/",
-    "dist.es2015/",
-    "LICENSE"
-  ],
-  "scripts": {
-    "lint": "tslint \"src/**/*\" --project tsconfig.json",
-    "build": "rimraf dist/ dist.es2015/ && tsc && tsc -P tsconfig.es2015.json",
-    "specs": "jest --coverage",
-    "test": "npm run build && npm run lint && npm run specs",
-    "size": "size-limit",
-    "prepare": "npm run build"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git://github.com/blakeembrey/change-case.git"
-  },
-  "keywords": [
-    "snake",
-    "case",
-    "underscore",
-    "lower",
-    "convert",
-    "transform",
-    "identifier",
-    "python"
-  ],
-  "author": {
-    "name": "Blake Embrey",
-    "email": "hello@blakeembrey.com",
-    "url": "http://blakeembrey.me"
-  },
-  "license": "MIT",
-  "bugs": {
-    "url": "https://github.com/blakeembrey/change-case/issues"
-  },
-  "homepage": "https://github.com/blakeembrey/change-case/tree/master/packages/snake-case#readme",
-  "size-limit": [
-    {
-      "path": "dist/index.js",
-      "limit": "400 B"
-    }
-  ],
-  "jest": {
-    "roots": [
-      "<rootDir>/src/"
-    ],
-    "transform": {
-      "\\.tsx?$": "ts-jest"
-    },
-    "testRegex": "(/__tests__/.*|\\.(test|spec))\\.(tsx?|jsx?)$",
-    "moduleFileExtensions": [
-      "ts",
-      "tsx",
-      "js",
-      "jsx",
-      "json",
-      "node"
-    ]
-  },
-  "publishConfig": {
-    "access": "public"
-  },
-  "dependencies": {
-    "dot-case": "^3.0.4",
-    "tslib": "^2.0.3"
-  },
-  "devDependencies": {
-    "@size-limit/preset-small-lib": "^2.2.1",
-    "@types/jest": "^24.0.23",
-    "@types/node": "^12.12.14",
-    "jest": "^24.9.0",
-    "rimraf": "^3.0.0",
-    "ts-jest": "^24.2.0",
-    "tslint": "^5.20.1",
-    "tslint-config-prettier": "^1.18.0",
-    "tslint-config-standard": "^9.0.0",
-    "typescript": "^4.1.2"
-  },
-  "gitHead": "76a21a7f6f2a226521ef6abd345ff309cbd01fb0"
-}

package/examples/advanced/custom-file-header/node_modules/style-dictionary/LICENSE

@@ -1,201 +0,0 @@
-                                 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.

package/examples/advanced/custom-file-header/node_modules/style-dictionary/NOTICE

@@ -1,2 +0,0 @@
-Style Dictionary
-Copyright 2017 Amazon.com, Inc. or its affiliates. All Rights Reserved.

package/examples/advanced/custom-file-header/node_modules/style-dictionary/README.md

@@ -1,309 +0,0 @@
-<pre>
-<a href="https://amzn.github.io/style-dictionary/#/version_3">What's new in Style Dictionary 3.0!</a>
-</pre>
-
-<img src="docs/assets/logo.png" alt="Style Dictionary logo and mascot" title="&quot;Pascal&quot;" width="100" align="right" />
-
-[![npm version](https://img.shields.io/npm/v/style-dictionary.svg?style=flat-square)](https://badge.fury.io/js/style-dictionary)
-![license](https://img.shields.io/npm/l/style-dictionary.svg?style=flat-square)
-[![PRs welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](https://github.com/amzn/style-dictionary/blob/main/CONTRIBUTING.md#submitting-pull-requests)
-[![GitHub Workflow Status](https://img.shields.io/github/workflow/status/amzn/style-dictionary/Test?style=flat-square)](https://github.com/amzn/style-dictionary/actions/workflows/test.yml)
-[![downloads](https://img.shields.io/npm/dm/style-dictionary.svg?style=flat-square)](https://www.npmjs.com/package/style-dictionary)
-
-# Style Dictionary
-> *Style once, use everywhere.*
-
-A Style Dictionary uses design tokens to define styles once and use those styles on any platform or language. It provides a single place to create and edit your styles, and exports these tokens to all the places you need - iOS, Android, CSS, JS, HTML, sketch files, style documentation, etc. It is available as a CLI through npm, but can also be used like any normal node module if you want to extend its functionality.
-
-When you are managing user experiences, it can be quite challenging to keep styles consistent and synchronized across multiple development platforms and devices. At the same time, designers, developers, PMs and others must be able to have consistent and up-to-date style documentation to enable effective work and communication. Even then, mistakes inevitably happen and the design may not be implemented accurately. Style Dictionary solves this by automatically generating style definitions across all platforms from a single source - removing roadblocks, errors, and inefficiencies across your workflow.
-
-For detailed usage head to https://amzn.github.io/style-dictionary
-
-## Watch the Demo on Youtube
-[![Watch the video](/docs/assets/fake_player.png)](http://youtu.be/1HREvonfqhY)
-
-## Experiment in the playground
-Try the browser-based Style Dictionary playground: [https://www.style-dictionary-play.dev/](https://www.style-dictionary-play.dev/), built by the folks at [\<div\>RIOTS](https://divriots.com/).
-
-## Contents
-* [Installation](#installation)
-* [Usage](#usage)
-* [Example](#example)
-* [Quick Start](#quick-start)
-* [Design Tokens](#design-tokens)
-* [Extending](#extending)
-* [Contributing](#contributing)
-* [License](#license)
-
-
-## Installation
-*Note that you must have node (and npm) installed.*
-
-If you want to use the CLI, you can install it globally via npm:
-```bash
-$ npm install -g style-dictionary
-```
-
-Or you can install it like a normal npm dependency. This is a build tool and you are most likely going to want to save it as a dev dependency:
-```bash
-$ npm install -D style-dictionary
-```
-
-If you want to install it with yarn:
-```bash
-$ yarn add style-dictionary --dev
-```
-
-## Usage
-### CLI
-```bash
-$ style-dictionary build
-```
-Call this in the root directory of your project. The only thing needed is a `config.json` file. There are also arguments:
-
-| Flag | Short Flag | Description |
-| --- | --- | --- |
-| --config \[path\] | -c | Set the config file to use. Must be a .json file |
-| --platform \[platform\] | -p | Only build a specific platform defined in the config file. |
-| --help | -h | Display help content |
-| --version | -v | Display the version |
-
-### Node
-You can also use the style dictionary build system in node if you want to [extend](#extending) the functionality or use it in another build system like Grunt or Gulp.
-```javascript
-const StyleDictionary = require('style-dictionary').extend('config.json');
-
-StyleDictionary.buildAllPlatforms();
-```
-
-The `.extend()` method is an overloaded method that can also take an object with the configuration in the same format as a config.json file.
-```javascript
-const StyleDictionary = require('style-dictionary').extend({
-  source: ['tokens/**/*.json'],
-  platforms: {
-    scss: {
-      transformGroup: 'scss',
-      buildPath: 'build/',
-      files: [{
-        destination: 'variables.scss',
-        format: 'scss/variables'
-      }]
-    }
-    // ...
-  }
-});
-
-StyleDictionary.buildAllPlatforms();
-```
-
-## Example
-[Take a look at some of our examples](examples/)
-
-A style dictionary is a collection of design tokens, key/value pairs that describe stylistic attributes like colors, sizes, icons, motion, etc. A style dictionary defines these design tokens in JSON or Javascript files, and can also include static assets like images and fonts. Here is a basic example of what the package structure can look like:
-
-```
-├── config.json
-├── tokens/
-│   ├── size/
-│       ├── font.json
-│   ├── color/
-│       ├── font.json
-│   ...
-├── assets/
-│   ├── fonts/
-│   ├── images/
-```
-
-### config.json
-This tells the style dictionary build system how and what to build. The default file path is `config.json` or `config.js` in the root of the project, but you can name it whatever you want by passing in the `--config` flag to the [CLI](https://amzn.github.io/style-dictionary/#/using_the_cli).
-
-```json
-{
-  "source": ["tokens/**/*.json"],
-  "platforms": {
-    "scss": {
-      "transformGroup": "scss",
-      "buildPath": "build/",
-      "files": [{
-        "destination": "scss/_variables.scss",
-        "format": "scss/variables"
-      }]
-    },
-    "android": {
-      "transformGroup": "android",
-      "buildPath": "build/android/",
-      "files": [{
-        "destination": "font_dimens.xml",
-        "format": "android/fontDimens"
-      }]
-    }
-  }
-}
-```
-
-| Attribute | Type | Description |
-| :--- | :--- | :--- |
-| source | Array | An array of file path [globs](https://github.com/isaacs/node-glob) to design token files. Style Dictionary will do a deep merge of all of the token files, allowing you to organize your files files however you want. |
-| include | Array | An array of file path [globs](https://github.com/isaacs/node-glob) to design token files that contain default styles. The Style Dictionary uses this as a base collection of tokens. The tokens found using the "source" attribute will overwrite tokens found using include. |
-| platforms | Object | Sets of platform files to be built. |
-| platform.transformGroup | String (optional) | Apply a group of transforms to the tokens, must either define this or `transforms`. |
-| platform.transforms | Array (optional) | Transforms to apply sequentially to all tokens. Can be a built-in one or you can create your own. |
-| platform.buildPath | String (optional) | Base path to build the files, must end with a trailing slash. |
-| platform.files | Array (optional) | Files to be generated for this platform. |
-| platform.file.destination | String (optional) | Location to build the file, will be appended to the buildPath. |
-| platform.file.format | String (optional) | Format used to generate the file. Can be a built-in one or you can create your own. [More on formats](https://amzn.github.io/style-dictionary/#/formats) |
-| platform.file.options | Object (optional) | A set of extra options associated with the file. |
-| platform.file.options.showFileHeader | Boolean | If the generated file should have a "Do not edit + Timestamp" header (where the format supports it). By default is "true". |
-
-### Design Tokens
-
-```json
-{
-  "size": {
-    "font": {
-      "small" : { "value": "10px" },
-      "medium": { "value": "16px" },
-      "large" : { "value": "24px" },
-      "base"  : { "value": "{size.font.medium.value}" }
-    }
-  }
-}
-```
-
-Here we are creating some basic font size design tokens. The style definition size.font.small.value is "10px" for example. The style definition size.font.base.value is automatically aliased to the value found in size.font.medium.value and both of those resolve to "16px".
-
-Now what the style dictionary build system will do with this information is convert it to different formats, enabling these values to be used in any type of codebase. From this one file you can generate any number of files like:
-
-```scss
-$size-font-small: 10px;
-$size-font-medium: 16px;
-$size-font-large: 24px;
-$size-font-base: 16px;
-```
-
-```xml
-<dimen name="font-small">10sp</dimen>
-<dimen name="font-medium">16sp</dimen>
-<dimen name="font-large">24sp</dimen>
-<dimen name="font-base">16sp</dimen>
-```
-
-```objc
-float const SizeFontSmall = 10.00f;
-float const SizeFontMedium = 16.00f;
-float const SizeFontLarge = 24.00f;
-float const SizeFontBase = 16.00f;
-```
-
-
-## Quick Start
-
-The style dictionary framework comes with some example code to get you stared. Install the node module globally, create a directory and `cd` into it.
-
-```
-$ npm i -g style-dictionary
-$ mkdir MyStyleDictionary
-$ cd MyStyleDictionary
-```
-
-Now run:
-
-```
-$ style-dictionary init basic
-```
-
-This command will copy over the example files found in [example](examples/) in this repo. Now you have an example project set up. You can make changes to the style dictionary and rebuild the project by running:
-
-```
-$ style-dictionary build
-```
-
-Take a look at the documentation for the example code.
-
-
-## Design Tokens
-
-A design token is an attribute to describe something visually. It is atomic (it cannot be broken down further). Design tokens have a name, a value, and optional attributes or metadata. The name of a token can be anything, but we have a proposed naming structure that we find works really well in the next section.
-
-### Category/Type/Item Structure
-
-While not exactly necessary, we feel this classification structure of design tokens makes the most sense semantically. Design tokens can be organized into a hierarchical tree structure with the top level, category, defining the primitive nature of the token. For example, we have the color category and every token underneath is always a color. As you proceed down the tree to type, item, sub-item, and state, you get more specific about what that color is. Is it a background color, a text color, or a border color? What kind of text color is it? You get the point. Now you can structure your token json files like simple objects:
-
-```
-{
-  "size": {
-    "font": {
-      "base":  { "value": "16" },
-      "large": { "value": "20" }
-    }
-  }
-}
-```
-
-The CTI is implicit in the structure, the category and type is 'size' and 'font', and there are 2 tokens 'base' and 'large'.
-
-Structuring design tokens in this manner gives us consistent naming and accessing of these tokens. You don't need to remember if it is button_color_error or error_button_color, it is color_background_button_error!
-
-You can organize and name your design tokens however you want, there are no restrictions. But we have a good amount of helpers if you do use this structure, like the 'attribute/cti' transform which adds attributes to the token of its CTI based on the path in the object. There are a lot of name transforms as well for when you want a flat structure like for Sass variables.
-
-Also, the CTI structure provides a good mechanism to target transforms for specific kinds of tokens. All of the transforms provided by the framework use the CTI of a token to know if it should be applied. For instance, the 'color/hex' transform only applies to tokens of the category 'color'.
-
-You can also add a _comment_ to a design token:
-
-```
-{
-  "size": {
-    "font": {
-      "base":  {
-        "value": "16",
-        "comment": "the base size of the font"
-      },
-      "large": {
-        "value": "20",
-        "comment": "the large size of the font"
-      }
-    }
-  }
-}
-```
-
-The comment  will appear in the output files, where relevant or the output format supports comments.
-
-
-## Extending
-
-The style dictionary build system is made to be extended. We don't know exactly how everyone will want to use style dictionaries in their project, which is why you can create custom transforms and formats.
-
-```javascript
-const StyleDictionary = require('style-dictionary').extend('config.json');
-
-StyleDictionary.registerTransform({
-  name: 'time/seconds',
-  type: 'value',
-  matcher: function(prop) {
-    return prop.attributes.category === 'time';
-  },
-  transformer: function(prop) {
-    return (parseInt(prop.original.value) / 1000).toString() + 's';
-  }
-});
-
-StyleDictionary.buildAllPlatforms();
-```
-
-For more information on creating your own transforms and formats, take a look at our [docs](https://amzn.github.io/style-dictionary/).
-
-## Mascot
-
-The mascot for Style Dictionary is ["Pascal"](https://github.com/amzn/style-dictionary/issues/97) the chameleon (seen below). You can also find them blending in as the logo throughout the documentation.
-
-<img src="docs/assets/logo.png" alt="Style Dictionary logo and mascot" title="&quot;Pascal&quot;" width="240" />
-
-## Contributing
-
-Please help make this framework better. For more information take a look at [CONTRIBUTING.md](CONTRIBUTING.md)
-
-
-## License
-
-[Apache 2.0](LICENSE)