diff --git a/.astro/types.d.ts b/.astro/types.d.ts
index f964fe0cf..03d7cc43f 100644
--- a/.astro/types.d.ts
+++ b/.astro/types.d.ts
@@ -1 +1,2 @@
///
+///
\ No newline at end of file
diff --git a/public/images/brand-square.png b/public/img/brand-square.png
similarity index 100%
rename from public/images/brand-square.png
rename to public/img/brand-square.png
diff --git a/public/images/brand.png b/public/img/brand.png
similarity index 100%
rename from public/images/brand.png
rename to public/img/brand.png
diff --git a/public/images/brand.svg b/public/img/brand.svg
similarity index 100%
rename from public/images/brand.svg
rename to public/img/brand.svg
diff --git a/public/images/cursors/add.svg b/public/img/cursors/add.svg
similarity index 100%
rename from public/images/cursors/add.svg
rename to public/img/cursors/add.svg
diff --git a/public/images/cursors/remove.svg b/public/img/cursors/remove.svg
similarity index 100%
rename from public/images/cursors/remove.svg
rename to public/img/cursors/remove.svg
diff --git a/public/images/default-avatar.png b/public/img/default-avatar.png
similarity index 100%
rename from public/images/default-avatar.png
rename to public/img/default-avatar.png
diff --git a/public/images/features/in-progress.png b/public/img/features/in-progress.png
similarity index 100%
rename from public/images/features/in-progress.png
rename to public/img/features/in-progress.png
diff --git a/public/images/gifs/bot.gif b/public/img/gifs/bot.gif
similarity index 100%
rename from public/images/gifs/bot.gif
rename to public/img/gifs/bot.gif
diff --git a/public/images/gifs/party-popper.gif b/public/img/gifs/party-popper.gif
similarity index 100%
rename from public/images/gifs/party-popper.gif
rename to public/img/gifs/party-popper.gif
diff --git a/public/images/gifs/rocket.gif b/public/img/gifs/rocket.gif
similarity index 100%
rename from public/images/gifs/rocket.gif
rename to public/img/gifs/rocket.gif
diff --git a/public/images/gifs/star.gif b/public/img/gifs/star.gif
similarity index 100%
rename from public/images/gifs/star.gif
rename to public/img/gifs/star.gif
diff --git a/public/images/gifs/starstruck.gif b/public/img/gifs/starstruck.gif
similarity index 100%
rename from public/images/gifs/starstruck.gif
rename to public/img/gifs/starstruck.gif
diff --git a/public/images/gifs/sunglasses.gif b/public/img/gifs/sunglasses.gif
similarity index 100%
rename from public/images/gifs/sunglasses.gif
rename to public/img/gifs/sunglasses.gif
diff --git a/public/images/gifs/wave.gif b/public/img/gifs/wave.gif
similarity index 100%
rename from public/images/gifs/wave.gif
rename to public/img/gifs/wave.gif
diff --git a/public/images/graph.svg b/public/img/graph.svg
similarity index 100%
rename from public/images/graph.svg
rename to public/img/graph.svg
diff --git a/public/images/hackernews.svg b/public/img/hackernews.svg
similarity index 100%
rename from public/images/hackernews.svg
rename to public/img/hackernews.svg
diff --git a/public/images/icons8-wand.gif b/public/img/icons8-wand.gif
similarity index 100%
rename from public/images/icons8-wand.gif
rename to public/img/icons8-wand.gif
diff --git a/public/images/og-img.png b/public/img/og-img.png
similarity index 100%
rename from public/images/og-img.png
rename to public/img/og-img.png
diff --git a/public/images/partners/ambassador-graphic-1.png b/public/img/partners/ambassador-graphic-1.png
similarity index 100%
rename from public/images/partners/ambassador-graphic-1.png
rename to public/img/partners/ambassador-graphic-1.png
diff --git a/public/images/partners/ambassador-graphic-2.png b/public/img/partners/ambassador-graphic-2.png
similarity index 100%
rename from public/images/partners/ambassador-graphic-2.png
rename to public/img/partners/ambassador-graphic-2.png
diff --git a/public/images/partners/apollo-event.jpg b/public/img/partners/apollo-event.jpg
similarity index 100%
rename from public/images/partners/apollo-event.jpg
rename to public/img/partners/apollo-event.jpg
diff --git a/public/images/partners/apollo-learning.jpg b/public/img/partners/apollo-learning.jpg
similarity index 100%
rename from public/images/partners/apollo-learning.jpg
rename to public/img/partners/apollo-learning.jpg
diff --git a/public/images/partners/apollo-workshop.png b/public/img/partners/apollo-workshop.png
similarity index 100%
rename from public/images/partners/apollo-workshop.png
rename to public/img/partners/apollo-workshop.png
diff --git a/public/images/partners/graphql-summit.png b/public/img/partners/graphql-summit.png
similarity index 100%
rename from public/images/partners/graphql-summit.png
rename to public/img/partners/graphql-summit.png
diff --git a/public/images/partners/honeycomb-ebook.jpg b/public/img/partners/honeycomb-ebook.jpg
similarity index 100%
rename from public/images/partners/honeycomb-ebook.jpg
rename to public/img/partners/honeycomb-ebook.jpg
diff --git a/public/images/partners/nginx.png b/public/img/partners/nginx.png
similarity index 100%
rename from public/images/partners/nginx.png
rename to public/img/partners/nginx.png
diff --git a/public/images/partners/spring-tile.png b/public/img/partners/spring-tile.png
similarity index 100%
rename from public/images/partners/spring-tile.png
rename to public/img/partners/spring-tile.png
diff --git a/public/images/partners/zilliz.png b/public/img/partners/zilliz.png
similarity index 100%
rename from public/images/partners/zilliz.png
rename to public/img/partners/zilliz.png
diff --git a/public/images/party.gif b/public/img/party.gif
similarity index 100%
rename from public/images/party.gif
rename to public/img/party.gif
diff --git a/public/images/reddit.svg b/public/img/reddit.svg
similarity index 100%
rename from public/images/reddit.svg
rename to public/img/reddit.svg
diff --git a/public/images/roadmap-editor.jpeg b/public/img/roadmap-editor.jpeg
similarity index 100%
rename from public/images/roadmap-editor.jpeg
rename to public/img/roadmap-editor.jpeg
diff --git a/public/images/system-design.png b/public/img/system-design.png
similarity index 100%
rename from public/images/system-design.png
rename to public/img/system-design.png
diff --git a/public/images/team-promo/contact.png b/public/img/team-promo/contact.png
similarity index 100%
rename from public/images/team-promo/contact.png
rename to public/img/team-promo/contact.png
diff --git a/public/images/team-promo/documentation.png b/public/img/team-promo/documentation.png
similarity index 100%
rename from public/images/team-promo/documentation.png
rename to public/img/team-promo/documentation.png
diff --git a/public/images/team-promo/growth-plans.png b/public/img/team-promo/growth-plans.png
similarity index 100%
rename from public/images/team-promo/growth-plans.png
rename to public/img/team-promo/growth-plans.png
diff --git a/public/images/team-promo/hero-img.png b/public/img/team-promo/hero-img.png
similarity index 100%
rename from public/images/team-promo/hero-img.png
rename to public/img/team-promo/hero-img.png
diff --git a/public/images/team-promo/hero.png b/public/img/team-promo/hero.png
similarity index 100%
rename from public/images/team-promo/hero.png
rename to public/img/team-promo/hero.png
diff --git a/public/images/team-promo/invite-members.png b/public/img/team-promo/invite-members.png
similarity index 100%
rename from public/images/team-promo/invite-members.png
rename to public/img/team-promo/invite-members.png
diff --git a/public/images/team-promo/many-roadmaps.png b/public/img/team-promo/many-roadmaps.png
similarity index 100%
rename from public/images/team-promo/many-roadmaps.png
rename to public/img/team-promo/many-roadmaps.png
diff --git a/public/images/team-promo/onboarding.png b/public/img/team-promo/onboarding.png
similarity index 100%
rename from public/images/team-promo/onboarding.png
rename to public/img/team-promo/onboarding.png
diff --git a/public/images/team-promo/our-roadmaps.png b/public/img/team-promo/our-roadmaps.png
similarity index 100%
rename from public/images/team-promo/our-roadmaps.png
rename to public/img/team-promo/our-roadmaps.png
diff --git a/public/images/team-promo/progress-tracking.png b/public/img/team-promo/progress-tracking.png
similarity index 100%
rename from public/images/team-promo/progress-tracking.png
rename to public/img/team-promo/progress-tracking.png
diff --git a/public/images/team-promo/roadmap-editor.png b/public/img/team-promo/roadmap-editor.png
similarity index 100%
rename from public/images/team-promo/roadmap-editor.png
rename to public/img/team-promo/roadmap-editor.png
diff --git a/public/images/team-promo/sharing-settings.png b/public/img/team-promo/sharing-settings.png
similarity index 100%
rename from public/images/team-promo/sharing-settings.png
rename to public/img/team-promo/sharing-settings.png
diff --git a/public/images/team-promo/skill-gap.png b/public/img/team-promo/skill-gap.png
similarity index 100%
rename from public/images/team-promo/skill-gap.png
rename to public/img/team-promo/skill-gap.png
diff --git a/public/images/team-promo/team-dashboard.png b/public/img/team-promo/team-dashboard.png
similarity index 100%
rename from public/images/team-promo/team-dashboard.png
rename to public/img/team-promo/team-dashboard.png
diff --git a/public/images/team-promo/team-insights.png b/public/img/team-promo/team-insights.png
similarity index 100%
rename from public/images/team-promo/team-insights.png
rename to public/img/team-promo/team-insights.png
diff --git a/public/images/team-promo/update-progress.png b/public/img/team-promo/update-progress.png
similarity index 100%
rename from public/images/team-promo/update-progress.png
rename to public/img/team-promo/update-progress.png
diff --git a/public/images/tns-sm.png b/public/img/tns-sm.png
similarity index 100%
rename from public/images/tns-sm.png
rename to public/img/tns-sm.png
diff --git a/public/images/tns.png b/public/img/tns.png
similarity index 100%
rename from public/images/tns.png
rename to public/img/tns.png
diff --git a/public/images/twitter-img.png b/public/img/twitter-img.png
similarity index 100%
rename from public/images/twitter-img.png
rename to public/img/twitter-img.png
diff --git a/public/pdfs/roadmaps/golang.pdf b/public/pdfs/roadmaps/golang.pdf
index 9dcb35556..3d766c18d 100644
Binary files a/public/pdfs/roadmaps/golang.pdf and b/public/pdfs/roadmaps/golang.pdf differ
diff --git a/public/roadmap-content/cpp.json b/public/roadmap-content/cpp.json
index 25ecce875..61e0deb2e 100644
--- a/public/roadmap-content/cpp.json
+++ b/public/roadmap-content/cpp.json
@@ -68,7 +68,7 @@
},
"ew0AfyadpXPRO0ZY3Z19k": {
"title": "Code Editors / IDEs",
- "description": "Code editors and IDEs are programs specifically designed for editing, managing and writing source code. They offer a wide range of features that make the development process easier and faster. Here's a brief introduction to some of the most popular code editors and IDEs for C++:\n\n* **Visual Studio**: Visual Studio is an Integrated Development Environment (IDE) for Windows, developed by Microsoft. It includes its own integrated compiler known as Microsoft Visual C++ (MSVC).\n \n* **Visual Studio Code (VSCode)**: Visual Studio Code is a popular, free, open-source, and lightweight code editor developed by Microsoft. It offers an extensive library of extensions that enhance functionality for C++ development.\n \n* **Sublime Text**: Sublime Text is a cross-platform text editor that is quite popular among developers due to its speed and minimalist design. It supports C++ with the help of plugins and has a variety of themes and packages available for customization.\n \n* **CLion**: CLion is an Integrated Development Environment (IDE) developed by JetBrains specifically for C and C++ developers. It provides advanced features like code completion, refactoring support, debugging, and more. It's worth noting that CLion is a commercial IDE, and there is no community version available; users are required to purchase a license for usage.\n \n\nThese are just a few examples, and there are many other code editors available, including Atom, Notepad++, and Geany. They all have their features and may suit different developers' needs. Finding the right code editor is often a matter of personal preference and workflow.\n\nTo work with C++ in your chosen code editor, you often need to install some additional tools and add-ons, such as compilers, linters, and debugger support. Make sure to follow the instructions provided in the editor's documentation to set up C++ correctly.\n\nLearn more from the following resources:",
+ "description": "Code editors and IDEs are programs specifically designed for editing, managing and writing source code. They offer a wide range of features that make the development process easier and faster. Here's a brief introduction to some of the most popular code editors and IDEs for C++:\n\n* **Visual Studio**: Visual Studio is an Integrated Development Environment (IDE) for Windows, developed by Microsoft. It includes its own integrated compiler known as Microsoft Visual C++ (MSVC).\n \n* **Visual Studio Code (VSCode)**: Visual Studio Code is a popular, free, open-source, and lightweight code editor developed by Microsoft. It offers an extensive library of extensions that enhance functionality for C++ development.\n \n* **Sublime Text**: Sublime Text is a cross-platform text editor that is quite popular among developers due to its speed and minimalist design. It supports C++ with the help of plugins and has a variety of themes and packages available for customization.\n \n* **CLion**: CLion is an Integrated Development Environment (IDE) developed by JetBrains specifically for C and C++ developers. It provides advanced features like code completion, refactoring support, debugging, and more. It's worth noting that CLion is a commercial IDE, but there is community version available.\n \n\nThese are just a few examples, and there are many other code editors available, including Atom, Notepad++, and Geany. They all have their features and may suit different developers' needs. Finding the right code editor is often a matter of personal preference and workflow.\n\nTo work with C++ in your chosen code editor, you often need to install some additional tools and add-ons, such as compilers, linters, and debugger support. Make sure to follow the instructions provided in the editor's documentation to set up C++ correctly.\n\nLearn more from the following resources:",
"links": [
{
"title": "Using C++ on Linux in VSCode",
diff --git a/public/roadmap-content/design-system.json b/public/roadmap-content/design-system.json
new file mode 100644
index 000000000..6b6c1b22f
--- /dev/null
+++ b/public/roadmap-content/design-system.json
@@ -0,0 +1,982 @@
+{
+ "understand-the-basics@uvnV1IjE8RV-FKDxHntUU.md": {
+ "title": "Understand the Basics",
+ "description": "",
+ "links": []
+ },
+ "4PrkkoZ5fY-oow0O-bVhu": {
+ "title": "What is a Design System?",
+ "description": "A Design System is the single source of truth which groups all the elements that will allow the teams to design, realize and develop a product.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Everything you need to know about Design Systems",
+ "url": "https://uxdesign.cc/everything-you-need-to-know-about-design-systems-54b109851969",
+ "type": "article"
+ },
+ {
+ "title": "Design Systems 101",
+ "url": "https://www.nngroup.com/articles/design-systems-101/",
+ "type": "article"
+ },
+ {
+ "title": "A comprehensive guide to design systems",
+ "url": "https://www.invisionapp.com/inside-design/guide-to-design-systems/",
+ "type": "article"
+ }
+ ]
+ },
+ "2rlmLn_yQQV-7DpX1qT98": {
+ "title": "Need of Design System",
+ "description": "Having a solid design system speeds up your work by making the product team more efficient, and it creates consistency and harmony within the product and brand ecosystem. A strong design system takes the burden off individual designers to think through commonly recurring design problems. With a full library of pre-approved elements, designers can focus on bigger problems like creating seamless, intuitive flows that delight users. That kind of efficiency pays huge dividends over time.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Why You Need a Strong Design System (and How to Build One)",
+ "url": "https://www.drawbackwards.com/blog/why-you-need-a-strong-design-system-and-how-to-build-one",
+ "type": "article"
+ },
+ {
+ "title": "On Design Systems: Sell The Output, Not The Workflow",
+ "url": "https://www.smashingmagazine.com/2016/05/design-systems-responsive-design-sell-output-not-workflow/",
+ "type": "article"
+ },
+ {
+ "title": "Design Systems, when and how much?",
+ "url": "https://www.youtube.com/watch?v=Hx02SaL_IH0",
+ "type": "video"
+ }
+ ]
+ },
+ "J5mU0v491qrm-mr1W3Msd": {
+ "title": "Design System vs Component Library",
+ "description": "A component library is just a collection of visuals i.e. colours, button stylings, fonts, etc. A Design System takes it to the next level by including standards and documentation around the look and usage of each component. The Design System acts as the single-source of truth.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "A Design System: So Much More Than A Component Library",
+ "url": "https://www.architech.ca/a-design-system-so-much-more-than-a-component-library",
+ "type": "article"
+ },
+ {
+ "title": "Design System vs UI Component Library vs Brand Style Guide",
+ "url": "https://prototype.net/blog/design-system-component-library-style-guide",
+ "type": "article"
+ },
+ {
+ "title": "Design Systems vs Pattern Libraries vs Style Guides vs Component Libraries",
+ "url": "https://www.uxpin.com/studio/blog/design-systems-vs-pattern-libraries-vs-style-guides-whats-difference/",
+ "type": "article"
+ }
+ ]
+ },
+ "6r9XbwlBtHmJrhviG2cTD": {
+ "title": "What is Atomic Design",
+ "description": "Atomic design (by Brad Frost) is a mental model to help you think of user interfaces as a cohesive whole and a collection of parts at the same time. Through the comparison to atoms, molecules, and organisms, we can think of the design of our UI as a composition of self-containing modules put together.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Atomic Design Principles & Methodology 101",
+ "url": "https://xd.adobe.com/ideas/process/ui-design/atomic-design-principles-methodology-101/",
+ "type": "article"
+ },
+ {
+ "title": "Atomic Design Methodology",
+ "url": "https://atomicdesign.bradfrost.com/chapter-2/",
+ "type": "article"
+ },
+ {
+ "title": "Atomic Design and UI Components: Theory to Practice",
+ "url": "https://blog.bitsrc.io/atomic-design-and-ui-components-theory-to-practice-f200db337c24",
+ "type": "article"
+ }
+ ]
+ },
+ "_3_tFOpQisx6DSP4Yc2E2": {
+ "title": "Stakeholders Involved in Building",
+ "description": "Building an effective design system is not an individual responsibility, you need more than just designers. Here’s a quick list of the disciplines that can be represented in your team to create an effective design system:\n\n* **Designers:** to define the visual elements of the system\n* **Frontend Developers:** To create modular efficient code\n* **Accessibility Experts:** Accessibility experts to ensure your system conforms to standards like WCAG\n* **Performance Experts:** who can ensure your system loads quickly on all devices\n* **Content Strategists:** who can help the team nail the voice and tone of the system\n* **Researchers:** who can help you understand customer needs\n* **Product Managers:** to ensure the system is aligning to customer needs\n* **Leaders:** (VPs and directors) to champion and align the vision throughout the company including up to executive leadership\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Designing the Design System",
+ "url": "https://www.designbetter.co/design-systems-handbook/designing-design-system",
+ "type": "article"
+ }
+ ]
+ },
+ "hauTvrBOAHgrUnO_m_kDM": {
+ "title": "Design System Examples",
+ "description": "Visit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Collection of Open Source Design Systems",
+ "url": "https://github.com/alexpate/awesome-design-systems",
+ "type": "opensource"
+ },
+ {
+ "title": "Material Design (Google)",
+ "url": "https://material.io/",
+ "type": "article"
+ },
+ {
+ "title": "Carbon Design System (IBM)",
+ "url": "https://carbondesignsystem.com/",
+ "type": "article"
+ },
+ {
+ "title": "Atlassian Design System",
+ "url": "https://atlassian.design/",
+ "type": "article"
+ },
+ {
+ "title": "Polaris Design System (Shopify)",
+ "url": "https://polaris.shopify.com/",
+ "type": "article"
+ },
+ {
+ "title": "Gov.uk Design System",
+ "url": "https://design-system.service.gov.uk/",
+ "type": "article"
+ }
+ ]
+ },
+ "de0TKvmFTDmKGZc5X7iFq": {
+ "title": "Terminology",
+ "description": "Design systems can be tricky if you don’t know what certain words mean. Have a look at the roadmap nodes as well as follow the link below to read the glossary.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Design Systems Glossary",
+ "url": "https://web.archive.org/web/20220620075140/https://superfriendly.com/design-systems/glossary/",
+ "type": "article"
+ }
+ ]
+ },
+ "97cpJyKBKNAq1P_pQZH-t": {
+ "title": "Component",
+ "description": "Components are the reusable building blocks of a design system. Each component meets a specific interaction or UI needs, and is specifically created to work together to create patterns and intuitive user experiences.",
+ "links": []
+ },
+ "vJ4WytrzY7j10mo8S3O1u": {
+ "title": "Component Library",
+ "description": "A component library is a collection of all the components used in a website, software or app. Some of the common tools to showcase and browse components in a component library include are given below:\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Pattern Lab",
+ "url": "https://patternlab.io/",
+ "type": "article"
+ },
+ {
+ "title": "Fractal",
+ "url": "https://fractal.build/",
+ "type": "article"
+ },
+ {
+ "title": "Storybook",
+ "url": "https://storybook.js.org/",
+ "type": "article"
+ }
+ ]
+ },
+ "fPUuXrlchna3K00KcY4O6": {
+ "title": "Design Language",
+ "description": "A design language or design vocabulary is an overarching scheme or style that guides the design of a complement of products or architectural settings, creating a coherent design system for styling.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "What is a Design Language.. really?",
+ "url": "https://medium.com/thinking-design/what-is-a-design-language-really-cd1ef87be793",
+ "type": "article"
+ },
+ {
+ "title": "How to Develop a Design Language",
+ "url": "https://xd.adobe.com/ideas/principles/web-design/how-to-develop-design-language/",
+ "type": "article"
+ },
+ {
+ "title": "What Actually Constitutes Design Language?",
+ "url": "https://www.uxpin.com/studio/blog/design-language/",
+ "type": "article"
+ },
+ {
+ "title": "Visual Design Language: The Building Blocks Of Design",
+ "url": "https://www.smashingmagazine.com/2020/03/visual-design-language-building-blocks/",
+ "type": "article"
+ }
+ ]
+ },
+ "kifE3JE2immnU1O3-toZf": {
+ "title": "Governance",
+ "description": "Governance is a framework for clarifying roles, responsibilities, and authority over decisions. Having that clarity ensures that decisions for the design system funnel smoothly through the governance process\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Governance is a design system’s friend",
+ "url": "https://zeroheight.com/blog/governance-is-a-design-systems-friend",
+ "type": "article"
+ },
+ {
+ "title": "Design System Governance – Scale Your Design",
+ "url": "https://www.uxpin.com/studio/blog/design-system-governance/",
+ "type": "article"
+ },
+ {
+ "title": "Governance by design: Building successful design systems",
+ "url": "https://rangle.io/blog/governance-by-design-building-successful-design-systems/",
+ "type": "article"
+ },
+ {
+ "title": "Team Models for Scaling a Design System",
+ "url": "https://medium.com/eightshapes-llc/team-models-for-scaling-a-design-system-2cf9d03be6a0",
+ "type": "article"
+ }
+ ]
+ },
+ "mlBzJ2YvBr9QuOthKdj0p": {
+ "title": "Guidelines",
+ "description": "Design guidelines are sets of recommendations on how to apply design principles to provide a positive user experience. Designers use such guidelines to judge how to adopt principles such as intuitiveness, learnability, efficiency and consistency so they can create compelling designs and meet and exceed user needs.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Design Guidelines",
+ "url": "https://www.interaction-design.org/literature/topics/design-guidelines",
+ "type": "article"
+ }
+ ]
+ },
+ "7xPT8rUX3hjSWbxH_FfQs": {
+ "title": "Pattern",
+ "description": "Patterns are best practice design solutions for specific user-focused tasks and page types. Patterns often use one or more components and explain how to adapt them to the context. Some sample patterns could be user signing in to the application or performing the checkout operation.",
+ "links": []
+ },
+ "4dzoZmkNHPedgLqLy93t8": {
+ "title": "Pilot",
+ "description": "Pilots are one of the best ways to put your design system through its paces, especially before the design system even gets to a v1. Like television pilots help test audience reactions to a series concept without investing significant resources to create the whole thing, application pilots are a good foundation for ensuring your design system’s design and code are battle-tested.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Design Systems: Pilots & Scorecards",
+ "url": "https://superfriendly.com/design-systems/articles/design-systems-pilots-scorecards/",
+ "type": "article"
+ }
+ ]
+ },
+ "jETJVuS_EczJiQASLqaQr": {
+ "title": "Token",
+ "description": "Design system tokens are the style values of UI elements such as color, typography, spacing, shadows, etc., that are used across products and capable of being converted to a format for any platform (web, mobile, desktop). Tokens are building blocks of the design system—think of them as sub atoms, the smallest pieces of style values that allow designers to create styles for a product.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "What Are Design Tokens?",
+ "url": "https://xd.adobe.com/ideas/principles/design-systems/what-are-design-tokens/",
+ "type": "article"
+ }
+ ]
+ },
+ "lUObv2N7eH3Jdnwwd5vmI": {
+ "title": "UI Kit",
+ "description": "As it relates to a design system, a UI Kit is a representation of coded components created in a way that designers who don’t know code can create interface mockups. Examples of UI kits are Sketch libraries and [Figma design systems](https://www.figma.com/blog/how-to-build-your-design-system-in-figma/).\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Design System vs UI Kit",
+ "url": "https://uigstudio.com/insights/design-system-vs-ui-kit",
+ "type": "article"
+ },
+ {
+ "title": "Your sketch library is not a design system",
+ "url": "http://bradfrost.com/blog/post/your-sketch-library-is-not-a-design-system/",
+ "type": "article"
+ }
+ ]
+ },
+ "dUaoMARPabiD4DRqdkaer": {
+ "title": "Making a Design System",
+ "description": "First step in building a design system is identifying [if you even need a design system](https://sparkbox.com/foundry/when_not_to_use_a_design_system).\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Design Systems: Step-by-Step Guide to Creating Your Own",
+ "url": "https://www.uxpin.com/create-design-system-guide/",
+ "type": "article"
+ },
+ {
+ "title": "Does My Organization Need a Design System?",
+ "url": "https://www.method.com/insights/does-my-organization-need-a-design-system/",
+ "type": "article"
+ },
+ {
+ "title": "Introducing Design Systems Into Chaos - Diana Mounter, GitHub",
+ "url": "https://www.youtube.com/watch?v=FZSi1bK-BRM",
+ "type": "video"
+ },
+ {
+ "title": "Design Systems, when and how much?",
+ "url": "https://www.youtube.com/watch?v=Hx02SaL_IH0",
+ "type": "video"
+ },
+ {
+ "title": "Create a Design System with Figma - Full Course",
+ "url": "https://www.youtube.com/watch?v=RYDiDpW2VkM",
+ "type": "video"
+ }
+ ]
+ },
+ "-9I3fTpnQlmcZmIIuQiPe": {
+ "title": "Making it from Scratch",
+ "description": "If you are building a Design System from Scratch, you may skip the \"Existing Design Analysis\" node of the roadmap and start with \"Creating Design Language\".\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Create a Design System with Figma - Full Course",
+ "url": "https://www.youtube.com/watch?v=RYDiDpW2VkM",
+ "type": "video"
+ }
+ ]
+ },
+ "z5gBy7BjlBKwbYbxXtoDA": {
+ "title": "Making it from Existing Design",
+ "description": "If you are creating a Design System from pre-existing product design, there is an additional step to perform the existing design analysis, understand the existing design process, perform a visual audit, identify design elements and components and so on.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Create a Design System with Figma - Full Course",
+ "url": "https://www.youtube.com/watch?v=RYDiDpW2VkM",
+ "type": "video"
+ }
+ ]
+ },
+ "8eWhvW2zDIxMGHaXl0Y9i": {
+ "title": "Existing Design Analysis",
+ "description": "First step in creating a design system from an existing design is performing a design analysis and understanding what you will be working with to identify the requirements and prepare a plan. Performing the analysis may consist of:\n\n* Understanding the Existing Design Process\n* Performing Visual Audit\n* Identifying Design Elements\n* Identify Common Components\n* Understanding the A/B Testing and Experimentation Needs\n* Understanding any Locale or regional requirements (such as LTR/RTL).\n* Documenting your findings",
+ "links": []
+ },
+ "NKm-gXbt5Y7dDwKVkPHjX": {
+ "title": "Performing a Visual Audit",
+ "description": "Take screenshots of your current product with the help of your team. You can use any presentation software like Google Slides or print and pin them on foam-core boards. Group the screenshots into categories like buttons, navigation, forms, tables, charts, lists etc.\n\nNow, review each category to find inconsistencies and note areas for improvement with your team. Use a tool like [CSS Stats](https://cssstats.com/) to see how many unique colors, typefaces you have in your style sheets.",
+ "links": []
+ },
+ "CnsDoZ3gIaPeNbwHuZXYJ": {
+ "title": "Identify Existing Design Process",
+ "description": "To better understand the kind of design system you would like to implement, you need to start by reviewing and analyzing the current approach for design at your company. Find the answers to the following questions:\n\n* What is the design process that your company follows?\n* What are the existing tools that your company uses?\n\nIt’s also recommended to evaluate the level of design maturity of the product teams. This knowledge will help you estimate the time required to introduce the system to your organization.",
+ "links": []
+ },
+ "aak3227IDDJMh0MquQX6m": {
+ "title": "Icons",
+ "description": "Icons are visual symbols that communicate meaning quickly. They should maintain consistent style, use a grid system, provide multiple sizes, organize into semantic categories, ensure accessibility, consider cultural neutrality, be available in multiple formats, include interactive states, and follow systematic versioning.",
+ "links": []
+ },
+ "-MrrapoyFWKhSeE2PZ9mb": {
+ "title": "Visual Forms",
+ "description": "Visual forms focus on aesthetic and interactive design aspects of form components. Effective design should establish clear information architecture, create consistent field styling, develop harmonious label positioning, design clear error communication, implement progressive enhancement, prioritize mobile-first design, and ensure cross-platform consistency.",
+ "links": []
+ },
+ "78RsPhsWpl00AbkwKXUxL": {
+ "title": "Sizing",
+ "description": "Sizing tokens establish consistent dimensions across components and layouts. An effective system should establish a foundational unit, create predefined size variations, ensure minimum accessibility requirements, define standard icon sizes, establish container dimensions, implement fluid sizing, and account for platform-specific requirements.",
+ "links": []
+ },
+ "GtLYBPJjdZwG0qgA7erk7": {
+ "title": "Spaces",
+ "description": "Spacing tokens define white space between elements, creating visual rhythm and clear relationships. An effective system should establish a foundational unit, create systematic scales, define consistent internal spacing, establish layout guidelines, implement fluid spacing, create meaningful categories, and ensure cross-platform consistency.",
+ "links": []
+ },
+ "2prUeRYbSJTYjo2quJIKs": {
+ "title": "Color",
+ "description": "Color establishes brand identity and visual hierarchy in design systems. A comprehensive color system should organize colors logically, meet WCAG accessibility standards, support light/dark themes, create semantic categories, establish systematic naming, balance brand expression with function, and provide multiple formats.",
+ "links": []
+ },
+ "ODQ8zrHc2rsc8PN-APKvz": {
+ "title": "Typography",
+ "description": "Typography establishes hierarchy, readability, and brand personality. An effective system should develop harmonious scales using mathematical ratios, choose appropriate typefaces, implement fluid typography, establish consistent line-heights, define font weight hierarchy, ensure accessibility compliance, and provide clear usage guidelines.",
+ "links": []
+ },
+ "_dIMuXWI73ogboGjnLIpT": {
+ "title": "Avatar",
+ "description": "Avatars represent users or entities in interfaces. They should support multiple shapes (circular, square), various sizes, handle missing images with initials or default icons, include status indicators, maintain image quality standards, ensure accessibility, provide loading states, and support group arrangements with proper interactive feedback.",
+ "links": []
+ },
+ "UG4AIgJBfZpuhia4Y1K5v": {
+ "title": "Badges",
+ "description": "Badges are small status indicators that communicate information about objects or actions. Effective design should include numeric indicators for notifications, status badges with distinct colors, category labels, interactive states, multiple sizes, semantic color integration, consistent positioning, content guidelines, and proper accessibility.",
+ "links": []
+ },
+ "5DUobzueMZbScyTZTHpCS": {
+ "title": "Banners",
+ "description": "Banners communicate important information at the top of pages. They should support different message types with distinct visuals, various positioning options, clear dismissal mechanisms, relevant actions, consistent iconography, mobile adaptations, subtle animations, content guidelines, proper accessibility, and stacking rules for multiple banners.",
+ "links": []
+ },
+ "s6oqvHgwK4Cwyx-JENBbY": {
+ "title": "Buttons",
+ "description": "Buttons enable user actions and require clear visual hierarchy (primary, secondary, tertiary), comprehensive interactive states, multiple sizes, icon support, content guidelines, minimum 44px touch targets, loading indicators, responsive behavior, proper accessibility with ARIA labels, and subtle animations.",
+ "links": []
+ },
+ "yLLAUGbGUHBTEDkZNK0fm": {
+ "title": "Cards",
+ "description": "Cards are flexible content containers that group related information and actions. They require clear content hierarchy, consistent elevation systems, responsive behavior, distinct interactive states, media support, defined action areas, content variants, loading states, proper accessibility, and consistent spacing aligned with the design system.",
+ "links": []
+ },
+ "hzVwLVzAij6TgPTcNHyhv": {
+ "title": "Dropdowns",
+ "description": "Dropdowns reveal option lists when activated to save space. They need clear triggers with visual indicators, organized options with grouping, search/filtering for long lists, multi-select support, smart positioning, full keyboard navigation, loading states, mobile adaptations, proper accessibility, and performance optimization.",
+ "links": []
+ },
+ "5LCMzBnnS206t5EtgaUx8": {
+ "title": "Forms",
+ "description": "Forms collect user input and require standardized input components, comprehensive validation systems, effective labeling strategies, consistent layouts, clear error handling, progressive disclosure, required field indicators, auto-complete integration, proper accessibility, and mobile optimization.",
+ "links": []
+ },
+ "Ia1gYzepJOTvTro961eSj": {
+ "title": "...other",
+ "description": "Specialized elements beyond core components include badges for notifications, breadcrumbs for navigation, progress indicators, tooltips for help, pagination for browsing, tab systems, accordions for collapsible content, modals for focused interactions, notification systems, and basic data visualization elements.",
+ "links": []
+ },
+ "ILRDAnpfGHCZq-FBlbfDO": {
+ "title": "A/B Tests & Experiments",
+ "description": "Understand how the team implements A/B tests and experiments on different screens and if the new design system should accommodate any necessary requirements.",
+ "links": []
+ },
+ "pRJ9wEPNfFx_6EYB501vk": {
+ "title": "Regional Requirements",
+ "description": "Understand any regional requirements such as LTR or any other UX variations that your design system should accommodate.",
+ "links": []
+ },
+ "-b4GjLpL_ppDMJSiChTef": {
+ "title": "Documentation",
+ "description": "Organize and document the results of visual audit, design elements, components with variations, states, patterns found, any existing documentation, current design process, and considerations. This documentation will be shared across the team and act as a guide when building the new design system.",
+ "links": []
+ },
+ "JnaNZ9MfMrXQrjW2wABzB": {
+ "title": "Creating Design Language",
+ "description": "Like any language, a design language is a methodical way of communicating with your audience through your approach to product design. It’s the cornerstone of consistent customer experiences.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "What is a Design Language.. really?",
+ "url": "https://medium.com/thinking-design/what-is-a-design-language-really-cd1ef87be793",
+ "type": "article"
+ },
+ {
+ "title": "How to Develop a Design Language",
+ "url": "https://xd.adobe.com/ideas/principles/web-design/how-to-develop-design-language/",
+ "type": "article"
+ },
+ {
+ "title": "What Actually Constitutes Design Language?",
+ "url": "https://www.uxpin.com/studio/blog/design-language/",
+ "type": "article"
+ },
+ {
+ "title": "Visual Design Language: The Building Blocks Of Design",
+ "url": "https://www.smashingmagazine.com/2020/03/visual-design-language-building-blocks/",
+ "type": "article"
+ }
+ ]
+ },
+ "toyNbBB5tbyiJZkzuklIv": {
+ "title": "Writing Guidelines",
+ "description": "Every consistent experience needs watertight writing. Laying down the foundations for your house style early keeps everything in line with consistent grammar, style choices and action-oriented language to help your design.",
+ "links": []
+ },
+ "fnlVIgsmyxj2UVCCjM-8g": {
+ "title": "Tone of Voice",
+ "description": "A clear tone of voice defines how you speak to your audience at every moment in their journey, helping them get wherever they want to go.",
+ "links": []
+ },
+ "Zspu1SsuTE34PVmYePcs4": {
+ "title": "Terminology",
+ "description": "Create the standard terms and phrases that need to be kept the same throughout the user experience, speeding up the design process and unifying your voice.",
+ "links": []
+ },
+ "1RJrMVJf_3clM7E5OML-f": {
+ "title": "Design Principles",
+ "description": "The considerations that guide the basis of your practice. They outline how you approach design from a philosophical perspective and help with everyday decisions.",
+ "links": []
+ },
+ "cMfsRtvzvDZZJ0TqeUOxm": {
+ "title": "Vision",
+ "description": "Brand vision serves as the foundation for design system decisions, providing purpose and direction. An effective vision should articulate organizational purpose, identify core values, visualize future success, prioritize user needs, clarify brand uniqueness, account for cultural considerations, and connect to measurable goals.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Creating Brand Vision",
+ "url": "https://www.interaction-design.org/literature/article/branding-in-ux",
+ "type": "article"
+ },
+ {
+ "title": "Vision-Driven Design Systems",
+ "url": "https://bradfrost.com/blog/post/the-design-system-ecosystem/",
+ "type": "article"
+ },
+ {
+ "title": "Brand Strategy for Design",
+ "url": "https://alistapart.com/article/creating-a-brand-identity/",
+ "type": "article"
+ },
+ {
+ "title": "Purpose-Driven Design",
+ "url": "https://designsystem.digital.gov/design-tokens/brand/",
+ "type": "article"
+ },
+ {
+ "title": "Explore top posts about Brand Strategy",
+ "url": "https://app.daily.dev/tags/branding?ref=roadmapsh",
+ "type": "article"
+ }
+ ]
+ },
+ "Wn8CylBz-hyl9-iXcUVTO": {
+ "title": "Monochrome Version",
+ "description": "A monochrome version of your logo that looks good on top of photography or when it’s printed with a poor quality printer.",
+ "links": []
+ },
+ "FA3JsZgNhKrgNHVtVreol": {
+ "title": "Small Use Guidance",
+ "description": "Your logo must perform well and be recognisable at all sizes. Tips for using your logo in these cases will minimise the risk of it being misused.",
+ "links": [
+ {
+ "title": "Everything You Need to Know About Logo Usage Guidelines",
+ "url": "https://www.tailorbrands.com/blog/logo-usage-guidelines",
+ "type": "article"
+ }
+ ]
+ },
+ "7n61402xwhIgJ7dPHg8q7": {
+ "title": "Placement Guidance",
+ "description": "Logo placement guidance ensures consistent brand representation through clear positioning, sizing, and clearance rules. Effective guidelines should define minimum clearance areas, establish preferred positions for different contexts, provide size specifications, define background treatments, and account for platform-specific requirements.",
+ "links": []
+ },
+ "RmSFwKqL9yXXxGKZusKWX": {
+ "title": "Usage Guidance",
+ "description": "Logo usage guidance provides rules for proper implementation to maintain brand consistency. Effective guidance should establish clear examples of proper usage and mistakes to avoid, define logo variations, specify color requirements, prohibit unauthorized alterations, and include approval processes for new contexts.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Logo Usage Best Practices",
+ "url": "https://99designs.com/blog/tips/logo-usage-guidelines/",
+ "type": "article"
+ },
+ {
+ "title": "Brand Guidelines Development",
+ "url": "https://designsystem.digital.gov/design-tokens/logo/",
+ "type": "article"
+ },
+ {
+ "title": "Trademark and Logo Legal Guidelines",
+ "url": "https://www.uspto.gov/trademarks-getting-started/trademark-basics",
+ "type": "article"
+ },
+ {
+ "title": "Brand Identity Protection",
+ "url": "https://www.brandfolder.com/blog/brand-guidelines",
+ "type": "article"
+ },
+ {
+ "title": "Explore top posts about Brand Management",
+ "url": "https://app.daily.dev/tags/branding?ref=roadmapsh",
+ "type": "article"
+ }
+ ]
+ },
+ "-6LPUMRm-SqvRVEWPDFl8": {
+ "title": "File Formats",
+ "description": "Providing a variety of formats for the vector version of your logo will make it easier for others to work and prevent anyone from redrawing it.",
+ "links": [
+ {
+ "title": "What is a Vector Logo and Why You Need It",
+ "url": "https://www.renderforest.com/blog/vector-logo",
+ "type": "article"
+ }
+ ]
+ },
+ "aLtOGjNFxaRzg0PI-ed99": {
+ "title": "Accessibility",
+ "description": "Guidelines for how you approach accessibility and how you leverage colour, hierarchy and assistive technologies to help your users.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "Introduction to Web Accessibility",
+ "url": "https://www.w3.org/WAI/fundamentals/accessibility-intro/",
+ "type": "article"
+ },
+ {
+ "title": "What is Accessibility? by Mozilla",
+ "url": "https://developer.mozilla.org/en-US/docs/Learn/Accessibility/What_is_accessibility",
+ "type": "article"
+ },
+ {
+ "title": "Accessibility Principles",
+ "url": "https://www.w3.org/WAI/fundamentals/accessibility-principles/",
+ "type": "article"
+ },
+ {
+ "title": "WebAIMs Website (Web Accessibility In Mind)",
+ "url": "https://webaim.org/",
+ "type": "article"
+ },
+ {
+ "title": "WAVE Web Accessibility Evaluation Tool",
+ "url": "https://wave.webaim.org/",
+ "type": "article"
+ },
+ {
+ "title": "Explore top posts about Accessibility",
+ "url": "https://app.daily.dev/tags/accessibility?ref=roadmapsh",
+ "type": "article"
+ }
+ ]
+ },
+ "PlW8mHnOTyYnbtl0zUSG9": {
+ "title": "User Onboarding",
+ "description": "How you onboard your users to your product or a new feature and give them a great experience from the start.",
+ "links": [
+ {
+ "title": "What is user onboarding? ",
+ "url": "https://www.youtube.com/watch?v=PatIqbGEQe4",
+ "type": "video"
+ }
+ ]
+ },
+ "bD-DjUbAA6l2eK1R9ITcK": {
+ "title": "Microcopy Guidelines",
+ "description": "The standard way to write for the components in your design system. These take platform conventions and best practices for writing all into consideration.",
+ "links": []
+ },
+ "a53cl6ZKvYXxG25Ii2_zu": {
+ "title": "Defining Design Tokens",
+ "description": "Variables that store values for the base layer of your design system, like colour and typography. They’re used in components, so changes on this level will resonate throughout the whole system.\n\nVisit the following resources to learn more:",
+ "links": [
+ {
+ "title": "What Are Design Tokens?",
+ "url": "https://xd.adobe.com/ideas/principles/design-systems/what-are-design-tokens/",
+ "type": "article"
+ }
+ ]
+ },
+ "fW0cEy2SB0HDbiF7QA7Ev": {
+ "title": "Accessibility",
+ "description": "Make sure to have accessible pairings between the main colours in your palette. More importantly, make sure that your background and text colours have at least an AA standard contrast ratio between them.",
+ "links": []
+ },
+ "__Pv19gRr2SFknVnfm0Mr": {
+ "title": "Functional Colors",
+ "description": "Besides your brand colours, make sure to have colours defined and made into variables for functions like disabled states, backgrounds, actions and high contrast text.",
+ "links": []
+ },
+ "kxUnqpydDwB73IwrCPZM0": {
+ "title": "Dark Mode",
+ "description": "Preparing a dark mode version of your colour palette will allow your design system to adapt to dark mode and respect what your user wants to see.",
+ "links": []
+ },
+ "XDfxs5cgjSuTEprZi2Z5b": {
+ "title": "Guidelines",
+ "description": "Provide guidelines on how and when to use the colours in your palette, what to keep in mind when working with them and how not to use them.",
+ "links": []
+ },
+ "wQbMhC7q3qdKYf_pX5qL4": {
+ "title": "Units",
+ "description": "Units are the most granular building blocks for layout. Defining a set of values with consistent increments (such as 4, 8, 12 and 16 for a 4-point system) will provide you with the foundation when you’re designing your grid and spacing values.",
+ "links": []
+ },
+ "8f2V-rM7soorTTvNo5Vcx": {
+ "title": "Grid",
+ "description": "Every layout should sit on a grid that brings order and hierarchy to the interface. Define a grid separately for mobile, tablet and desktop devices with columns, gutters, and margins so your interface can adapt to any platform easily.",
+ "links": []
+ },
+ "djwnJq9Y_Hx1Ynw01wr_u": {
+ "title": "Breakpoints",
+ "description": "Predefine the screen sizes and orientations your grid will adapt to.",
+ "links": []
+ },
+ "dXaYOwTAnYSlipNEBSV9l": {
+ "title": "Spacking",
+ "description": "Horizontal and vertical rhythm plays a big role in a layout. You should provide easy methods for adding space between interface elements independent of your grid.",
+ "links": []
+ },
+ "8YVCtgYRHR3VcpUJXMVwP": {
+ "title": "Responsiveness",
+ "description": "Desktop devices can usually afford to have bigger font sizes compared to mobile devices. Creating a typography scale that adapts to the viewport size will help with a more meaningful hierarchy and layout.",
+ "links": []
+ },
+ "Zl7MVllzJgObruYtlibKf": {
+ "title": "Grid Relation",
+ "description": "Font sizes and leading should match your grid to allow better pairing between text and other UI elements. A good example of this is text paired with icons with bounding boxes.",
+ "links": []
+ },
+ "L2NHddsv5RGR_BW0I3f4T": {
+ "title": "Readability",
+ "description": "Optimising the letter spacing (tracking), line height (leading) and line length for your typography scale will help with the readability of text.",
+ "links": []
+ },
+ "wFL9axjaPcVvI8XWduxgz": {
+ "title": "Performance",
+ "description": "Custom fonts need to be downloaded before they can be displayed, especially on the web. Make sure that you have sensible fallbacks and fast loading time for your typography assets. Using system fonts solves this performance problem.",
+ "links": []
+ },
+ "Jab5LO0mGhTy1cU61Catu": {
+ "title": "Guidelines",
+ "description": "Provide guidelines on how and when to use the pairings in your typography scale, what to keep in mind when working with them and how not to use them.",
+ "links": []
+ },
+ "DhrnZwQODG0P7D-27_3ec": {
+ "title": "Accessibility",
+ "description": "For icons that convey a meaning or serve a function, add the necessary support for screen readers. You can skip this for decorative icons.",
+ "links": []
+ },
+ "SPK1i0XuHpNEWyi1iIxrV": {
+ "title": "Style",
+ "description": "Make sure that your icon family makes visual sense as a whole. Picking an outlined or filled style and sticking with it will lead to better visual consistency and predictability.",
+ "links": []
+ },
+ "wiclAEEYioRgLmXFcKQ4E": {
+ "title": "Naming",
+ "description": "Name your icons based on what they are, not what they represent. For instance, a trash icon should be named trash, not delete. You can still add related keywords to improve discoverability.",
+ "links": []
+ },
+ "6Hmj_TeQ563jshqAAl__I": {
+ "title": "Grid Relation",
+ "description": "Draw your icons in a bounding box that plays well with your grid. This makes for a better pairing with other UI elements. A good example of this would be icons with bounding boxes paired with text.",
+ "links": []
+ },
+ "w3LS85eFerscaxb2Xp-dP": {
+ "title": "Sizes",
+ "description": "Provide different sizes for icons that correlate to your grid. Provide a minimum size and remove unnecessary detail for your icons for smaller sizes.",
+ "links": []
+ },
+ "HDf2L4F1f8uUGpVaf7Y7z": {
+ "title": "Keywords",
+ "description": "Adding keywords will improve the discoverability of each icon and provide a better user experience for anyone using your system.",
+ "links": []
+ },
+ "Y0KxHVrcNGHDao-38Oz3w": {
+ "title": "Reserved Icons",
+ "description": "Reserving icons that represent common actions will prevent their use in any other context. System icons for navigation or adding and deleting are a good example. This leads to a more intuitive user experience.",
+ "links": []
+ },
+ "eTxhpC3AQIMcUax6WFU9U": {
+ "title": "Guidelines",
+ "description": "Provide guidelines on how and when to use icons, what to keep in mind when working with them and how not to use them.",
+ "links": []
+ },
+ "Hw_LQInG6OtSwDXch3Lvg": {
+ "title": "Creating Core Components",
+ "description": "Components are the main building blocks for user interfaces. Building a reusable component library enhances your product development workflow by reducing design and tech debt and speeding up the process. Core components can’t be broken down into granular pieces without losing their meaning.",
+ "links": []
+ },
+ "h3TZY1yBkzLYUK6W7K7xs": {
+ "title": "Avatar",
+ "description": "Avatars are used to show a thumbnail of a user photo or a visual representation of any other type of content.\n\n* **Image:** Avatars should mask an image into their shape and work with any image size since they may get this image from unknown data sources.\n* **Image Fallback:** There should be fallbacks when there’s no image available. This can be done with placeholder images or initials.\n* **Accessibility:** Always provide a description for screen readers describing what’s displayed on the avatar image instead of just naming its role.\n* **Sizes:** There are many contexts to use avatars and they all require different sizes for the component. For average projects use at least 2-3 different sizes and make sure there’s at least a small size available.\n* **Icon:** Avatars can be used with an icon instead of an image to emphasize areas that don’t necessarily have (or need) an image associated with it.\n* **Background Colors:** When used with icons or text, there has to be a background colour from the design system colour tokens applied to the avatar shape. Make sure that icons and text have enough contrast ratio with the background according to the WCAG AA standard.",
+ "links": []
+ },
+ "hjiJJg4KNr8lyktFQd868": {
+ "title": "Input Text",
+ "description": "Input text lets users enter and edit text.\n\n* **Disabled State:** Prevents input interactions and removes its value from the form submission.\n* **Placeholder:** When there’s no value entered, show a placeholder with a potential value example. Don’t use placeholders as labels for the inputs.\n* **Label:** There should be a text label linked with the text field. Clicking the label should move the focus to the field.\n* **Error State:** The error state is used for form validation errors when the error is related to the text field only. Always use a text error along with changing the colour of the field.\n* **Focused State:** The focused state should highlight the text field when users start to interact with it. There is always only one focused field in the form.\n* **Autocomplete:** When applicable, adding support for the HTML autocomplete attribute will allow users to easily enter different data types.\n* **Icon Support:** Icons are used to describe input methods, express a text field state or provide additional functionality.",
+ "links": []
+ },
+ "kkqRIgdXWaJbX9CjLpwha": {
+ "title": "Banner",
+ "description": "Banners display an actionable message used as a prominent way of communicating with your users.\n\n* **Appearance:** Banners are used to display different types of messages and it’s important to differentiate their visual appearance based on the role they’re playing. If you’re using background colours for role differentiation, make sure there’s enough contrast ratio with the content according to the WCAG AA standard.\n* **Area for icons or images:** Banners can supplement their message using a supporting icon or image. They shouldn’t be used instead of text content.\n* **Actions:** Actions in banners should relate to its text and provide a way to react to the message sent to the user.\n* **Dismissible Action:** Don’t overwhelm the user with banners on the page and include a dismissable action. That may be either a separate close button or one of the actions provided.\n* **Accessibility:** If a banner dynamically appears on the page, it should be announced to the user by their assistive technology.\n* **Responsiveness:** Banners should adapt to the viewport size. This usually means that they become full-width for mobile to save some space.",
+ "links": []
+ },
+ "LNsXQI8sE_5kzSD_iMLJA": {
+ "title": "Badge",
+ "description": "Badges are elements that represent the status of an object or user input value.\n\n* **Appearance:** Badges may play various roles in your product and having a predefined colour for each role should help users understand their meaning. When changing colours, make sure the text has enough contrast ratio with the background according to the WCAG AA standard.\n* **Dismissible Action:** Badges can be used as a dynamic way to display selected values and there should be a way to dismiss them.",
+ "links": []
+ },
+ "LWihkf4q5UawjLd84KQxN": {
+ "title": "Button",
+ "description": "Buttons are interactive elements used for single-step actions.\n\n* **Hover State:** Clearly show that the button is interactive when it gets hovered with a mouse cursor.\n* **Active State:** Used when a button gets pressed. The same state can be used to represent the button responsible for toggling another element on the page while that element is visibly opened.\n* **Focused State:** Used when a button gets selected through keyboard navigation.\n* **Icon Support:** Icons easily communicate the purpose of the button when used next to its label or can be used without text when there’s not enough space. Make sure that the accessibility label is provided when used with an icon only.\n* **Disabled:** Visually shows that a button is not interactive and restricts it from being pressed.\n* **Loading:** Used when users have to wait for the result of their action after they press a button. If a spinner is used to display this state make sure that it’s not changing the original button width or height.\n* **Full Width:** By default buttons take the width of their content, but they should also come with a full width variant that works well in mobile devices.\n* **Variants:** When using multiple buttons, there should be a way to differentiate between primary and secondary actions. Buttons may play different roles for the user or be used on different types of surfaces and they have to change the way they look.\n* **Sizes:** Buttons can be used in different areas of the website and may have multiple predefined sizes. On mobile, tappable areas have to be a minimum of 48px to be accessible according to iOS and Android accessibility guidelines.",
+ "links": []
+ },
+ "rZ7d1C9swiqlRTbdJLZ0R": {
+ "title": "Card",
+ "description": "Cards are used to group information about subjects and their related actions.\n\n* **Supports any type of content:** Cards are one of the most used components in the product, so they have to be flexible enough to support any other components placed in them.\n* **Information structure:** No matter how flexible cards are, it’s important for cards to have a specific structure for its elements for product consistency.\n* **Supports media sections:** One of the most popular scenarios for using cards is mixing them with media content. The most popular options are having a full-width area on top of the content or full-height area at one of the card’s sides.\n* **Supplementary actions:** Cards can be used with actions usually placed at the bottom of the card, or the card itself can be tappable and represent an action.\n* **Responsiveness:** On mobile viewports cards are usually full-width in order to save space for the content.",
+ "links": []
+ },
+ "yWEXfjzuzk99dxjZlG4Cq": {
+ "title": "Carousel",
+ "description": "Carousels stack the same type of items and allows scrolling through them horizontally.\n\n* **Navigation Controls:** Carousels should have easy-to-find navigation controls for scrolling through content.\n* **Supports any content:** Carousels can be used in different contexts and shouldn’t be limited to a specific child component. In some scenarios you might want items within the same carousel to differ from each other.\n* **Items width customisation:** For simple products, it might be fine to use multiple predefined sizes for carousel items. For more flexibility, it’s good to provide a way to define a custom width.\n* **Touch events support:** Carousels should be scrollable on touch devices. Some of the best practices are to use native scrolling and to make sure you’re supporting the same behaviour for all touch devices, not just mobile phones.\n* **Keyboard navigation:** It should be possible to scroll through content with keyboard arrows when focused on navigation controls.\n* **Responsiveness:** It’s good practice to hide or reduce the size of navigation controls for mobile viewports to improve the visibility of the content.",
+ "links": []
+ },
+ "MtBSvKoyjdLd6DIdolLRi": {
+ "title": "Dropdown",
+ "description": "Dropdowns are used to display a contextual subview with a list of actions or content related to the area where the dropdown is.\n\n* **Supports any type of content:** Dropdowns may be used in a lot of contexts like date pickers, language selection or other product features.\n* **Action Menu:** One of the most used scenarios for dropdowns is providing an action menu for the user, so it’s useful to have this layout defined.\n* **Focus Trapping:** Once the dropdown’s opened, the focus should work only for elements inside the dropdown. When it’s closed, the focus should move to the dropdown trigger.\n* **Close Action:** Either some actions inside the dropdown should close it or there should be a separate close button. Also, it’s good practice to close the dropdown when a user clicks outside.\n* **Keyboard Navigation:** It should be possible to navigate through dropdown children elements with the keyboard and close it with an Esc key.\n* **Dynamic Position:** Dropdown content should be displayed based on the current position of the trigger element on the screen and always visible to the user.\n* **Responsiveness:** Dropdown content should be adapted for mobile viewpoints as it may take a lot of space on desktops.",
+ "links": []
+ },
+ "bzY_iXRnotct_WnNRTlbd": {
+ "title": "Icon",
+ "description": "The icon component is a way to align the way iconography static assets are displayed in the product.\n\n* **Sizes:** Icons should have a number of predefined sizes to provide a holistic experience across the product. Typography pairings may be used for these size values to ensure that they are aligned with the text sizes.\n* **Colors:** Icons should be using values from the design system colour palette. Using parent element text colour for icon fill colour can make this automatic.",
+ "links": []
+ },
+ "F5_sxUnnGEdgF6BkA5T5x": {
+ "title": "Input Checkbox",
+ "description": "An input checkbox is a form element used for selecting one or multiple options.\n\n* **Checked State:** Used when the checkbox is selected and will use its value for the form submission.\n* **Disabled State:** Prevents checkbox interactions and removes its value from the form submission.\n* **Intermediate State:** Used when the checkbox has children selectable elements and only some of them are selected.\n* **Label:** There should be a text label linked with the checkbox field. Clicking the label should also trigger the checkbox selection.\n* **Error State:** The error state is used for form validation errors when the error is related to the checkbox field only. Always use a text error along with changing the colour of the field.\n* **Keyboard State:** Checkbox selections should be triggered with the Space key. Using native elements for this should provide this kind of interaction out of the box.\n* **Checkbox Group:** Checkboxes can be grouped to work with multiple values at the same time.",
+ "links": []
+ },
+ "rN-_plAA5FkcQl03wsL18": {
+ "title": "Input Radio",
+ "description": "An input radio is a form element used for selecting one option from a list.\n\n* **Checked State:** Used when the radio is selected and will use its value for the form submission. A radio input can’t be unselected by pressing it again.\n* **Disabled State:** Prevents radio interactions and removes its value from the form submission.\n* **Label:** There should be a text label linked with the radio field. Clicking the label should also trigger the radio selection.\n* **Error State:** The error state is used for form validation errors when the error is related to the radio field only. Always use a text error along with changing the colour of the field.\n* **Keyboard State:** A radio selection should be triggered when the Space key is pressed. Using native elements for this should provide this kind of interaction out of the box.\n* **Radio Group:** Radio inputs should always be used in a group. If one of them is selected, it can be deselected only by choosing another radio.",
+ "links": []
+ },
+ "NISeaJUlDtQ0kSuyxmrOT": {
+ "title": "Input Switch",
+ "description": "Input switches toggle the state of a single item. Compared to the input checkbox, their changes usually apply without any additional submission.\n\n* **Checked State:** Used when an input switch is turned on. It’s better to provide an additional way to indicate the checked state besides changing its colour when applicable.\n* **Disabled State:** Prevents interacting with an input switch.\n* **Label:** There should be a text label linked with the switch field. Clicking the label should also trigger the input selection.\n* **Keyboard State:** A switch selection should be triggered when the Space key is pressed.",
+ "links": []
+ },
+ "n1nUkMqGtPobZPJHCvPsk": {
+ "title": "Select",
+ "description": "Select lets user select a value from a list of values in a form context:\n\n* **Disabled State:** Prevents input interactions and removes its value from the form submission.\n* **Placeholder:** When there’s no value entered, show a placeholder with a potential value example. Don’t use placeholders as labels for the inputs.\n* **Label:** There should be a text label linked with the text field. Clicking the label should move the focus to the field.\n* **Error State:** The error state is used for form validation errors when the error is related to the text field only. Always use a text error along with changing the colour of the field.\n* **Focused State:** The focused state should highlight the text field when users start to interact with it. There is always only one focused field in the form.\n* **Autocomplete:** When applicable, adding support for the HTML autocomplete attribute will allow users to easily enter different data types.\n* **Icon Support:** Icons are used to describe input methods, express a text field state or provide additional functionality.",
+ "links": []
+ },
+ "iusI39fxcu2rbMXiosaM6": {
+ "title": "Textarea",
+ "description": "Text area lets users enter and edit text.\n\n* **Disabled State:** Prevents input interactions and removes its value from the form submission.\n* **Placeholder:** When there’s no value entered, show a placeholder with a potential value example. Don’t use placeholders as labels for the inputs.\n* **Label:** There should be a text label linked with the text field. Clicking the label should move the focus to the field.\n* **Error State:** The error state is used for form validation errors when the error is related to the text field only. Always use a text error along with changing the colour of the field.\n* **Focused State:** The focused state should highlight the text field when users start to interact with it. There is always only one focused field in the form.",
+ "links": []
+ },
+ "2T7tiM3Ew3H1U5iJR2TDb": {
+ "title": "List",
+ "description": "Lists define the layout of the page content or groups of elements stacking them vertically or horizontally.\n\n* **Support any type of content:** Lists can be used in any context from page-level layout to managing offsets between granular components. hey should work with any component used inside.\n* **Horizontal Stacking:** Lists can be used for inline elements and they have to manage how they’re stacked horizontally, including handling offsets between multiple rows of elements.\n* **Divided Variant:** Lists with dividers are the best practice advised by many platform guidelines (especially on mobile).\n* **Supports Actionable Content:** Sometimes lists are used for grouping tappable components, where the whole area of the list item should be clickable.",
+ "links": []
+ },
+ "JhnHOMIlU6mQcwvIpErUY": {
+ "title": "Loading Indicator",
+ "description": "The loading indicator shows that an operation’s being performed and how long the process will take.\n\n* **Linear and non-linear Variants:** Depending on the context and the component it’s used for, the loading indicator can be represented either with linear or with a non-linear (e.g. circular) variant.\n* **Determinate or indeterminate wait time:** In some cases, the wait time can’t be determined. The loading indicator should be shown until the loading finishes or an error happens. In other cases, it’s better to indicate how much time’s left until the loading is done.\n* **Light Variant:** The loading indicator should respect its parent element background and provide a variant to be used on darker background colours.\n* **Reduced Motion:** The loading indicator should be synced with the system motion settings and reduce its animation speed when reduced motion settings are turned on.",
+ "links": []
+ },
+ "IjNitkG25vNo30rB4ckNV": {
+ "title": "Modal",
+ "description": "Modals are containers appearing in front of the main content to provide critical information or an actionable piece of content.\n\n* **Supports any type of Content:** Like any other container, modals can be used in different scenarios and you should be able to use it with any other component inside.\n* **Supplementary Actions:** Since content in the modal may be actionable, it’s important to have an area for action elements. This area is usually located at the bottom of the modal container.\n* **Close Action:** Modals should provide a clear way to be closed as they’re blocking content when open. This may be either a separate close button or one of the supplementary actions.\n* **Information Structure:** Even though modals can be used as an empty container for the content, they need a defined information structure to provide a holistic experience. It may include defining how titles and subtitles look by default or where an action element’s area is.\n* **Keyboard Navigation Support:** It should be possible to close a modal by pressing the Esc key and all the focusable elements inside the modal container should be accessible with keyboard navigation.\n* **Focus Trapping:** Once a modal is opened, the focus should be moved to the first element inside the modal and should be looped within the modal container. Closing the modal should return the focus to the last focused element on the page.",
+ "links": []
+ },
+ "1vYR1EMyZhJA-znxnFBBb": {
+ "title": "Tabs",
+ "description": "Tabs organise navigation between multiple pages or content sections.\n\n* **Active Button State:** There should be a clear differentiation between selected and unselected tab buttons.\n* **Button Icon Support:** Icons help show the purpose of the tab buttons when used next to its label.\n* **Equally-sized tab buttons:** Tabs can be used in a relatively small-sized container where you need to switch between a definite number of sections. For such scenarios, it’s better to support a variant where the button’s area is divided equally.\n* **Keyboard Navigation:** All tab buttons should be focusable and navigation between the tab’s component should be accessible from the keyboard.\n* **Responsiveness:** If all tabs on mobile don’t fit into the viewport, users should still have access to all tab buttons. Ways to solve this can be making the button area scrollable for mobile or showing a More button containing a dropdown with the rest of the buttons.",
+ "links": []
+ },
+ "-T7uL6a3lJ5-IIcDaG6IN": {
+ "title": "Toast",
+ "description": "Toasts provide short meaningful feedback messages about the action results.\n\n* **Dismissed Automatically:** Toast messages shouldn’t interrupt the user flow, block the screen for a long time or require additional action from the user.\n* **Action Support:** Besides displaying the message, toasts may also provide an action related to the message like undoing an action.\n* **Handles Multiple Instances:** Even though it doesn’t happen often, toasts can be called from multiple sources at the same time and all resulting toasts should be queued. It’s good practice not to show all the messages at the same time.\n* **Accessibility:** Toast messages should be announced by the voice assistive technology and their action should be easily accessible from the keyboard.\n* **Responsivenss:** Toasts should be aligned with the mobile viewport and their action should be easily reachable for tapping.",
+ "links": []
+ },
+ "2oCAzsk_y2Y2oHUi467dp": {
+ "title": "Tooltip",
+ "description": "Tooltips are desktop-only components that display additional information when hovering over or focusing on an element.\n\n* **Keyboard Hover Support:** Tooltips should be accessible when an element is focused using the keyboard.\n* **Dynamic Positioning:** Tooltip content should be displayed based on the current position of the trigger element on the screen and always visible to the user.\n* **Hover Timeout:** Having a small timeout before triggering a tooltip will help to prevent occasionally showing tooltips while users move their mouse cursor.\n* **Light Variant:** The tooltip should respect its parent element background and provide a variant to be used on darker background colours.\n* **Instant Transition for Element Groups:** If there’s a group of elements using tooltips, hovering over another element while a tooltip’s already active shouldn’t trigger the animation.",
+ "links": []
+ },
+ "jggrr5nZOe6FY3ZrZJTOw": {
+ "title": "Tooling",
+ "description": "Design system tooling encompasses technical infrastructure and workflows. Effective tooling should integrate with design tools, provide component libraries for frameworks, implement token management, utilize documentation platforms, establish automated versioning, create testing infrastructure, and enable collaboration workflows.",
+ "links": []
+ },
+ "ccpT9MPFbc3Ewjm1tFMsZ": {
+ "title": "Design Editor",
+ "description": "There are many design editors available in the market today with the most popular names being Sketch, Figma and Adobe XD. If you're unsure which route to go down it's often best to speak with your team.",
+ "links": []
+ },
+ "uO-2O0Jwh_DxrMAB9wxp1": {
+ "title": "Plugins",
+ "description": "Most popular Design Editors (Sketch and Figma, especially) come with third-party plugin support. Whilst it's best to use the editors in-built tools for laying out your components, plugins can bring in a range of useful data to populate them.",
+ "links": []
+ },
+ "CYY6nbQiC2pu5ATWmO6wA": {
+ "title": "Version Control",
+ "description": "Having your design versioned with semantic versioning will allow you to easily align design with development, roll back faulty changes and release changes in code and design at the same time.",
+ "links": []
+ },
+ "TiCNCRpMPgZUhn7JdaIZA": {
+ "title": "Contribution Guidelines",
+ "description": "Define the process of contributing to the UI and UX of the design system and document it in a discoverable place to make it easier for everyone to contribute.",
+ "links": []
+ },
+ "VeLiPzbGr22_Mh_8T2Gnf": {
+ "title": "Component Catalog",
+ "description": "Isolate your UI components’ environment outside of your product codebase to make sure they’re not dependent on any global dependencies and can be easily reused.",
+ "links": []
+ },
+ "k1Lwk_b6cLIeyQwc4RUh1": {
+ "title": "Documentation",
+ "description": "Having your code documented is key to driving adoption and reducing the load on the contributors.",
+ "links": []
+ },
+ "zEqFAuH9zmKTLwwgx54pW": {
+ "title": "Code Style",
+ "description": "Having a defined code style helps align the way code’s written in the system and increases development velocity. It should be automated with the tools provided for each platform.",
+ "links": []
+ },
+ "y8No8I0MltA91j4Q2toT0": {
+ "title": "Unit Testing",
+ "description": "Every part of the design system should be covered with unit tests. Once your system’s adopted, any change in the isolated environment may affect how the product works.",
+ "links": []
+ },
+ "yhP8EhyCWWRBLkYPyOFeg": {
+ "title": "Accessibility Testing",
+ "description": "Design systems should cover accessibility as much as possible. Making this automatic reduces the risk of inaccessible components or user flows in the product.",
+ "links": []
+ },
+ "ZLt1yJqinC8OSpqucC2dV": {
+ "title": "Semantic Versioning",
+ "description": "Version your code with semantic versioning that dictates how version numbers are assigned and incremented.",
+ "links": []
+ },
+ "CfWCQNaCJGL-egRhFhc4B": {
+ "title": "Release Strategy",
+ "description": "Design system releases should be automated and ideally use scripts ran locally or in remote CI pipelines to prevent broken releases.",
+ "links": []
+ },
+ "IVYe8oh1IWbUbxMZRxVQA": {
+ "title": "Commit Guidelines",
+ "description": "Automate the generation of your changelog by adopting a commit message guidelines that categorise and define the changes being made.",
+ "links": []
+ },
+ "wd9ZHZmqV7wbLN-9V4EQy": {
+ "title": "PR Templates",
+ "description": "Create pull request templates that outline the change being proposed to facilitate productive discussions.",
+ "links": []
+ },
+ "xJ1LAAhiZvbZOLRVc1HZa": {
+ "title": "Contribution Guidelines",
+ "description": "Define the process of contributing to the code of the design system. Document everything in a discoverable place to make it easier for everyone to contribute.",
+ "links": []
+ },
+ "JfXwzkN29UGz17FYHHE3A": {
+ "title": "Project Management",
+ "description": "Design systems are no different than any other project your team might take on. In order to successfully build and maintain one, you need a clear strategy that’s well executed daily, and you‘ll need to create opportunities for your colleagues to give feedback to help share your design system together.",
+ "links": []
+ },
+ "gMrX5600JqFDplriq-eU3": {
+ "title": "Roadmap",
+ "description": "Setting your short and long term vision and mapping things out helps you decide the steps to take, understand your place in the bigger picture and prioritise day-to-day tasks.",
+ "links": []
+ },
+ "ruPXxVwmD9vSlS7rBZmA-": {
+ "title": "Milestones",
+ "description": "Define milestones that act as bigger epics in your project management with the help of your roadmap. These will help you understand your progress.",
+ "links": []
+ },
+ "i39J0fk4DaPeNFIMbH0ap": {
+ "title": "Ticketing",
+ "description": "Make it easier to track your day-to-day progress by using ticketing software like Jira, Trello or GitHub. This’ll make it easier for others to submit feature proposals or bug reports.",
+ "links": []
+ },
+ "G8dOkM_4hP7wPF3QJ8y4g": {
+ "title": "Component Analytics",
+ "description": "Track the usage of your components. For development you can use built-in tools like Figma’s Design System Analytics. For the end product you can have a separate way of tracking per platform depending on the technology.",
+ "links": []
+ },
+ "xYqDmDpjwkShtL86nt-vY": {
+ "title": "Logging",
+ "description": "Implement a way to track and pinpoint component-related outages in your product.",
+ "links": []
+ },
+ "qiJGYYWL4naJX-MgZA9Ms": {
+ "title": "Tooling Analytics",
+ "description": "Track what tools are being used for your design system. Find out which ones are used the most and which features are the most popular.",
+ "links": []
+ },
+ "5znnOkpf9G9tdiMWB6Rut": {
+ "title": "Service and Health Metrics",
+ "description": "Define service and health metrics for your design system to set a benchmark on how well you’re doing. Common examples can be the number of tickets closed, improvements made or bugs fixed.",
+ "links": []
+ },
+ "eG8ranXuINtcqWfeMH5GW": {
+ "title": "Community Meetings",
+ "description": "Arrange community meetings with everyone who uses the design system. Share your knowledge and make proposals to improve the sense of community.",
+ "links": []
+ },
+ "LWrrKrhwXfMDKgbFW5DuO": {
+ "title": "Communication Channel",
+ "description": "Most product development work happens digitally, so create a digital channel where people can reach out and ask questions.",
+ "links": []
+ },
+ "YWoPoO9IW3vLZyxLL2fnT": {
+ "title": "Open Hours",
+ "description": "Create open hours in which you can engage your audience in a more private setting where you can discuss things in more detail. You can also use these as peer coding or peer design opportunities.",
+ "links": []
+ },
+ "cpAeotBxN8BCsU9RqTEue": {
+ "title": "FAQs",
+ "description": "To save everyone time, define which questions are asked frequently by your audience and document them in a discoverable place.",
+ "links": []
+ }
+}
\ No newline at end of file
diff --git a/public/roadmaps/golang.png b/public/roadmaps/golang.png
index cd43c51c8..7489134ed 100644
Binary files a/public/roadmaps/golang.png and b/public/roadmaps/golang.png differ
diff --git a/readme.md b/readme.md
index ea7e3a647..e97e41e1a 100644
--- a/readme.md
+++ b/readme.md
@@ -1,5 +1,5 @@
+ 