EDU-15679 - Review 'Getting started with storefront solutions' #2104
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
barbara-celi
changed the title
|
Frontmatter errors in
|
Navigation Preview LinkNo changes detected in the navigation.json file |
Preview LinksOpen this URL to set up the portal with this branch changes. You can now access the edited pages with the following URLs: |
Grammar review summaryReview for
|
Documentation feedback for docs/guides/vtex-io/Storefront-Guides/getting-started-with-storefront-solutions.mdGeneral FeedbackThe document provides a comprehensive comparison of VTEX storefront solutions (FastStore, Store Framework, and Legacy CMS Portal). However, it does not adhere to the structure and purpose of a Guide as defined in the provided rules. The document is more of a comparison table or overview rather than a task-oriented guide. It lacks instructions on how to achieve a specific goal. Therefore, it needs to be restructured or refocused to align with the Guide format. Actionable Feedback
Suggested RevisionWas this feedback useful?
|
|
Frontmatter errors in
|
Grammar review summaryReview for
|
barbara-celi
commented
Aug 12, 2025
| | [**Reviews & Ratings**](https://developers.vtex.com/docs/apps/vtex.reviews-and-ratings) | ⚠️ | ✅ | ❌ | | ||
| | [**Store Locator**](https://developers.vtex.com/docs/apps/vtex.store-locator) | ⚠️ | ✅ | ❌ | | ||
| | [**Wishlist**](https://developers.vtex.com/docs/apps/vtex.wish-list) | ⚠️ | ✅ | ❌ | | ||
|
|
There was a problem hiding this comment.
@carolinamenezes , eu excluí esse tópico por causa do release note sobre apps deprecados. A maioria das apps nessa tabela aqui não tem mais suporte.
Passei o que restou (Intelligent Search e Live Shopping) pro tópico anterior.
barbara-celi
commented
Aug 12, 2025
| ✅ **Available:** An out-of-the-box feature, ready to use. | ||
|
|
||
| ⚠️ **Limited:** The feature is possible but needs custom implementation. | ||
| ⚠️ **Limited:** The feature is possible but requires custom implementation. To understand the viability of this implementation for your project, open a ticket with [VTEX Support](https://help.vtex.com/en/support). |
There was a problem hiding this comment.
Estou validando com o time da FS se vale a pena manter essas features com
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
Frontmatter errors in
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
docs/guides/vtex-io/Storefront-Guides/getting-started-with-storefront-solutions.md
Show resolved
Hide resolved
Grammar review summaryReview for
|
| --- | ||
|
|
||
| The VTEX platform provides three options for storefront development, each with distinct characteristics to meet the needs of our clients: | ||
| The VTEX platform provides three options for storefront development, each with distinct characteristics. This guide compares them to help you choose the best option for your business needs. |
There was a problem hiding this comment.
[markdownlint-fix] reported by reviewdog 🐶
Suggested change
| The VTEX platform provides three options for storefront development, each with distinct characteristics. This guide compares them to help you choose the best option for your business needs. | |
| The VTEX platform provides three options for storefront development, each with distinct characteristics. This guide compares them to help you choose the best option for your business needs. |
github-actions
bot
force-pushed
the
main
branch
from
fd49c61 to
bba71c2
Compare
carolinamenezes
approved these changes
Aug 27, 2025
github-actions
bot
force-pushed
the
main
branch
from
207b06e to
1315392
Compare
github-actions
bot
force-pushed
the
main
branch
2 times, most recently
from
44809f5 to
9e4dab3
Compare
|
Frontmatter errors in
|
Documentation feedback for docs/localization/getting-started-with-storefront-solutions.mdxGeneral FeedbackThe document provides a comprehensive comparison of VTEX storefront solutions (FastStore, Store Framework, and Legacy CMS Portal). However, it does not adhere to the structure of a Guide, as it lacks the required sections like "Before you begin" and "Instructions." The title also doesn't follow the gerund form. The content is more of a comparison document than a how-to guide. Actionable Feedback
Suggested Revision---
title: "Choosing a Storefront Solution for Your VTEX Store"
slug: "choosing-a-storefront-solution-for-your-vtex-store"
hidden: false
excerpt: "Learn how to choose the best VTEX storefront solution for your business needs by comparing FastStore, Store Framework, and Legacy CMS Portal."
createdAt: "2024-05-20t12:59:27.687Z"
updatedAt: "2025-10-01T19:16:58.931Z"
---
This guide will help you choose the best VTEX storefront solution for your business needs. By understanding the differences between FastStore, Store Framework, and Legacy CMS Portal, you'll be able to make an informed decision that aligns with your technical capabilities, business goals, and desired level of customization.
## Before you begin
* Familiarize yourself with the basic concepts of VTEX IO, FastStore, and the Legacy CMS Portal. You can find more information in the [VTEX Help Center](https://help.vtex.com/).
* Identify your store's key requirements, such as performance needs, desired level of customization, and integration with other VTEX services.
## Instructions
### Step 1 - Understand the Core Differences
The VTEX platform provides three options for storefront development, each with distinct characteristics:
* **FastStore:** Innovative technology that prioritizes performance and stability, offering operational teams an easily maintainable solution for editing store pages.
* **Store Framework:** Emphasizes a composable commerce model, allowing the integration of VTEX IO apps for dynamic storefronts.
* **Legacy CMS Portal:** VTEX’s first storefront technology that relies on HTML, CSS, and JavaScript, with code management exclusively through the VTEX Admin.
### Step 2 - Compare the Storefront Solutions
The following table outlines the main differences between VTEX FastStore, Store Framework, and Legacy CMS Portal. Use this table to evaluate which solution best fits your needs.
| | FastStore | Store Framework | Legacy CMS Portal |
| --- | --- | --- | --- |
| **Storefront development** | FastStore is built with a **performance** focus based on the Jamstack (JavaScript, API, and Markup) architecture.<br><br>Development is done through the integration of `npm` packages provided by VTEX and customizations via the extensibility of VTEX API core services. | Store Framework is based on **composability**, as development is based on VTEX IO apps, allowing the combination of different content, services, and data. | Development is done through the Admin, using the [Legacy Content Management System (CMS)](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC). |
| **Tech stack** | <ul><li>[React](https://react.dev/)</li><li>[Typescript](https://www.typescriptlang.org/)</li><li>[Node.js](https://nodejs.org/)</li><li>[Next.js](https://nextjs.org/)</li><li>[GraphQL](https://graphql.org/)</li></ul> | <ul><li>[React](https://react.dev/)</li><li>[TypeScript](https://www.typescriptlang.org/)</li><li>[Node.js](https://nodejs.org/)</li><li>[.NET](https://learn.microsoft.com/pt-pt/dotnet/)</li><li>[GraphQL](https://graphql.org/)</li></ul> | <ul><li>[CSS](https://developer.mozilla.org/pt-BR/docs/Web/CSS/)</li><li>HTML</li><li>JavaScript</li></ul> |
| **Starter (initial template)** | After completing the [FastStore Starter](https://starter.vtex.app/), you can access [FastStore Onboarding](https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview). This allows you to kick off the project with a base template focused on performance. | [Store Theme](https://github.com/vtex-apps/store-theme) is the initial template you can use to launch the storefront project or start from scratch. | The [Layout](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj#layout) section allows you to create your storefront with HTML and CSS.<br><br>In it, you can find the standard [templates](https://help.vtex.com/en/tutorial/what-are-templates--4l7BQBYO9ycumsqua2CU88), which are files that contain the code of your website pages. |
| **CMS solution** | Integrated with [Headless CMS](https://developers.vtex.com/docs/guides/faststore/headless-cms-overview). | Integrated with [Site Editor](https://developers.vtex.com/docs/guides/vtex-io-documentation-site-editor). | The [Layout](https://help.vtex.com/en/tutorial/what-is-cms-layout--EmO8u2WBj2W4MUQCS8262) feature allows you to create your storefront with HTML and CSS. |
| **Deployment platform** | Store deployment through [FastStore WebOps](https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview) and VTEX GitHub quality assurance bots. | Store deployment through the [VTEX IO platform](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) using the [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-installation-and-command-reference). | Content updates are done directly through the CMS. |
| **Deployment environment** | Supports running a [local server](https://developers.vtex.com/docs/guides/faststore/getting-started-2-setting-up-the-project#step-2-running-a-local-server), which works as a development environment. Changes made in the local development server don't impact the live store. | Supports creating [development workspaces](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-development-workspace) and [production workspaces](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-production-workspace), allowing developers to deploy changes confidently, without affecting the live store. | Doesn't have a separate development environment. |
| **Admin Apps (Extensions Hub)** | The VTEX IO backend apps can work on FastStore through the [API Extensions](https://developers.vtex.com/docs/guides/faststore/api-extensions-overview) tool. Frontend apps that manipulate React components aren't available. | Allows installation and use. | Allows installation and use of some apps. |
| **Customizations** | Performance-focused: Allows customization through [Theming](https://developers.vtex.com/docs/guides/faststore/using-themes-overview), [Overrides](https://developers.vtex.com/docs/guides/faststore/overrides-overview), [API extensions](https://developers.vtex.com/docs/guides/faststore/api-extensions-overview), and [Dynamic Content](https://developers.vtex.com/docs/guides/faststore/dynamic-content-overview) features. | Composability-focused: Flexible and customizable through [VTEX IO apps](https://developers.vtex.com/docs/vtex-io-apps). | Customizations are limited and can be managed by creating, organizing, and editing the structure of folders, files, and components within the [Layout](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj#layout) feature. |
| **Performance** | Maximum performance possible, as it uses [Jamstack](https://jamstack.org/), a framework focused on performance that serves pre-rendered content to a CDN. It's made dynamic through APIs and serverless functions.<br><br>Additionally, FastStore leverages [Partytown](https://partytown.builder.io/) for minimizing performance degradation caused by third-party scripts.<br><br>Built with performance as a core principle, FastStore not only optimizes speed but also provides clear visibility into performance metrics, ensuring transparency. | SSR (Server-Side Rendering) features generate the complete HTML of a page on the server as a response to a page request, while SPA (Single-Page Application) loads elements such as the header only once the page is loaded. | Outdated technologies make it challenging to maintain optimal performance, especially in scenarios demanding multiple customizations. |
| **Availability**<br><br>_You can have both FastStore and Store Framework running simultaneously in your store, as the environments are completely different._ | General availability.<br><br>For information on unavailable features, check the [Business models](#business-models) and [Features and Functionalities](#features-and-functionalities) sections. | General availability. | No longer available to new stores starting to use VTEX. |
| **Support**<br><br>_To learn more about our support, see our documentation [Responsibilities within the VTEX ecosystem](https://help.vtex.com/en/tutorial/responsabilidades-no-ecossistema-vtex--3vL9aWICDr3WR64DYi1fJ3)._ | Available for VTEX core commerce services, [FastStore packages](https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore), and troubleshooting code issues. | Available for VTEX core commerce services, VTEX IO native apps or components, and troubleshooting code issues. | Available for [VTEX core commerce services](https://developers.vtex.com/docs/guides/getting-started#vtex-core-services), and VTEX native [Controls](https://developers.vtex.com/docs/guides/list-of-controls-for-templates) and [Templates](https://help.vtex.com/en/tutorial/what-are-templates--4l7BQBYO9ycumsqua2CU88). |
### Step 3 - Consider Business Models
The VTEX platform supports the configuration of different business models, such as business-to-business (B2B), marketplaces, omnichannel, and internationalization. See below the availability for each storefront technology.
| | FastStore | Store Framework | Legacy CMS Portal |
| --- | :---: | :---: | :---: |
| [**B2B capabilities**](https://help.vtex.com/en/tutorial/b2b-overview--5vb9SNXhX2bZnkpAh7ADdC?\&utm_source=autocomplete) | ❌ | ✅ | ❌ |
| [**Bindings**](https://help.vtex.com/en/tutorial/what-is-binding--4NcN3NJd0IeYccgWCI8O2W?\&utm_source=autocomplete) | ❌ | ✅ | ✅ |
| [**Cross-border and multi-language stores**](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs) | ❌ | ✅ | ❌ |
| [**Franchise accounts**](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) | ✅ | ✅ | ✅ |
| [**Marketplace capabilities**](https://help.vtex.com/en/tutorial/marketplace-strategies-at-vtex--tutorials_402) | ✅ | ✅ | ✅ |
| [**Multiple trade policies**](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV) | ✅ | ✅ | ✅ |
### Step 4 - Evaluate Features and Functionalities
Explore below the features and functionalities available for each storefront technology. Consider the following legend:
✅ **Available:** An out-of-the-box feature, ready to use.
⚠️ **Limited:** The feature is possible but requires custom implementation. To understand the viability of this implementation for your project, open a ticket with [VTEX Support](https://help.vtex.com/en/support).
❌ **Not available:** This feature is currently unavailable, even with customizations.
#### Advanced store functionalities
| | FastStore | Store Framework | Legacy CMS Portal |
| --- | :---: | :---: | :---: |
| [**Abandoned Cart**](https://help.vtex.com/en/tutorial/setting-up-abandoned-carts--tutorials_740) | ⚠️ | ✅ | ✅ |
| [**Attachments**](https://help.vtex.com/en/tutorial/what-is-an-attachment--aGICk0RVbqKg6GYmQcWUm) | ✅ | ✅ | ✅ |
| [**Coupons**](https://help.vtex.com/en/tutorial/coupons-beta--1aAEN3ADpz19ss5JCIEBdL) | ✅ | ✅ | ✅ |
| [**Delivery Promise**](https://help.vtex.com/en/tutorial/delivery-promise-beta--p9EJH9GgxL0JceA6dBswd) | ✅ | ✅ | ❌ |
| [**Gift Card**](https://developers.vtex.com/docs/guides/gift-card-integration-guide) **integration** | ✅ | ✅ | ✅ |
| [**GTM - Google Analytics 4**](https://help.vtex.com/en/tutorial/how-to-setup-google-analytics-in-vtex-store--G2P0rmSrEiqCcmUMyUUwG) | ✅ | ✅ | ✅ |
| [**Intelligent Search**](https://help.vtex.com/tracks/vtex-intelligent-search) **integration** | ✅ | ✅ | ❌ |
| [**Live Shopping**](https://developers.vtex.com/docs/apps/vtexventures.livestreaming) | ⚠️ | ✅ | ✅ |
| [**Master Data**](https://developers.vtex.com/docs/guides/master-data) **integration** | ⚠️ | ✅ | ✅ |
| [**Newsletter integration with Master Data**](https://developers.vtex.com/docs/guides/implementing-newsletter-opt-in-with-master-data-v1) | ✅ | ✅ | ✅ |
| [**Price table**](https://help.vtex.com/en/tutorial/creating-price-tables--58YmY2Iwggyw4WeSCGg24S) | ✅ | ✅ | ✅ |
| [**Promotions**](https://help.vtex.com/en/tutorial/creating-promotions--tutorials_320) | ✅ | ✅ | ✅ |
| [**Regionalization**](https://developers.vtex.com/docs/guides/faststore/features-regionalization) | ✅ | ✅ | ❌ |
| [**SmartCheckout**](https://help.vtex.com/en/tutorial/smartcheckout-customer-information-automatic-fill-in--2Nuu3xAFzdhIzJIldAdtan) | ✅ | ✅ | ✅ |
| [**Sitemap**](https://help.vtex.com/en/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) **integration** | ✅ | ✅ | ✅ |
| [**Subscription**](https://help.vtex.com/en/tutorial/how-subscriptions-work--frequentlyAskedQuestions_4453) | ✅ | ✅ | ✅ |
| **Support for** [**VTEX IO frontend apps**](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developing-storefront-apps-using-react-and-vtex-io) | ❌ | ✅ | ❌ |
#### Development experience
| | FastStore | Store Framework | Legacy CMS Portal |
| --- | --- | --- | :---: |
| **API integration** | ✅ [FastStore APIs](https://developers.vtex.com/docs/guides/faststore/faststore-api-overview) | ✅ [API reference](https://developers.vtex.com/docs/api-reference) | ✅ [API reference](https://developers.vtex.com/docs/api-reference) |
| **Automatic storefront updates** | ✅ | ✅ | ❌ |
| **Command Line Interface (CLI)** | ✅ [FastStore CLI](https://developers.vtex.com/docs/guides/faststore/getting-started-3-faststore-cli) | ✅ [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-installation-and-command-reference) | ❌ |
| **GitHub [WebOps](https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview) workflow** | ✅ | ❌ | ❌ |
Learn more in [Developer experience](https://developers.vtex.com/docs/guides/developer-experience).
## Next steps
* Explore the documentation for your chosen storefront solution: [FastStore](https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore), [Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io), or [Legacy CMS Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC).
* Start building your storefront by following the getting started guides for each solution.
* Consider the long-term maintainability and scalability of your chosen solution.Was this feedback useful?
|
Grammar review summaryReview for
|
| | **Customizations** | Performance-focused: Allows customization through [Theming](https://developers.vtex.com/docs/guides/faststore/using-themes-overview), [Overrides](https://developers.vtex.com/docs/guides/faststore/overrides-overview), [API extensions](https://developers.vtex.com/docs/guides/faststore/api-extensions-overview), and [Dynamic Content](https://developers.vtex.com/docs/guides/faststore/dynamic-content-overview) features. | Composability-focused: Flexible and customizable through [VTEX IO apps](https://developers.vtex.com/docs/vtex-io-apps). | Customizations are limited and can be managed by creating, organizing, and editing the structure of folders, files, and components within the [Layout](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj#layout) feature. | | ||
| | **Performance** | Maximum performance possible, as it uses [Jamstack](https://jamstack.org/), a framework focused on performance that serves pre-rendered content to a CDN. It is made dynamic through APIs and serverless functions.<br><br>Additionally, FastStore leverages [Partytown](https://partytown.builder.io/) for minimizing performance degradation caused by third-party scripts.<br><br>Built with performance as a core principle, FastStore not only optimizes speed but also provides clear visibility into performance metrics, ensuring transparency. | SSR (Server-Side Rendering) features generate the complete HTML of a page on the server as a response to a page request, while SPA (Single-Page Application) loads elements such as the header only once the page is loaded. | Outdated technologies make it challenging to maintain optimal performance, especially in scenarios demanding multiple customizations. | | ||
| | **Availability**<br><br>_You can have both FastStore and Store Framework running simultaneously in your store, as the environments are completely different._ | General availability.<br><br>For information on unavailable features, check the [Business models](#business-models) and [Features and Functionalities](#features-and-funcionalities) sections. | General availability. | No longer available to new stores starting to use VTEX. | | ||
| | **Performance** | Maximum performance possible, as it uses [Jamstack](https://jamstack.org/), a framework focused on performance that serves pre-rendered content to a CDN. It's made dynamic through APIs and serverless functions.<br><br>Additionally, FastStore leverages [Partytown](https://partytown.builder.io/) for minimizing performance degradation caused by third-party scripts.<br><br>Built with performance as a core principle, FastStore not only optimizes speed but also provides clear visibility into performance metrics, ensuring transparency. | SSR (Server-Side Rendering) features generate the complete HTML of a page on the server as a response to a page request, while SPA (Single-Page Application) loads elements such as the header only once the page is loaded. | Outdated technologies make it challenging to maintain optimal performance, especially in scenarios demanding multiple customizations. | |
There was a problem hiding this comment.
📝 [Grammar reviewer] reported by reviewdog 🐶
- The pronoun 'It' in the original sentence is ambiguous. Clarifying the subject to 'Jamstack' makes the statement more precise and accurately describes the framework's capability.
- The original sentence was long and the description of SPA was slightly inaccurate and confusing. 'Features generate' is awkward. The corrected version clarifies that SSR generates the HTML and provides a more precise and accurate description of how SPA handles initial loading versus subsequent dynamic updates, improving clarity and technical accuracy.
Suggested change
| | **Performance** | Maximum performance possible, as it uses [Jamstack](https://jamstack.org/), a framework focused on performance that serves pre-rendered content to a CDN. It's made dynamic through APIs and serverless functions.<br><br>Additionally, FastStore leverages [Partytown](https://partytown.builder.io/) for minimizing performance degradation caused by third-party scripts.<br><br>Built with performance as a core principle, FastStore not only optimizes speed but also provides clear visibility into performance metrics, ensuring transparency. | SSR (Server-Side Rendering) features generate the complete HTML of a page on the server as a response to a page request, while SPA (Single-Page Application) loads elements such as the header only once the page is loaded. | Outdated technologies make it challenging to maintain optimal performance, especially in scenarios demanding multiple customizations. | | |
| | **Performance** | Maximum performance possible, as it uses [Jamstack](https://jamstack.org/), a framework focused on performance that serves pre-rendered content to a CDN. Jamstack enables dynamism through APIs and serverless functions.<br><br>Additionally, FastStore leverages [Partytown](https://partytown.builder.io/) for minimizing performance degradation caused by third-party scripts.<br><br>Built with performance as a core principle, FastStore not only optimizes speed but also provides clear visibility into performance metrics, ensuring transparency. | SSR (Server-Side Rendering) generates the complete HTML of a page on the server in response to a page request. In contrast, SPA (Single-Page Application) loads its core elements, such as the header, only once during the initial page load, and then dynamically updates content. | Outdated technologies make it challenging to maintain optimal performance, especially in scenarios demanding multiple customizations. | |
| | **Performance** | Maximum performance possible, as it uses [Jamstack](https://jamstack.org/), a framework focused on performance that serves pre-rendered content to a CDN. It is made dynamic through APIs and serverless functions.<br><br>Additionally, FastStore leverages [Partytown](https://partytown.builder.io/) for minimizing performance degradation caused by third-party scripts.<br><br>Built with performance as a core principle, FastStore not only optimizes speed but also provides clear visibility into performance metrics, ensuring transparency. | SSR (Server-Side Rendering) features generate the complete HTML of a page on the server as a response to a page request, while SPA (Single-Page Application) loads elements such as the header only once the page is loaded. | Outdated technologies make it challenging to maintain optimal performance, especially in scenarios demanding multiple customizations. | | ||
| | **Availability**<br><br>_You can have both FastStore and Store Framework running simultaneously in your store, as the environments are completely different._ | General availability.<br><br>For information on unavailable features, check the [Business models](#business-models) and [Features and Functionalities](#features-and-funcionalities) sections. | General availability. | No longer available to new stores starting to use VTEX. | | ||
| | **Performance** | Maximum performance possible, as it uses [Jamstack](https://jamstack.org/), a framework focused on performance that serves pre-rendered content to a CDN. It's made dynamic through APIs and serverless functions.<br><br>Additionally, FastStore leverages [Partytown](https://partytown.builder.io/) for minimizing performance degradation caused by third-party scripts.<br><br>Built with performance as a core principle, FastStore not only optimizes speed but also provides clear visibility into performance metrics, ensuring transparency. | SSR (Server-Side Rendering) features generate the complete HTML of a page on the server as a response to a page request, while SPA (Single-Page Application) loads elements such as the header only once the page is loaded. | Outdated technologies make it challenging to maintain optimal performance, especially in scenarios demanding multiple customizations. | | ||
| | **Availability**<br><br>_You can have both FastStore and Store Framework running simultaneously in your store, as the environments are completely different._ | General availability.<br><br>For information on unavailable features, check the [Business models](#business-models) and [Features and Functionalities](#features-and-functionalities) sections. | General availability. | No longer available to new stores starting to use VTEX. | |
There was a problem hiding this comment.
📝 [Grammar reviewer] reported by reviewdog 🐶
The phrase 'starting to use VTEX' is redundant when combined with 'new stores.' 'New VTEX stores' is more concise and clear.
Suggested change
| | **Availability**<br><br>_You can have both FastStore and Store Framework running simultaneously in your store, as the environments are completely different._ | General availability.<br><br>For information on unavailable features, check the [Business models](#business-models) and [Features and Functionalities](#features-and-functionalities) sections. | General availability. | No longer available to new stores starting to use VTEX. | | |
| | **Availability**<br><br>_You can have both FastStore and Store Framework running simultaneously in your store, as the environments are completely different._ | General availability.<br><br>For information on unavailable features, check the [Business models](#business-models) and [Features and Functionalities](#features-and-functionalities) sections. | General availability. | No longer available to new VTEX stores. | |
| ## Features and functionalities | ||
|
|
||
| Below, explore the features and functionalities available for each storefront technology. Consider the following legend: | ||
| Explore below the features and functionalities available for each storefront technology. Consider the following legend: |
There was a problem hiding this comment.
📝 [Grammar reviewer] reported by reviewdog 🐶
Placing 'below' at the end of the sentence is more natural and improves the flow of the sentence in English.
Suggested change
| Explore below the features and functionalities available for each storefront technology. Consider the following legend: | |
| Explore the features and functionalities available for each storefront technology below. Consider the following legend: |
There was a problem hiding this comment.
📝 [Grammar reviewer] reported by reviewdog 🐶
- The acronym 'API' should be plural ('APIs') to correctly reflect the standard definition of Jamstack, which stands for JavaScript, APIs, and Markup.
- While 'via' is acceptable, 'through' often provides a slightly clearer and more common phrasing when describing the means by which something is achieved, improving readability.
There was a problem hiding this comment.
📝 [Grammar reviewer] reported by reviewdog 🐶
'TypeScript' is a proper noun and should be capitalized with a capital 'S'.
There was a problem hiding this comment.
📝 [Grammar reviewer] reported by reviewdog 🐶
Adding 'for' after 'See below' improves the grammatical flow and naturalness of the English phrasing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Types of changes
EDU-15679