# Store launchpads overview

commercetools Frontend comes with out-of-the-box store launchpads to reduce development effort when building your digital commerce website.

## Available store launchpads

- **[Store Launchpad for B2C Retail](/frontend-development/b2c-store-launchpad-overview.md)**

  Build a B2C commerce website.

- **[Store Launchpad for B2B Manufacturing](/frontend-development/b2b-store-launchpad-overview.md)**

  Build a B2B commerce website.

## What store launchpads are

Store launchpads are ready-to-use codebases that include the following:

- Next.js code for [Frontend components](/frontend-development/development-concepts.md#components), including JSON [schemas](/frontend-development/schemas.md)
- The [extension for commercetools commerce APIs](/frontend-development/using-the-commercetools-extension.md) for B2C or B2B
- Pre-configurations of project settings and pages in the [Studio](/frontend-studio)

The purpose of store launchpads is to give you a starting point and guidance to develop your commerce website, thus reducing your time-to-market and helping you offer a seamless and engaging shopping experience to your customers.
Store launchpads serve as foundational templates that you can customize, extend, or use as they are. Also, because every project is unique, you can use the full store launchpad or only some components, depending on your needs.

The store launchpad codebases target [Web Content Accessibility Guidelines (WCAG) 2.2 level AA](https://www.w3.org/TR/WCAG22/) as its foundation for web and digital accessibility requirements.

## What store launchpads are not

Store launchpads are not libraries nor monolithic storefronts limited in flexibility.

## Who are store launchpads for

Store launchpads are designed for organizations who want to expedite the launch of their commerce website and are looking for tools to make their work faster. However, even if you are planning to build a completely custom commerce website, store launchpads can help you understand how to work with commercetools Frontend because they outline the best practices to develop Frontend components and [extensions](/frontend-development/extensions.md).

## Store launchpads vs. commercetools Frontend

The purpose of store launchpads is to showcase the capabilities of commercetools Frontend together with the commercetools commerce APIs. Unlike Frontend, which is one of commercetools' products, store launchpads are ready-to-use codebases on top of Frontend.

We constantly improve both Frontend and store launchpads. However, while Frontend is automatically updated by us as a SaaS product, store launchpads are not. When store launchpads are added to your Frontend project, they represent the state of the code at that point in time. Therefore, it is your responsibility to maintain and update them.

## Update store launchpads

Once you start using and modifying store launchpads, it becomes your responsibility to maintain and update them. However, we provide resources to ease this process. You can consult the related Storybook and GitHub public repository to check the latest releases. Then, you can manually incorporate these changes into your codebase to keep it up-to-date.

- Storybook:
  - [Store Launchpad for B2C Retail](https://poc-b2cdev.frontend.site/storybook/)
  - [Store Launchpad for B2B Manufacturing](https://poc-b2bdev.frontend.site/storybook/)
- GitHub public repository:
  - [Store Launchpad for B2C Retail](https://github.com/FrontasticGmbH/scaffold-b2c/)
  - [Store Launchpad for B2B Manufacturing](https://github.com/FrontasticGmbH/scaffold-b2b/)

## Provide feedback on store launchpads

You can submit your feedback, questions, and suggestions about store launchpads by creating an issue in the related public GitHub repository or by contacting the [commercetools support team](https://support.commercetools.com/).

## Related pages

- [Area overview page with navigation](/frontend-development.md)
- [Next page: Best practices for accessibility](/frontend-development/launchpad-accessibility.md)