chore: update README to reflect repository migration and archive status

Author: cmourullo

README.md

@@ -1,143 +1,26 @@
-# Store Launchpad for B2C Next.js Starter
+# Commerce commercetools Extension
 
-> :information_source: Full documentation can be found [Here](https://docs.commercetools.com/docs/frontend)
+## ⚠️ Important Notice: Repository Migration
 
-This is a commercetools Launchpad project that uses Next.js
+This repository is **archived**. For the latest updates, improvements, and ongoing development of the B2C components, please visit the official scaffold repository:
 
-# Getting Started With Frontend:
+**🔗 [Official B2C Scaffold Repository](https://github.com/FrontasticGmbH/scaffold-b2c)**
 
-## 1- Start the development environment
+## What This Means
 
-### Running locally in development mode
+- **Current Repository**: Will become read-only (archived)
+- **New Development**: All future updates will be published to the [scaffold-b2c repository](https://github.com/FrontasticGmbH/scaffold-b2b)
+- **Documentation**: Updated documentation and examples will be available in the new location
 
-```
-yarn install
-yarn dev
-```
+## Migration Steps
 
-### Building and deploying in production
+If you're currently using this B2C components:
 
-```
-yarn install
-yarn build
-yarn start
-```
+1. **Bookmark** the new repository: https://github.com/FrontasticGmbH/scaffold-b2c
+2. **Watch** the new repository for updates and releases
+3. **Migrate** your projects to use the latest version from the scaffold repository
+4. **Update** your documentation and team references
 
-### Running storybook
+---
 
-```
-yarn storybook
-```
-
-### Build a production storybook
-
-```
-yarn storybook:rebuild
-```
-
-## 2- Create a basic component
-
-```javascript
-export default function MyComponent(props) {
-  return <h1>{props.headline}</h1>;
-}
-```
-
-## 3- Create a tastic for your component
-
-### Under `/packages/frontend/frontastic/tastics/{{MyComponent}}`
-
-- Create a `schema.json`
-
-```json
-{
-  "tasticType": "my-component",
-  "name": "My Component",
-  "icon": "favorite",
-  "category": "Content",
-  "schema": [
-    {
-      "name": "Basic Options",
-      "fields": [
-        {
-          "label": "Headline",
-          "field": "headline",
-          "type": "string",
-          "required": true
-        }
-      ]
-    }
-  ]
-}
-```
-
-- Create an `index.tsx`
-
-```javascript
-export default function MyComponentTastic(props) {
-  return <MyComponent headline={props.data.headline} />;
-}
-```
-
-You can find more about tastics [Here](https://docs.frontastic.cloud/docs/creating-a-frontastic-component)
-
-## 4- Register your tastic
-
-### Under `/packages/frontend/frontastic/tastics/index.tsx`
-
-```javascript
-export const tastics = {
-    ...
-    'my-component': MyComponentTastic
-}
-```
-
-## 5- Finally upload your component to studio
-
-![Fig.1](https://files.readme.io/37460f8-Components_on_Frontastic_studio_dashboard_staging.png)
-![Fig.2](https://files.readme.io/4c30e4d-Click_add_icon_to_add_a_new_component.png)
-
-## That's it.. Now you're all set and can start using your new component in any page you like!
-
-<br />
-<hr />
-<br />
-
-## Linting
-
-This project uses linting rules that improve the Core Web Vitals of the storefront which are also the recommended rules by Next.js in addition to some other rules for react hooks, typescript, jest, etc...
-
-If you want more fine-grained configuration, feel free to configure the eslint rules by deactivating and/or extending them in the `.eslintrc.json` in the `frontend` folder.
-
-To run the linter, just run
-
-```
-yarn lint
-```
-
-To fix erros that can be automatically fixed, run
-
-```
-yarn lint:fix
-```
-
-We recommend to add linting directly to your code editor or development environment, to get immediate feedback.
-
-### Linting in vim
-
-There are a variety of extensions that can add linting support to vim and Neovim.
-If you're using vim, we recommend either [ALE](https://github.com/dense-analysis/ale)
-or [CoC](https://github.com/neoclide/coc.nvim) and if you use Neovim you can
-use the integrated Language Server Protocol to run [eslint_d](https://github.com/mantoni/eslint_d.js/) in the background.
-Here's [a handy guide](https://phelipetls.github.io/posts/configuring-eslint-to-work-with-neovim-lsp/) on how to do that
-
-### Linting in Visual Studio Code
-
-To integrate ESLint into Visual Studio Code, you will need to install the ESLint extension for Visual Studio Code. Search for ESLint in the Extensions tab and click Install once you have located the extension.
-Once ESLint is installed in Visual Studio Code, you’ll notice colorful underlining in your JS/TS files highlighting errors. These markers are color-coded based on severity. If you hover over your underlined code, you will see a message that explains the error to you.
-
-## Prettier / Code formatting
-
-Prettier is integrated with the linter so when running `yarn lint:fix` you'll have your code auto formatted as well.
-
-We also recommend to setup your editor to use prettier to format a document on save.
+**Thank you for your understanding during this transition. We're committed to providing you with the best possible development experience in our new, centralized repository structure.**