The primary goal was to present users with products from stores located within a 15-mile radius of the user’s location.

We also ensured that the website displays boutiques and products even when the users do not share their location.

The Google Maps API lets share the location where they want the product to be delivered or their current location.

It allows the client application to identify the current user, and to potentially change their experience based on that information.

Additionally, an authenticated user can also be authorized to perform specific actions depending on their account's permissions.

We used simple_oauth module for authentication on Drupal end.

For more information around user authentication, read User Authentication for Gatsby and Drupal Decoupled site - https://bit.ly/3fOoF6u

We created each boutique as a new store. ShopTheArea admin can onboard boutique owners by creating a new user and a store for them. 

As this is a location-based service so it was very crucial for us to get the exact location (geo coordinates) of the boutique to provide better results. 

We implemented the Field geolocation module which provides integration with Google Maps API. 

The Boutique owner role comes with a set of permissions - managing products, access to a dashboard with different reports, etc.

The search functionality was added to the Catalog page, enabling users to narrow down to their desired search results.

We set up another Gatsby instance which only pulls the required data for the catalogue page. This instance works as a search index for us. We make GraphQL requests against this Gatsby instance to display the search results with respect to the user’s choices.

Whenever data changes on Drupal end both Gatsby instance data gets updated.

There may be scenarios where a user might lose the products added to the cart because they haven’t logged in, resulting in poor user experience.

To avoid this we created a custom REST endpoint which will be triggered when an anonymous user registers on the site. 

When a user registers on the site we assign the current cart with the newly registered user. In this way when a user logs in on the site and checks the cart page, the products will remain intact in the cart.

Whenever content is added, updated or deleted on the Drupal end it won’t automatically update on the Gatsby site. As Gatsby will process only data that is available at the build time.

To achieve this we used the build hook module. Which provides different options to choose for triggering the build hook.

We configured the build hook in such a way that whenever any content update happens it will trigger the Netlify build hook for our site so that our site content will be always up to date.

Build refers to the process of compiling your site. During a build, or at build time, your project gets transformed from component files to optimized HTML, CSS, and JavaScript files that you can deploy to your hosting provider.

While build happens for your site Gatsby fetches data from Drupal site. So we disabled all the JSON:API resources which aren’t required in the frontend so that unnecessary data shouldn’t be fetched and processed.

Also, we used gatsby-plugin-netlify-cache. This plugin caches your build files locally or in the Netlify cache directory. It will massively speed up subsequent builds. This plugin reduces the builds almost by 60-70% of build time.

We integrated Stripe - a payment gateway with easy to understand interface.

Multi-factor authentication - once payment is completed, Stripe sends the backend the status of the payment ie. success or failure. The system backend places the order only when Stripe sends a success message.

The primary goal was to present users with products from stores located within a 15-mile radius of the user’s location.

We also ensured that the website displays boutiques and products even when the users do not share their location.

The Google Maps API lets share the location where they want the product to be delivered or their current location.

It allows the client application to identify the current user, and to potentially change their experience based on that information.

Additionally, an authenticated user can also be authorized to perform specific actions depending on their account's permissions.

We used simple_oauth module for authentication on Drupal end.

For more information around user authentication, read User Authentication for Gatsby and Drupal Decoupled site - https://bit.ly/3fOoF6u

We created each boutique as a new store. ShopTheArea admin can onboard boutique owners by creating a new user and a store for them. 

As this is a location-based service so it was very crucial for us to get the exact location (geo coordinates) of the boutique to provide better results. 

We implemented the Field geolocation module which provides integration with Google Maps API. 

The Boutique owner role comes with a set of permissions - managing products, access to a dashboard with different reports, etc.

The search functionality was added to the Catalog page, enabling users to narrow down to their desired search results.

We set up another Gatsby instance which only pulls the required data for the catalogue page. This instance works as a search index for us. We make GraphQL requests against this Gatsby instance to display the search results with respect to the user’s choices.

Whenever data changes on Drupal end both Gatsby instance data gets updated.

There may be scenarios where a user might lose the products added to the cart because they haven’t logged in, resulting in poor user experience.

To avoid this we created a custom REST endpoint which will be triggered when an anonymous user registers on the site. 

When a user registers on the site we assign the current cart with the newly registered user. In this way when a user logs in on the site and checks the cart page, the products will remain intact in the cart.

Whenever content is added, updated or deleted on the Drupal end it won’t automatically update on the Gatsby site. As Gatsby will process only data that is available at the build time.

To achieve this we used the build hook module. Which provides different options to choose for triggering the build hook.

We configured the build hook in such a way that whenever any content update happens it will trigger the Netlify build hook for our site so that our site content will be always up to date.

Build refers to the process of compiling your site. During a build, or at build time, your project gets transformed from component files to optimized HTML, CSS, and JavaScript files that you can deploy to your hosting provider.

While build happens for your site Gatsby fetches data from Drupal site. So we disabled all the JSON:API resources which aren’t required in the frontend so that unnecessary data shouldn’t be fetched and processed.

Also, we used gatsby-plugin-netlify-cache. This plugin caches your build files locally or in the Netlify cache directory. It will massively speed up subsequent builds. This plugin reduces the builds almost by 60-70% of build time.

We integrated Stripe - a payment gateway with easy to understand interface.

Multi-factor authentication - once payment is completed, Stripe sends the backend the status of the payment ie. success or failure. The system backend places the order only when Stripe sends a success message.

The primary goal was to present users with products from stores located within a 15-mile radius of the user’s location.

We also ensured that the website displays boutiques and products even when the users do not share their location.

The Google Maps API lets share the location where they want the product to be delivered or their current location.

It allows the client application to identify the current user, and to potentially change their experience based on that information.

Additionally, an authenticated user can also be authorized to perform specific actions depending on their account's permissions.

We used simple_oauth module for authentication on Drupal end.

For more information around user authentication, read User Authentication for Gatsby and Drupal Decoupled site - https://bit.ly/3fOoF6u

We created each boutique as a new store. ShopTheArea admin can onboard boutique owners by creating a new user and a store for them. 

As this is a location-based service so it was very crucial for us to get the exact location (geo coordinates) of the boutique to provide better results. 

We implemented the Field geolocation module which provides integration with Google Maps API. 

The Boutique owner role comes with a set of permissions - managing products, access to a dashboard with different reports, etc.

The search functionality was added to the Catalog page, enabling users to narrow down to their desired search results.

We set up another Gatsby instance which only pulls the required data for the catalogue page. This instance works as a search index for us. We make GraphQL requests against this Gatsby instance to display the search results with respect to the user’s choices.

Whenever data changes on Drupal end both Gatsby instance data gets updated.

There may be scenarios where a user might lose the products added to the cart because they haven’t logged in, resulting in poor user experience.

To avoid this we created a custom REST endpoint which will be triggered when an anonymous user registers on the site. 

When a user registers on the site we assign the current cart with the newly registered user. In this way when a user logs in on the site and checks the cart page, the products will remain intact in the cart.

Whenever content is added, updated or deleted on the Drupal end it won’t automatically update on the Gatsby site. As Gatsby will process only data that is available at the build time.

To achieve this we used the build hook module. Which provides different options to choose for triggering the build hook.

We configured the build hook in such a way that whenever any content update happens it will trigger the Netlify build hook for our site so that our site content will be always up to date.

Build refers to the process of compiling your site. During a build, or at build time, your project gets transformed from component files to optimized HTML, CSS, and JavaScript files that you can deploy to your hosting provider.

While build happens for your site Gatsby fetches data from Drupal site. So we disabled all the JSON:API resources which aren’t required in the frontend so that unnecessary data shouldn’t be fetched and processed.

Also, we used gatsby-plugin-netlify-cache. This plugin caches your build files locally or in the Netlify cache directory. It will massively speed up subsequent builds. This plugin reduces the builds almost by 60-70% of build time.

We integrated Stripe - a payment gateway with easy to understand interface.

Multi-factor authentication - once payment is completed, Stripe sends the backend the status of the payment ie. success or failure. The system backend places the order only when Stripe sends a success message.

The primary goal was to present users with products from stores located within a 15-mile radius of the user’s location.

We also ensured that the website displays boutiques and products even when the users do not share their location.

The Google Maps API lets share the location where they want the product to be delivered or their current location.

It allows the client application to identify the current user, and to potentially change their experience based on that information.

Additionally, an authenticated user can also be authorized to perform specific actions depending on their account's permissions.

We used simple_oauth module for authentication on Drupal end.

For more information around user authentication, read User Authentication for Gatsby and Drupal Decoupled site - https://bit.ly/3fOoF6u

We created each boutique as a new store. ShopTheArea admin can onboard boutique owners by creating a new user and a store for them. 

As this is a location-based service so it was very crucial for us to get the exact location (geo coordinates) of the boutique to provide better results. 

We implemented the Field geolocation module which provides integration with Google Maps API. 

The Boutique owner role comes with a set of permissions - managing products, access to a dashboard with different reports, etc.

The search functionality was added to the Catalog page, enabling users to narrow down to their desired search results.

We set up another Gatsby instance which only pulls the required data for the catalogue page. This instance works as a search index for us. We make GraphQL requests against this Gatsby instance to display the search results with respect to the user’s choices.

Whenever data changes on Drupal end both Gatsby instance data gets updated.

There may be scenarios where a user might lose the products added to the cart because they haven’t logged in, resulting in poor user experience.

To avoid this we created a custom REST endpoint which will be triggered when an anonymous user registers on the site. 

When a user registers on the site we assign the current cart with the newly registered user. In this way when a user logs in on the site and checks the cart page, the products will remain intact in the cart.

Whenever content is added, updated or deleted on the Drupal end it won’t automatically update on the Gatsby site. As Gatsby will process only data that is available at the build time.

To achieve this we used the build hook module. Which provides different options to choose for triggering the build hook.

We configured the build hook in such a way that whenever any content update happens it will trigger the Netlify build hook for our site so that our site content will be always up to date.

Build refers to the process of compiling your site. During a build, or at build time, your project gets transformed from component files to optimized HTML, CSS, and JavaScript files that you can deploy to your hosting provider.

While build happens for your site Gatsby fetches data from Drupal site. So we disabled all the JSON:API resources which aren’t required in the frontend so that unnecessary data shouldn’t be fetched and processed.

Also, we used gatsby-plugin-netlify-cache. This plugin caches your build files locally or in the Netlify cache directory. It will massively speed up subsequent builds. This plugin reduces the builds almost by 60-70% of build time.

We integrated Stripe - a payment gateway with easy to understand interface.

Multi-factor authentication - once payment is completed, Stripe sends the backend the status of the payment ie. success or failure. The system backend places the order only when Stripe sends a success message.

The primary goal was to present users with products from stores located within a 15-mile radius of the user’s location.

We also ensured that the website displays boutiques and products even when the users do not share their location.

The Google Maps API lets share the location where they want the product to be delivered or their current location.

It allows the client application to identify the current user, and to potentially change their experience based on that information.

Additionally, an authenticated user can also be authorized to perform specific actions depending on their account's permissions.

We used simple_oauth module for authentication on Drupal end.

For more information around user authentication, read User Authentication for Gatsby and Drupal Decoupled site - https://bit.ly/3fOoF6u

We created each boutique as a new store. ShopTheArea admin can onboard boutique owners by creating a new user and a store for them. 

As this is a location-based service so it was very crucial for us to get the exact location (geo coordinates) of the boutique to provide better results. 

We implemented the Field geolocation module which provides integration with Google Maps API. 

The Boutique owner role comes with a set of permissions - managing products, access to a dashboard with different reports, etc.

The search functionality was added to the Catalog page, enabling users to narrow down to their desired search results.

We set up another Gatsby instance which only pulls the required data for the catalogue page. This instance works as a search index for us. We make GraphQL requests against this Gatsby instance to display the search results with respect to the user’s choices.

Whenever data changes on Drupal end both Gatsby instance data gets updated.

There may be scenarios where a user might lose the products added to the cart because they haven’t logged in, resulting in poor user experience.

To avoid this we created a custom REST endpoint which will be triggered when an anonymous user registers on the site. 

When a user registers on the site we assign the current cart with the newly registered user. In this way when a user logs in on the site and checks the cart page, the products will remain intact in the cart.

Whenever content is added, updated or deleted on the Drupal end it won’t automatically update on the Gatsby site. As Gatsby will process only data that is available at the build time.

To achieve this we used the build hook module. Which provides different options to choose for triggering the build hook.

We configured the build hook in such a way that whenever any content update happens it will trigger the Netlify build hook for our site so that our site content will be always up to date.

Build refers to the process of compiling your site. During a build, or at build time, your project gets transformed from component files to optimized HTML, CSS, and JavaScript files that you can deploy to your hosting provider.

While build happens for your site Gatsby fetches data from Drupal site. So we disabled all the JSON:API resources which aren’t required in the frontend so that unnecessary data shouldn’t be fetched and processed.

Also, we used gatsby-plugin-netlify-cache. This plugin caches your build files locally or in the Netlify cache directory. It will massively speed up subsequent builds. This plugin reduces the builds almost by 60-70% of build time.

We integrated Stripe - a payment gateway with easy to understand interface.

Multi-factor authentication - once payment is completed, Stripe sends the backend the status of the payment ie. success or failure. The system backend places the order only when Stripe sends a success message.

The primary goal was to present users with products from stores located within a 15-mile radius of the user’s location.

We also ensured that the website displays boutiques and products even when the users do not share their location.

The Google Maps API lets share the location where they want the product to be delivered or their current location.

It allows the client application to identify the current user, and to potentially change their experience based on that information.

Additionally, an authenticated user can also be authorized to perform specific actions depending on their account's permissions.

We used simple_oauth module for authentication on Drupal end.

For more information around user authentication, read User Authentication for Gatsby and Drupal Decoupled site - https://bit.ly/3fOoF6u

We created each boutique as a new store. ShopTheArea admin can onboard boutique owners by creating a new user and a store for them. 

As this is a location-based service so it was very crucial for us to get the exact location (geo coordinates) of the boutique to provide better results. 

We implemented the Field geolocation module which provides integration with Google Maps API. 

The Boutique owner role comes with a set of permissions - managing products, access to a dashboard with different reports, etc.

The search functionality was added to the Catalog page, enabling users to narrow down to their desired search results.

We set up another Gatsby instance which only pulls the required data for the catalogue page. This instance works as a search index for us. We make GraphQL requests against this Gatsby instance to display the search results with respect to the user’s choices.

Whenever data changes on Drupal end both Gatsby instance data gets updated.

There may be scenarios where a user might lose the products added to the cart because they haven’t logged in, resulting in poor user experience.

To avoid this we created a custom REST endpoint which will be triggered when an anonymous user registers on the site. 

When a user registers on the site we assign the current cart with the newly registered user. In this way when a user logs in on the site and checks the cart page, the products will remain intact in the cart.

Whenever content is added, updated or deleted on the Drupal end it won’t automatically update on the Gatsby site. As Gatsby will process only data that is available at the build time.

To achieve this we used the build hook module. Which provides different options to choose for triggering the build hook.

We configured the build hook in such a way that whenever any content update happens it will trigger the Netlify build hook for our site so that our site content will be always up to date.

Build refers to the process of compiling your site. During a build, or at build time, your project gets transformed from component files to optimized HTML, CSS, and JavaScript files that you can deploy to your hosting provider.

While build happens for your site Gatsby fetches data from Drupal site. So we disabled all the JSON:API resources which aren’t required in the frontend so that unnecessary data shouldn’t be fetched and processed.

Also, we used gatsby-plugin-netlify-cache. This plugin caches your build files locally or in the Netlify cache directory. It will massively speed up subsequent builds. This plugin reduces the builds almost by 60-70% of build time.

We integrated Stripe - a payment gateway with easy to understand interface.

Multi-factor authentication - once payment is completed, Stripe sends the backend the status of the payment ie. success or failure. The system backend places the order only when Stripe sends a success message.

The primary goal was to present users with products from stores located within a 15-mile radius of the user’s location.

We also ensured that the website displays boutiques and products even when the users do not share their location.

The Google Maps API lets share the location where they want the product to be delivered or their current location.

It allows the client application to identify the current user, and to potentially change their experience based on that information.

Additionally, an authenticated user can also be authorized to perform specific actions depending on their account's permissions.

We used simple_oauth module for authentication on Drupal end.

For more information around user authentication, read User Authentication for Gatsby and Drupal Decoupled site - https://bit.ly/3fOoF6u

We created each boutique as a new store. ShopTheArea admin can onboard boutique owners by creating a new user and a store for them. 

As this is a location-based service so it was very crucial for us to get the exact location (geo coordinates) of the boutique to provide better results. 

We implemented the Field geolocation module which provides integration with Google Maps API. 

The Boutique owner role comes with a set of permissions - managing products, access to a dashboard with different reports, etc.

The search functionality was added to the Catalog page, enabling users to narrow down to their desired search results.

We set up another Gatsby instance which only pulls the required data for the catalogue page. This instance works as a search index for us. We make GraphQL requests against this Gatsby instance to display the search results with respect to the user’s choices.

Whenever data changes on Drupal end both Gatsby instance data gets updated.

There may be scenarios where a user might lose the products added to the cart because they haven’t logged in, resulting in poor user experience.

To avoid this we created a custom REST endpoint which will be triggered when an anonymous user registers on the site. 

When a user registers on the site we assign the current cart with the newly registered user. In this way when a user logs in on the site and checks the cart page, the products will remain intact in the cart.

Whenever content is added, updated or deleted on the Drupal end it won’t automatically update on the Gatsby site. As Gatsby will process only data that is available at the build time.

To achieve this we used the build hook module. Which provides different options to choose for triggering the build hook.

We configured the build hook in such a way that whenever any content update happens it will trigger the Netlify build hook for our site so that our site content will be always up to date.

Build refers to the process of compiling your site. During a build, or at build time, your project gets transformed from component files to optimized HTML, CSS, and JavaScript files that you can deploy to your hosting provider.

While build happens for your site Gatsby fetches data from Drupal site. So we disabled all the JSON:API resources which aren’t required in the frontend so that unnecessary data shouldn’t be fetched and processed.

Also, we used gatsby-plugin-netlify-cache. This plugin caches your build files locally or in the Netlify cache directory. It will massively speed up subsequent builds. This plugin reduces the builds almost by 60-70% of build time.

We integrated Stripe - a payment gateway with easy to understand interface.

Multi-factor authentication - once payment is completed, Stripe sends the backend the status of the payment ie. success or failure. The system backend places the order only when Stripe sends a success message.

The primary goal was to present users with products from stores located within a 15-mile radius of the user’s location.

We also ensured that the website displays boutiques and products even when the users do not share their location.

The Google Maps API lets share the location where they want the product to be delivered or their current location.

It allows the client application to identify the current user, and to potentially change their experience based on that information.

Additionally, an authenticated user can also be authorized to perform specific actions depending on their account's permissions.

We used simple_oauth module for authentication on Drupal end.

For more information around user authentication, read User Authentication for Gatsby and Drupal Decoupled site - https://bit.ly/3fOoF6u

We created each boutique as a new store. ShopTheArea admin can onboard boutique owners by creating a new user and a store for them. 

As this is a location-based service so it was very crucial for us to get the exact location (geo coordinates) of the boutique to provide better results. 

We implemented the Field geolocation module which provides integration with Google Maps API. 

The Boutique owner role comes with a set of permissions - managing products, access to a dashboard with different reports, etc.

The search functionality was added to the Catalog page, enabling users to narrow down to their desired search results.

We set up another Gatsby instance which only pulls the required data for the catalogue page. This instance works as a search index for us. We make GraphQL requests against this Gatsby instance to display the search results with respect to the user’s choices.

Whenever data changes on Drupal end both Gatsby instance data gets updated.

There may be scenarios where a user might lose the products added to the cart because they haven’t logged in, resulting in poor user experience.

To avoid this we created a custom REST endpoint which will be triggered when an anonymous user registers on the site. 

When a user registers on the site we assign the current cart with the newly registered user. In this way when a user logs in on the site and checks the cart page, the products will remain intact in the cart.

Whenever content is added, updated or deleted on the Drupal end it won’t automatically update on the Gatsby site. As Gatsby will process only data that is available at the build time.

To achieve this we used the build hook module. Which provides different options to choose for triggering the build hook.

We configured the build hook in such a way that whenever any content update happens it will trigger the Netlify build hook for our site so that our site content will be always up to date.

Build refers to the process of compiling your site. During a build, or at build time, your project gets transformed from component files to optimized HTML, CSS, and JavaScript files that you can deploy to your hosting provider.

While build happens for your site Gatsby fetches data from Drupal site. So we disabled all the JSON:API resources which aren’t required in the frontend so that unnecessary data shouldn’t be fetched and processed.

Also, we used gatsby-plugin-netlify-cache. This plugin caches your build files locally or in the Netlify cache directory. It will massively speed up subsequent builds. This plugin reduces the builds almost by 60-70% of build time.

We integrated Stripe - a payment gateway with easy to understand interface.

Multi-factor authentication - once payment is completed, Stripe sends the backend the status of the payment ie. success or failure. The system backend places the order only when Stripe sends a success message.