In today's article, we'll compare how dynamic page implementation differs between Front-Commerce 2.x and Front-Commerce 3.x.

A dynamic page is generated on the fly when a user requests it, rather than being statically generated at build time. This is particularly useful for pages that rely on external data, such as product pages, category pages, or search pages. For this article, we are going to use an FAQ Article detail as an example.

This article aims to shed light on one of the most significant changes we've made in Front-Commerce 3.x, making it easier for you to understand.

As developers, we're no strangers to the crucial role configuration files play in our applications. They serve as the backbone, defining the behavior and structure of our systems. In this article, we'll dive into the transformative journey of configuration files in Front-Commerce, making a big leap from v2 to v3.

Progressive Web Applications (PWAs) are a way to deliver fast, reliable, and engaging user experiences on the web.

In Front-Commerce, we’ve always ensured that every applications could be turned into a PWA to improve the user experience. To achieve this, developers can rely on standard web features and technologies that we name “the PWA Stack”. Front-Commerce acts as a technical enabler to ease the lives of developers to create and maintain this stack.

In this blog post, we will explore the evolution of this “PWA Stack”, from its manual asset generation approach in Front-Commerce 2.x to the streamlined and automated process introduced in Front-Commerce 3.x.

Today is a special day! We need each one of you to help us make it a success.

We're launching Front-Commerce v3 on Product Hunt. Please support us by upvoting Front-Commerce and sharing it with your network.

This launch aims to introduce Front-Commerce to a broader audience, especially those who are not yet familiar with our product.

Read more for a step-by-step guide explaining how to upvote. It will take less than 1 minute!

Since 2016, Front-Commerce has been dedicated to supporting teams that operate in the Headless and Composable commerce space. Being among the first Frontend-as-a-service providers presented us with its unique challenges, but we have built solid foundations over the years.

Now, with Front-Commerce v3, we are excited to bring all our experience from the past seven years to the Remix ecosystem.

Read more to discover how Front-Commerce extends Remix to incorporate all the features available in Front-Commerce v2.

Starting from scratch is always exciting for a developer!

Creating new Front-Commerce projects quickly has endless advantages: build a minimal reproduction case for reporting issues, quickly test solutions, explain concepts to colleagues, or prototype for potential customers.

In this article we’ll explain how we made this process as smooth as possible, so you could start from a fresh, minimal state within seconds.

Front-Commerce serves as an important npm dependency in your e-commerce project, allowing you to update it as per your requirement. To ensure its seamless operation, we suggest adopting the following upgrade approach: semi-automated for patch versions and scheduled (2-3 times a year) for minor versions.

In today’s article, we’ll explain why we switched from a single Git dependency to several npm packages from a private registry.

We're happy to announce that we'll be sharing actionable insights with you about Front-Commerce!

As we get into 2024, we wanted to take a moment to reflect on our most important release so far: Front-Commerce Remixed!

When it comes to developing an e-commerce website, there are many different areas that require constant attention. Project teams may introduce performance issues or forget important features that could negatively impact the user experience. That's why audits are crucial to ensure that the website is meeting high standards and delivering a great user experience.

At Front-Commerce, we conduct thorough audits on our client projects and provide recommendations to improve website performance and user experience. In this blog post, we will discuss the key points we measure during our audits.

On most of the projects built with Front-Commerce, we perform an audit. Without surprise, these audits are conducted on the basis of a checklist. The first part is devoted to performance and the very first criterion is to evaluate the number of external requests necessary to build the most visited pages when everything is cached. The point is to target zero external request to generate those pages. Maybe you wonder why we check that or why we give it so much importance.