Retail eCommerce Remix.run Boilerplate
The furniture boilerplate is a fully-featured eCommerce boilerplate built using Remix and Crystallize. The boilerplate was developed with performance, a good developer experience, and best practices in mind. Visit the live demo to have a better look around.
npx @crystallize/cli-next@latest install ~/my-projects/my-ecommerce
The CLI gives you the option to bootstrap your tenant with all the demo data the furniture store has.
Once the development server is running, you will be able to browse to http://localhost:3018/.
The app is contained within the src folder that is located in the applications folder.
The assets folder has all the icons that are being used in the application. All of these are SVG files and you can add or remove these as required.
As the name suggests, this folder has all the styles being used in the application. So if you would like to change the colors and the font, the default.css file in the tailwind folder is where you would go to edit those. Additional component styles are defined in the index.css file present in this folder.
The translation folder contains the translation files.
This is all the “Use Cases” everything that is business related, you can see that as the “Domain” folder. There is no connection to the UI nor to the Framework in this folder. You will mainly find functions, that does meaningful actions like `fetchSomething`, `pushSomething`, `doSomething`. For instance, it is where all the queries used to fetch data from the APIs, in addition to functions that enable you to push customers and orders to Crystallize, while the latter contains everything related to the Service API.
That the User Interface, this folder contains all the components and the pages as well as the Hooks and Providers.
The routes folder contains all the pages the application has. There are some predefined routes such as shop, checkout, orders, etc. However, we also have what Remix refers to as a splat route that would render a page based on whatever shape it has - product, document, or folder.
This folder is really framework specific and connected to Remix Run.
This is where all the framework and server side specific are organized. Authentication, Mailer, BackendStorage etc.
Let’s take a deeper look at the core folder in this section.
The first folder in core contains the forms you will see throughout the site, namely on the checkout page. This includes the login form via a magic link as well as the user information page on checkout.
The layout for components specific to Crystallize, such as the paragraph collection, the properties tables, and the file component, can be found here. You can find these components on the product and the individual story pages in the app.
The boilerplate contains curated products that are part of curated stories. Once a user selects a curated product, they can then select different variants for it. To edit the layout there, you will edit the index file in this folder.
Each category in the shop contains various filters that are used to filter through products based on colors, price range, stock, etc. The filter components and the logic behind those can be edited within this folder.
We have various types of items in the boilerplate - product, curated product, document. On root categories, they are shown in a list view. This folder contains individual files to change the layout of these items.
With the boilerplate, you get multiple payment integrations such as Stripe and QuickPay (more to come!) in addition to the “Crystal” method, which is purely for testing purposes. You can remove the integrations you don’t require from this folder.
The header has a search component. This makes a call to the Search API in Crystallize and returns all the products that match the search term entered in the input field. To change anything about that input field, the file in this folder would be edited.
Let’s say you want to export a PDF invoice, or your catalogue, or information about the product itself as a PDF file. The boilerplate comes with this functionality right from the start. The styles for the PDF generated and the information displayed for each of these is defined within this folder. Examples: PDF for a product, PDF for a folder.
Any grid found in the demo application is made up of tiles in addition to items such as a product or a document. A tile could be one of the following - a banner, an embedded component, a slider, or a hero slider. To change the layout for any of the tiles, you can head over to this folder. Example - the entire frontpage is a grid made up of tiles.
Time to take a look at the API routes. Located within the routes folder, you will find API routes for cart, magic link, orders, payments, and webhooks. Let’s go through these one by one!
First, you will notice that there is `$langstore` and `api` folders. This is because the Boilerplate is multilingual, all the routes underneath `$langstore` can get access to the language and the store from the URL.
The files here take care of handling and placing the cart.
The boilerplate uses magic link to login and register users. This implies that a link is sent to the user via email and once the user clicks on it, the token is verified and then the user is logged in. This is the route that contains the logic to send the email and verify the token.
You can fetch orders by either the order ID or the customer identifier. The difference between the two is the former allows you to fetch a particular order, while the latter allows you to fetch every order placed by a customer. This route takes care of both scenarios.
The server-side logic for all the payment providers can also be found here.
Crystallize provides you with webhook functionality. This allows you to create and customize webhooks that fire off on events such as order creation, order update, item publish, and so much more. The boilerplate takes care of use cases for when a new order is created: an email is sent to the user confirming their order. The created.tsx file here is where you can change the layout of that email. Furthermore, we have a webhook to purge cache if you are using Fastly as your preferred service.
As this is an open source project, contributions are welcome. A guide on how to contribute is present in the readme for the repository.