{"id":24409009,"url":"https://github.com/codesandtags/design-tokens-studio-poc","last_synced_at":"2026-04-27T13:35:31.819Z","repository":{"id":222565260,"uuid":"757746078","full_name":"codesandtags/design-tokens-studio-poc","owner":"codesandtags","description":"This PoC covers how to use a local server to sync tokens.","archived":false,"fork":false,"pushed_at":"2024-02-15T00:27:47.000Z","size":192,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-12-30T22:41:33.662Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/codesandtags.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2024-02-14T22:19:17.000Z","updated_at":"2024-02-15T00:27:51.000Z","dependencies_parsed_at":null,"dependency_job_id":"58a167ab-6663-446f-a0c2-97b96fe3aa54","html_url":"https://github.com/codesandtags/design-tokens-studio-poc","commit_stats":null,"previous_names":["codesandtags/design-tokens-studio-poc"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/codesandtags/design-tokens-studio-poc","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/codesandtags%2Fdesign-tokens-studio-poc","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/codesandtags%2Fdesign-tokens-studio-poc/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/codesandtags%2Fdesign-tokens-studio-poc/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/codesandtags%2Fdesign-tokens-studio-poc/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/codesandtags","download_url":"https://codeload.github.com/codesandtags/design-tokens-studio-poc/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/codesandtags%2Fdesign-tokens-studio-poc/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":32339290,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-04-26T23:26:28.701Z","status":"online","status_checked_at":"2026-04-27T02:00:06.769Z","response_time":128,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-01-20T05:53:44.856Z","updated_at":"2026-04-27T13:35:31.814Z","avatar_url":"https://github.com/codesandtags.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Design Tokens Studio PoC\n\nThis PoC is because I was inspired by my friend Jyrmid, so I wanted to create the PoC by myself and also share a functional approach with the world.\n\n## Motivation\n\nNowadays the [Design Tokens](https://thedesignsystem.guide/design-tokens) are very common within the UI/UX design and Frontend Community to have a standard way for naming components and UI/UX elements. However, keeping a unique source of truth is difficult and we do not want to make difficult the cognitive load for UI/UX designer nor developers.\n\n## Goal\n\nDefine a simple approach to sync the `Design Tokens` created with Tokens Studio in **Figma**. These tokens can be used by developers and other designers.\n\n## Key Considerations\n\n- Designer should not download any tool / local development environment.\n- Tokens should be centralized to keep a unique source of information shared between designers and developers\n- The [schema used by Tokens Studio](https://schemas.tokens.studio/latest/tokens-schema.json) should be the same used by the REST API.\n\n## Proposal\n\n### Using JSON Server to store the tokens\n\n- Using `json-server` to create a simple REST API to store the tokens in a JSON file.\n- Using a [Generic Versioned Storage Sync](https://docs.tokens.studio/sync/generic-storage) to sync the values from Figma to the REST API.\n- Tokens should be stored in a JSON file when `Apply to selection` button is clicked in Figma.\n\n### Using Figma Tokens Generic Storage example repository\n\n- Using the [Figma Tokens Generic Storage](https://github.com/SorsOps/figma-tokens-generic-storage-example/tree/main) repository to create a simple example to sync the tokens from Figma to the REST API.\n\n## Results\n\n### Using JSON Server to store the tokens\n\n#### Pros\n\n- Using this options is quite easy to create a simple REST API to store the tokens in a JSON file.\n\n#### Cons\n\n- One drawback is that if the path is not defined from the begining, the `json-server` will not be able to store the tokens in the JSON file.\n- There are some errors when trying to sync the tokens from Figma to the REST API.\n- Data is easily lost if the server is restarted.\n- Data is stored with spaces which it takes more space in the JSON file.\n\n### Using Figma Tokens Generic Storage example repository\n\n#### Pros\n\n- This approach uses a db in SQLite to store the tokens.\n- Data is persisted if the server is restarted.\n\n#### Cons\n\n- The `figma-tokens-generic-storage-example` repository is not updated and it requires some changes with the latest version of the `tokens-schema` and dependencies.\n\n## Conclusion\n\nThe PoC was successful, however, the `json-server` approach is not the best option to store the tokens. The `figma-tokens-generic-storage-example` repository is a better option to store the tokens, but it requires some changes to work with the latest version of the `tokens-schema` and dependencies.\n\n## Next Steps\n\n- [ ] Create a Docker Image with the changes to expose the REST API to store the tokens.\n- [ ] Create a deployment pipeline to deploy the REST API to store the tokens in a - cloud provider.\n- [ ] Document the steps to sync the tokens from Figma to the REST API.\n- [ ] Write a proper article to share this approach with the world.\n\n## References\n\n- https://tokens.studio/\n- https://configurator.tokens.studio/\n- https://medium.com/@ian.lawton/a-simple-design-token-storage-server-for-figma-token-studio-3a9ba74aefb5\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcodesandtags%2Fdesign-tokens-studio-poc","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcodesandtags%2Fdesign-tokens-studio-poc","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcodesandtags%2Fdesign-tokens-studio-poc/lists"}