Menu
Feedback
Start here
Tutorials & Solutions
Developers Portal

Known Issues
Support Rules

Frequently Asked Questions
Announcements
Start here
VTEX Modules: Getting Started
Store developmentFrontend
Frontend
3 min read

The storefront is the presentation layer for the user. It defines their experience on the platform and is a key factor when deciding whether to complete a purchase or not. For a digital business to remain relevant and competitive, this layer must offer elements such as a great user experience (via desktop and mobile), omnichannel capability, customized shopping experience, and outstanding web performance.

To achieve these goals, VTEX provides different technologies for store frontend development. Depending on the project, one technology may be more suitable than the others.

Store Framework

Store Framework is based on composability, which allows the combination of different content, services, and data. So, in addition to integrations and API orchestration, VTEX offers the right tools to meet the most specific business needs.

The way this feature extension happens is through VTEX apps that are available globally.

Store Framework is a solution for building storefronts that leverages VTEX IO. Using it, you can rely on the user-friendly interface of Site Editor and easily manage store content.

{"base64":"  ","img":{"width":1600,"height":1452,"type":"png","mime":"image/png","wUnits":"px","hUnits":"px","length":192228,"url":"https://images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/5b55c0f934c47034373e47f9be09c754/image3.png"}}

Stores created with Store Framework also include:

  • Intelligent Search: Search tool that corrects spelling errors and enables conditional rules for displaying the search result.
  • Multi-language: VTEX IO enables the configuration of automatic translation into other languages in the store.
  • Cross-border: Allows a VTEX multi-store to operate in different countries with an approach specific to each of them.

FastStore

While Store Framework focuses on composability, FastStore was built with a performance focus and is based on the Jamstack (standing for JavaScript, API, and Markup) architecture. In Jamstack websites, the application logic generally lies on the client side without being tightly coupled to the backend server.

The intention is to leverage the Jamstack architecture to deliver storefronts quickly, securely, and reliably. In addition, it comes with many tools and features designed for this purpose, including WebOps pipelines and performance-optimized starter packs.

In this way, FastStore can integrate with any CMS and any development platform, but to benefit from the guarantees and support provided by VTEX, the FastStore, Webops, and Headless CMS is required.

Some features are not available, such as My Account customizations and full integration with IO apps and Intelligent Search.

CMS Portal (Legacy)

The CMS Portal is a legacy VTEX technology mainly responsible for managing the website's source code, which is the module containing the content displayed in the store.

For the Legacy CMS, an important concept is Controls, which are snippets of code that render native VTEX data. Controls help the retailer natively create content and embed tools on the site using what VTEX already offers. For this customization to happen, CSS, HTML, and JavaScript are used in the development, allowing you to create layouts and templates.

Due to the use of outdated technologies, when you need to make any changes in the legacy CMS, you have to access the codes internally and make the changes in the Layout field. Thus, CMS becomes more difficult to use and maintain, making it harder to keep up performance as more customizations are made.

Contributors
1
Photo of the contributor
+ 1 contributors
Was this helpful?
Yes
No
Suggest edits (Github)
Store development
« Previous
Backend
Next »
Contributors
1
Photo of the contributor
+ 1 contributors
On this page
Still got questions?
Request support from VTEX
For personalized assistance, contact our experts.
Open a support ticket
Ask the community
Find solutions and share ideas in the VTEX community.
Join our community
GithubDevelopers PortalCommunityFeedbackSite Map