diff --git a/0_Introduction-mdx.300b2848.iframe.bundle.js b/0_Introduction-mdx.300b2848.iframe.bundle.js
deleted file mode 100644
index 0bfcdc4bd..000000000
--- a/0_Introduction-mdx.300b2848.iframe.bundle.js
+++ /dev/null
@@ -1 +0,0 @@
-"use strict";(globalThis.webpackChunk_atomium_docs=globalThis.webpackChunk_atomium_docs||[]).push([[1346],{"./stories/0_Introduction.mdx":(__unused_webpack_module,__webpack_exports__,__webpack_require__)=>{__webpack_require__.r(__webpack_exports__),__webpack_require__.d(__webpack_exports__,{default:()=>MDXContent});__webpack_require__("../../node_modules/react/index.js");var jsx_runtime=__webpack_require__("../../node_modules/react/jsx-runtime.js"),lib=__webpack_require__("../../node_modules/@mdx-js/react/lib/index.js"),dist=__webpack_require__("../../node_modules/@storybook/blocks/dist/index.mjs");const READMEraw_namespaceObject='\n\n\n
Atomium - Design System
\n
\n \n \n \n \n
\n
\n
| [README](./packages/core/README.md) |\n| React | [`@juntossomosmais/atomium/react`](https://github.com/juntossomosmais/atomium/pkgs/npm/atomium) | | [README](./packages/react/README.md) |\n| Vue | [`@juntossomosmais/atomium/vue`](https://github.com/juntossomosmais/atomium/pkgs/npm/atomium) | | [README](./packages/react/README.md) |\n| Tokens | [`@juntossomosmais/atomium-tokens`](https://github.com/juntossomosmais/atomium/pkgs/npm/atomium-tokens) | 
| [README](./packages/tokens/README.md) |\n\n## About\n\nIt is built using a variety of powerful technologies, including:\n\n- **NX**: a set of extensible dev tools for monorepos, which helps us build and manage multiple projects within a single repository.\n- **Stencil**: a web component compiler that generates standard-compliant components using TypeScript, JSX, and HTML.\n- **Ionic**: a set of UI components and tools that help developers build performant, high-quality mobile and desktop applications using web technologies.\n- **Storybook**: a user interface development environment and testing tool that allows us to create and showcase components in isolation.\n- **Typescript**: a typed superset of JavaScript that compiles to plain JavaScript, providing powerful tools for building large-scale applications.\n- **Web Components**: a set of standards that enable the creation of reusable, encapsulated components using open web technologies.\n\n## Getting Started\n\nClone the repository via `ssh`\n\n```sh\ngit clone git@github.com:juntossomosmais/atomium.git\n```\n\nCopy `.npmrc.example` to `.npmrc`.\n\nReplace `` in the `.npmrc` file with your [GitHub PAT](https://github.com/settings/tokens). Your PAT should have following scopes: `repo` and `write:packages`.\n\n### Installation\n\n```bash\nnpm i\nnpm run build\n```\n\nIf you get errors about unresolved dependencies, you may need to run `npm i --legacy-peer-deps` instead.\n\n### Running Storybook and Stencil\n\n```bash\nnpm start\n```\n\nIf you want to run React Stories locally, you need to run the following command before `npm start`:\n\n```bash\nnpm run docs-react:start\n```\n\nAnd if you want to run Vue Stories locally, you need to run the following command before `npm start`:\n\n```bash\nnpm run docs-vue:start\n```\n\n### Running Tests\n\n```bash\nnpm test\n```\n\n### Building\n\n```bash\n## Build Libs\nnpm run build\n\n## Build Storybook\nnpm run docs:build\n```\n\n## Main folder structure\n\n* `apps/docs`: Contains the main documentation for the project.\n* `apps/docs-react`: Provides a React version of Storybook for showcasing components.\n* `apps/docs-vue`: Provides a Vue version of Storybook for showcasing components.\n* `packages/core`: The core of Atomium, responsible for building all the components.\n* `packages/react`: The React version of Atomium, automatically generated by Stencil.\n* `packages/vue`: The Vue version of Atomium, automatically generated by Stencil.\n* `packages/tokens`: Contains the design tokens for Atomium, where all the tokens are defined.\n* `packages/icons`: Contains the icons used in Atomium, where all the icons are stored.\n* `utils/**`: Contains utility modules used throughout the project, providing various helper functions and tools.\n\n## Stories Documentation\n\nWe are using [Storybook](https://storybook.js.org/) to document our components.\n\n### Writing Stories\n\nComponents stories are written in `packages/core/**/*.core.mdx` files to Web Components version and `packages/core/**/*.react.mdx` files to React version and are automatically loaded by Storybook. You also can using a shared file called `packages/**/*.args.ts` to share the same args between Web Components and React version.\n\nTokens stories are written in `packages/tokens/**/*.mdx` files.\n\nGeneral documentation is written in `apps/docs/**/*.mdx` files.\n\nThese files are written in [MDX](https://mdxjs.com/).\n\n### Syntax Highlighting\n\nTo enable syntax highlighting in your editor, you need to install the following extensions:\n\n- [lit-html](https://marketplace.visualstudio.com/items?itemName=bierner.lit-html)\n\n## Local test using Alpha/Beta versions\n\nTo locally test Atomium using Alpha/Beta versions, follow the steps below:\n\n1. Update the `.release-please-manifest.json` file in the root directory of the Atomium project with the next version number + alpha. Ex: the current version is `2.10.0`, so the next alpha version can be `2.11.0-alpha.1` (OBS: in the example, it is updating only the core lib, update the libs that your changes impact).\n\n\n\n2. Add the same version to the repespective `package.json` file in the root directory of the lib project. Ex: packages/core/package.json\n\n\n\n3. Build the Atomium libraries by running the following command in the root directory of the Atomium project\n\n```bash\nnpx nx run @juntossomosmais/atomium:publish-library-alpha\n```\n\nOBS: you can even share the alpha version with your team, than they can test it locally.\n\n## Local test using NPM Link\n\nTo locally test Atomium using NPM Link, follow the steps below:\n\nBuild the Atomium libraries by running the following command in the root directory of the Atomium project\n\n```bash\nnpm run core:build\n```\n\nLink the Atomium libraries by navigating to the `node_modules/@juntossomosmais/atomium` directory\n\n```bash\ncd node_modules/@juntossomosmais/atomium\nnpm link\n```\n\nImport Atomium into your project by linking it using NPM Link. Navigate to your project\'s directory and run the following command\n\n```bash\nnpm link @juntossomosmais/atomium\n```\n\nThis will create a symbolic link between your project and the locally built Atomium libraries.\n\nNow you can use the imported Atomium components in your project and test them locally. Make sure to revert these changes and remove the NPM Link when you\'re done testing to avoid any conflicts or unexpected behavior with the actual installed version of Atomium in your project.\n\nBy following these steps, you can easily test and verify any customizations or modifications you have made to Atomium locally using NPM Link.\n\n## Deployment\n\nWe are using [GitHub Actions](https://github.com/juntossomosmais/atomium/actions), [GitHub Packages](https://github.com/orgs/juntossomosmais/packages?repo_name=atomium) and [release please](https://github.com/googleapis/release-please) to automate the release process.\n\nWhen a PR is merged into the `main` branch, the release process is triggered. The release process will create a new release and publish the packages to GitHub Packages.\n\n### Publish errors\n\nIf you get an error in Github Actions to publish to NPM, you can run the following command to restart the release process:\n\n1. Go to the [Releases](https://github.com/juntossomosmais/atomium/releases) and remove the release that failed\n2. Go to the [Tags](https://github.com/juntossomosmais/atomium/tags) and remove the tag that failed or run the following command in your terminal:\n\n```bash\ngit tag -d \ngit push origin --delete \n```\n\n3. Get the last commit hash from the [Commits](https://github.com/juntossomosmais/atomium/commits/main/) and run the following command in your terminal:\n\n```bash\ngit reset --hard \ngit push origin main --force\n```\n\n4. So, a new PR will be created and the release process will be triggered again\n\n\n## Contributing\n\n**!important**, as it\'s an internal design system, we don\'t accept external suggestions to change or add new components.\n\nWe only accept contributions from **Juntos Somos Mais** members, but you could like our project and use it as a reference to build your own design system.\n';function _createMdxContent(props){return(0,jsx_runtime.jsxs)(jsx_runtime.Fragment,{children:[(0,jsx_runtime.jsx)(dist.W8,{title:"Introduction"}),"\n",(0,jsx_runtime.jsx)(dist.oz,{children:READMEraw_namespaceObject})]})}function MDXContent(props={}){const{wrapper:MDXLayout}={...(0,lib.R)(),...props.components};return MDXLayout?(0,jsx_runtime.jsx)(MDXLayout,{...props,children:(0,jsx_runtime.jsx)(_createMdxContent,{...props})}):_createMdxContent()}}}]);
\ No newline at end of file
diff --git a/0_Introduction-mdx.d396cf27.iframe.bundle.js b/0_Introduction-mdx.d396cf27.iframe.bundle.js
new file mode 100644
index 000000000..52197ea6b
--- /dev/null
+++ b/0_Introduction-mdx.d396cf27.iframe.bundle.js
@@ -0,0 +1 @@
+"use strict";(globalThis.webpackChunk_atomium_docs=globalThis.webpackChunk_atomium_docs||[]).push([[1346],{"./stories/0_Introduction.mdx":(__unused_webpack_module,__webpack_exports__,__webpack_require__)=>{__webpack_require__.r(__webpack_exports__),__webpack_require__.d(__webpack_exports__,{default:()=>MDXContent});__webpack_require__("../../node_modules/react/index.js");var jsx_runtime=__webpack_require__("../../node_modules/react/jsx-runtime.js"),lib=__webpack_require__("../../node_modules/@mdx-js/react/lib/index.js"),dist=__webpack_require__("../../node_modules/@storybook/blocks/dist/index.mjs");const READMEraw_namespaceObject='\n\n\n
Atomium - Design System
\n
\n \n \n \n \n
\n
\n