Mamix – NextJs Typescript Page-Router React-Bootstrap Admin & Dashboard Template
Mamix - NextJS Typescript Page-Router React-Bootstrap Admin Template, With these template formats, it's very easy to create a presence and grab someone's attention around the web page Because the template is built using Nextjs, Typescript, CSS3, React-Bootstrap framework and with Sass. So please before you start working with the template take a quick look on the documentation so that you can easily built your website.
If You Love Our Template Design Please don't forgot to rate it. Thank you so much! 😊
Dashboard
Welcome to Mamix - NextJS Typescript Page-Router React-Bootstrap Admin & Dashboard Template- Created Date : 21/March/2025
- Author : Spruko
- Company : Spruko Technologies Private Limited
Thank you for showing interest towards our admin template. Feel free to contact us any time. We have a dedicated team to provide you the best support. If you want any queries open support ticket https://support.spruko.com.
Mamix is a NextJS Typescript Page-Router React-Bootstrap Admin Template using modern and minimal design. It is fully flexible user-friendly and responsive. Mamix Modern template is powered with Nextjs,Typescript, SASS, & React-Bootstrap which looks great on Desktops, Tablets, and Mobile Devices. This Template Includes 230+ NextJs Components. . No Need to do hard work for this template customization. We already designed it and you can easily design your website just how you like it. This template using React-Bootstrap framework. After Purchased this template you will get All Nextjs CSS, Scss and TS Files.
It has super clean flat user interface admin design, easy customizable components and widgets.The Template comes with a awesome unique design also we ensure you can easily design template.
It is a fully responsive layout for all type of devices. Works on all major web browsers, Desktop, iPhone, iPad, Tablet and all other smart phone devices
Once you Purchase Mamix NextJS Typescript Page-Router React-Bootstrap Admin Template, you will be able to get free download of all future updates.
- Firefox
- Safari
- Opera
- Chrome
- Edge
Theme Styles
- Light & Dark Themes
- LTR & RTL
- Vertical & Horizontal Navigation Styles
- Menu Click & Hover Styles
- Icon Click & Hover Styles
- Page Regular & Classic Styles
- Layout Default, Full Width & Boxed
- Menu Fixed & Scrollable
- Header Fixed & Scrollable
- Sidemenu Closed
- Icon Text Menu
- Icon Overlay
- Detached
- Double Menu
Theme Colors
- Menu Light
- Menu Dark
- Menu Color
- Menu Gradient
- Menu Transparent
- Header Light
- Header Dark
- Header Color
- Header Gradient
- Header Transparent
- Theme Primary
- Theme Background
- Menu With Background Images
| Easy to Customize | Dark Layout | RTL Ready |
| Icons | Authentication Pages | Error Pages |
| 230+ NextJs Pages | React-Bootstrap Framework | Tour |
| Form Elements | Maps | Ratings |
| Form Advanced | Form wizards | Profile Settings |
| Grid JS Tables | Data Tables | Gallery |
| Apex Charts | Chartjs Charts | Echarts |
| Full Calendar | Sweet Alerts | Swiper JS |
| Blog Pages | Mail App | Chat |
| File Manager | Invoice | Landing Pages |
| Pricing | Profile | Placeholders |
| Classifieds Pages | Domain Pages | Market place Pages |
| Real Estate Pages | Ecommerce Pages | Job Pages |
| NFT Pages | CRM Pages | Crypto Pages |
| 24 * 7 Professional Company Support | Media Player | Under Construction Page |
| Color Theme Support (Primary and Background) | Neat, clean and simple design | W3C Validated |
Getting Started
Setting Up The Local Environment & Workspace
This comprehensive guide provides step-by-step instructions on how to set up your development environment Nextjs tool. It covers everything from the necessary prerequisites to installing the tool, creating an initial workspace, and setting up a starter app. You'll also learn how to run the app locally to test and verify your setup. By following this guide, you can ensure that your development environment is properly configured for Nextjs, and you can get started with your project confidently and efficiently. Whether you're a beginner or an experienced developer, this guide is an essential resource for anyone looking to work with Nextjs.
To get started with a Nextjs application, there are three prerequisites that you need to have in place.
Prerequisites
To use the NextJs Typescript Framework, you should be familiar with the following:- NextJs
- React Bootstrap
- Typescript
Creating a Component
The easiest way to create a component is with the React CLI. You can also create a component manually.
Creating a component using the React CLI
To create a component using the React CLI:
- From a terminal window, navigate to the directory containing your application
- Run the
generate-react-cli component <component-name>command, where<component-name>is the name of your new component.
generate-react-cli component <component-name>
By default, this command creates the following: - A folder named after the component
- A component file,
<component-name>.component - A template file,
<component-name>.component.tsx - A CSS file,
<component-name>.component.css - A testing specification file,
<component-name>.component.spec.ts
<component-name> is the name of your component.
NextJS Setup
Create a workspace and initial application
You develop apps in the context of an NextJS workspace.
To create a new workspace and initial starter app just follow the below steps
- Run the command , as shown below
- This new command prompts for the information about features to include in the initial app. Accept the defaults by pressing the Enter or Return key.
npx create-next-app my-app
If you want to create an single-page project in NextJs, you need to install the necessary NextJs as below
The NextJS installs the necessary NextJs npm packages and other dependencies. This can take a few minutes. This creates a new workspaces and a simple Welcome app, ready to run.
Run the application
The NextJS includes a server, so that you can build and serve your app locally.
- Navigate to the workspace folder, such as my-app.
- Run the following commands:
cd my-app
npm run dev
The yarn or npm serve command launches the server, watches your files, and rebuilds the
app as you make changes to those files.
The run dev just Option automatically opens your default
browser to http://localhost:3000/.
Mamix Next.js Setup
Note: you have already download and install node.js and Next.js then ignore prerequisites.
Prerequisites
Node.js
Download latest version of node.js from nodejs.org.
Install Node.js using downloaded file. To check your node version, run node -v in a terminal/console window (cmd)
Next.js
To install the Next.js using npm, open a terminal/console window and run the following command.
npm install
(or)
yarn install
Final installation of Mamix Next.js
Setup an Mamix Template by Download the Mamix-ts rar/zip file. then Extract it and then go in to Folder here you will see a MamixJS Folder
You can import all dependency by installing npm command
npm install
(or)
yarn install
Now you are in stage to successfully run mamix-ts using below command:
npm run dev
(or)
yarn run dev
Once you serve your application by default it will take their default port using http://localhost:3000/
Note:
If your are using "npm install", You should need to delete the "yarn-lock file" from project root.
If your are using "yarn install", You should need to delete the "package-lock.json file" from project root.
To install the peer Depencies
In general, the npm i command is used to install all dependencies or devDependencies from a package. However, sometimes you may encounter errors while installing certain dependencies. In such cases, the --force argument can be used to force npm to install those dependencies.
The --force argument overrides any previously installed dependencies and fetches remote resources even if a local copy exists on disk. It follows a "last-dependency-downloaded-wins" approach, which means that it will overwrite any previously downloaded dependencies.
Using the --force argument can be helpful when you need to install a specific dependency that is causing issues during installation. However, it should be used with caution, as it can potentially cause conflicts with other dependencies or lead to unexpected behavior. It's always a good idea to thoroughly test your application after using the --force argument to ensure that everything is working as expected.
npm install --force
When installing packages using npm, if there are peer dependency issues, npm will always skip the installation of peer dependencies, even if there are no issues. Peer dependencies are a specific type of dependency that a package requires to function properly, but which are not managed by that package's dependency manager.
Skipping the installation of peer dependencies can sometimes lead to issues with the functionality or compatibility of the package. To ensure that your package functions correctly, it's important to manually install any missing peer dependencies using the npm install command. When installing peer dependencies, you should also be aware of the potential for conflicts with other packages or dependencies. It's a good idea to carefully review the peer dependencies required by each package and ensure that they are compatible with other packages in your project. By taking these steps, you can avoid potential issues and ensure that your packages are installed and functioning correctly.
npm install--legacy-peer-deps
We have to use only one file example: (for yarn yarn-lock) & (for npm package-lock.json) file
For Build your Template
Build your application for host on server using below command:
yarn run build
(or)
npm run build
Note:
To deploy your project successfully, ensure that your domain is correctly added to the basePath in next.config.ts path:mamix-ts\next.config.ts
Installation Video
├── pages/
| |-- (api)/
| |-- |-- hello.ts/
| |-- (components)/
| |-- |-- advancedui/
| |-- | |-- accordions-collapse.tsx/
| |-- |-- apps/
| |-- |-- authentication/
| |-- |-- charts/
| |-- _app.tsx/
| |-- _document.tsx
| |-- index.tsx
├── public/
| |-- assets/
| |-- favicon.ico
| | file.svg
| | globe.svg
| | next.svg
| | vercel.svg
| | window.svg
├── shared/
| |-- @spk-reusable-components/
| |-- data/
| |-- firebase/
| |-- layout-components/
| |-- redux/
| |-- contextapi.tsx
| └── layoutcontext.tsx
├── styles
| └── globals.scss
├── eslintrc.json
├── .gitignore
├── next-env.d.ts
├── next.config.ts
├── package-lock.json
├── package.json
├── plugin.d.ts
├── README.md
└── tsconfig.json
-
Mamix - NextJs Typescript Page-Router Admin Dashboard Template /: Root template folder contain all tsx, scss, images and other files. -
-
pages/: This is the main directory for the application's routing. -
-
api/: Contains API routes (e.g., hello.ts) for handling backend requests -
components/: A grouping folder for four layouts.advancedui/: Contains UI components like accordions-collapse.tsx.apps/: Likely contains components for app-related features.authentication/:Components related to user authentication (e.g., login, registration).charts/: Components for visualizing data via charts.
-
_app.tsx:Custom App component in Next.js, wrapping all pages and handling global layout or state. -
_document.tsx: A custom Document component in Next.js used for augmenting the HTML document structure (e.g., adding custom metadata or global scripts). -
index.tsx:Entry point for the homepage of the app.
-
public/-
assets/:Stores static assets like images, accessible via /public/assets -
shared/:Reusable components and Data files that can be used across multiple pages. eslintrtc.json: ESLint configuration file.gitignore: Specifies intentionally untracked files to ignore.next-env.d.ts: Next.js environment declaration file.next-config.ts: Next.js configuration file.package.json: Contains metadata about the project and its dependencies.plugin.d.ts: Declaration file to handle package redeclaration errors.README.md: Project documentation and instructions.tsconfig.json: TypeScript configuration file.
-
Purpose of a starter kit
Introduction to the NextJS Typescript Starter Kit Template:
The NextJS template starterkit is a resource that helps developers kickstart their NextJS web development projects by providing a preconfigured and ready-to-use template. It aims to simplify the initial setup and provide a foundation for building NextJS-based websites or applications.
Purpose of the NextJS Starter Kit Template:
The purpose of the NextJS Starter Kit Template is to save developers time and effort by offering a set of prebuilt files and configurations commonly used in NextJS projects. Instead of starting from scratch, developers can leverage the starter kit to quickly set up a project structure that adheres to best practices and industry standards.
Benefits of Using the NextJS Starter Kit Template:
The starter kit eliminates the need to set up the basic project structure manually. It provides a well-organized file and folder structure, including commonly used directories for separating code, templates, assets, and configuration files. This allows developers to focus more on implementing business logic rather than spending time on initial setup.
Before using the NextJS Starter Kit Template, developers should have a basic understanding of NextJS and web development concepts.
Starterkit Overview
You can use the Starterkit if you are creating a new project. It will be time-consuming to use the full admin version for a new project as Mamix-nextJs Typescript have more than 150 components.
We have provided all the pre-build layouts like Sidemenu, Header, footer and blank pages etc in the Starterkit.
For further information or support regarding the template, please contact us using the provided link.
https://support.spruko.com/Starterkit Folder Structure
starterkit/
├── pages/
| |-- (api)/
| |-- |-- hello.ts/
| |-- (components)/
| |-- |-- dashboards/
| |-- | |-- sales.tsx/
| |-- _app.tsx/
| |-- _document.tsx
| |-- index.tsx
├── public/
| |-- assets/
| |-- favicon.ico
| | file.svg
| | globe.svg
| | next.svg
| | vercel.svg
| | window.svg
├── shared/
| |-- data/
| |-- firebase/
| |-- layout-components/
| |-- redux/
| └── layoutcontext.tsx
├── styles
| └── globals.scss
├── eslintrc.json
├── .gitignore
├── next-env.d.ts
├── next.config.ts
├── package-lock.json
├── package.json
├── plugin.d.ts
├── README.md
└── tsconfig.json
- Take a quick look at the folder structure of the "Starterkit."
- Integration of your customized NextJS pages becomes easy when using the "Starterkit."
- The "Starterkit" provides all the layout components, related assets, and plugins.
- To explore the contents of the "Starterkit," unzip the project folder received after purchase.
├── pages/
| ├── components/
| | ├──advanceui/
| | ├──apps/
| | ├──authentication/
| | ├──charts/
| | ├──dashboards/
| | ├──error/
| | ├──forms/
| | ├──maps/
| | ├──nestedmenu/
| | ├──pages/
| | ├──tables/
| | ├──uielements/
| | ├──utilities/
| | ├──icon.tsx/
| | └──widgets.tsx
├── public/
| ├── assets/
| | | ├──audio/
| | | ├──css/
| | | | ├──icons.css/
| | | | ├──icons.css.map/
| | | | ├──styles.css/
| | | | └──styles.css.map/
| | | ├── icon-fonts/
| | | | ├──bootstrap-icons/
| | | | ├──boxicons/
| | | | ├──feather/
| | | | ├──line-awesome/
| | | | ├──remixicons/
| | | | └──tabler-icons/
| | | ├──images/
| | | ├──scss/
| | | | ├──bootstrap/
| | | | ├──custom/
| | | | ├──global/
| | | | ├──menu-styles/
| | | | ├──pages/
| | | | ├──util/
| | | | ├──_bootstrap.scss
| | | | ├──_switcher.scss
| | | | ├──_variables.scss
| | | | ├──icons.scss
| | | | └──styles.scss
| └── └── └── video/
Basic Layout Structure
Root:\pages\_app.tsx
Routing
In a single-page application, you change what the user sees by showing or hiding portions of the display that correspond to particular components, rather than going out to the server to get a new page. As users perform application tasks, they need to move between the different views that you have defined
Suppose you want to create a new module ( For creating a new module refer create new module ) then you have to add new routes for that modules.
Basic Route
Following are the fundamental building blocks to creating a route.
import React, { Fragment } from "react";
import Link from 'next/link';
import { useRouter } from "next/router";
<ul>
<li>
<Link href="/components/dashboards/sales">Sles
</Link>
</li>
<li>
<Link href="/components/dashboards/analytics">Analytics
</Link>
</li>
<li>
<Link href="/blog/hello-world">Blog Post
</Link>
</li>
</ul>
Configure Link in Menu
To Add new link in Sidemenu
Following are the fundamental building blocks to creating a new link.
├── shared
├──layout-components
├──sidebar
nav.tsx
export const MenuItems: any = [
{
menutitle: "MAIN",
},
{
icon: DashboardIcon,
badgetxt: ,
title: "Dashboards",
type: "sub",
active: false,
children: [
{
path: "/components/dashboards/sales",
type: "link",
active: false,
selected: false,
dirchange: false,
title: "Sales",
},
{
path: "/components/dashboards/analytics",
type: "link",
active: false,
selected: false,
dirchange: false,
title: "Analytics",
},
{
path: "/components/dashboards/ecommere",
type: "link",
active: false,
selected: false,
dirchange: false,
title: "Ecommerce",
},
]
}
]
Introduction :
This documentation outlines the process of converting SCSS (Sassy CSS) files to standard CSS (Cascading Style Sheets) in a project's assets directory using the SASS package. SCSS is a preprocessor for CSS, and SASS is a popular choice for transforming SCSS into CSS efficiently. This guide provides step-by-step instructions on installing the SASS package, configuring it in your project, and converting SCSS files to CSS.
-
Prerequisites
Before proceeding, ensure that you have the following prerequisites:
Node.js installed on your system.
A project directory with SCSS files that you want to compile into CSS.
Installation :
Install the SASS package using npm (Node Package Manager) by running the following command:
npm install sass
This command will download and install the SASS package and its dependencies into your project.
Configuration :
To configure SASS for your project, follow these steps:
-
1. Open your project's
package.jsonfile. If you don't have one, you can create it by running npm init and following the prompts. -
2. Inside the
package.jsonfile, locate the "scripts" section. If it doesn't exist, create one:"scripts": { // ...existing scripts... } -
3. Add a script that specifies the compilation process from SCSS to CSS. You can name the script as you prefer, but for this example, we'll name it "sass." The script should look like this:
"scripts": { "sass": "sass ./public/assets/scss:./public/assets/css/" }In the script above, replace
./public/assets/scsswith the path to your SCSS files and./public/assets/csswith the destination directory for your compiled CSS files. -
4. Add a script that specifies the compilation compressed process from SCSS to CSS. You can name the script as you prefer, but for this example, we'll name it "sass-min." The script should look like this:
"scripts": { "sass-min": "sass ./public/assets/scss:./public/assets/css/ --style compressed" }In the script above, replace
./public/assets/scsswith the path to your SCSS files and./public/assets/csswith the destination directory for your compiled CSS files. -
5. Save the
package.jsonfile.
Compiling SCSS to CSS :
With the SASS package and script configured, you can now compile your SCSS files to CSS with the following steps:
-
1. Open your terminal or command prompt.
-
2. Navigate to your project's root directory if you're not already there.
-
3. Execute the following command to run the "sass" script:
npm run sassThis command will initiate the SCSS to CSS compilation process using the SASS package.
-
4. Execute the following command to run the "sass-min" script:
npm run sass-minThis command will initiate the SCSS to CSS compilation compressed process using the SASS package.
-
5. Once the process is complete, the compiled CSS files will be generated in the specified destination directory (e.g., ./public/assets/css).
Conclusion :
You have successfully configured and used the SASS package to convert SCSS files to CSS in your project. This allows you to take advantage of SCSS's powerful features while ensuring that your web application uses standard CSS for styling.
Firebase SetUp
Step-1: Now run below commands inside our nextjs project to install firebase latest.
step-2: Add firebase API configuration details(create database on firebase) to the firebase Auth Component refer the path (/shared/firebase/firebaseapi.tsx)
Firebase Revocation process
To remove firebase from the project make sure that you have to remove the firebase tab from the (app\page.tsx). change the key variable to 'next.js' Example : const [key, setKey] = useState('next.js') in the the (app\page.tsx).Firebase installation process
(Root:\shared\layout-components\layout\Rootwrapper.tsx)
<html lang="en" dir="ltr" data-nav-layout="vertical" data-theme-mode="light" data-header-styles="light" data-menu-styles="light" data-toggled="close"></html>
| Attribute | Description |
|---|---|
data-theme-mode="light"
data-header-styles="light"
data-menu-styles="light"
|
To set the light theme |
data-theme-mode="dark"
data-header-styles="dark"
data-menu-styles="dark"
|
To set the Dark theme |
dir="ltr"
|
To set LTR version default |
dir="rtl"
|
To set LTR version to RTL version |
data-nav-layout="vertical"
|
To set menu layout to vertical |
data-nav-layout="horizontal"
data-nav-style="menu-click"
|
To set menu layout to horizontal |
data-nav-style="menu-click"
|
To set navigation style to menu click - *Works same for both vertical and horizontal |
data-nav-style="menu-hover"
|
To set navigation style to menu hover - *Works same for both vertical and horizontal |
data-nav-style="icon-click"
|
To set navigation style to icon click - *Works same for both vertical and horizontal |
data-nav-style="icon-hover"
|
To set navigation style to icon hover - *Works same for both vertical and horizontal |
data-page-style="regular"
|
To set page style to Default |
data-page-style="classic"
|
To set page style to Classic |
data-width="default"
|
To set page width to Default Width |
data-width="fullwidth"
|
To set page width to Full Width |
data-width="boxed"
|
To set page width to Boxed |
data-menu-position="fixed"
|
To set menu position Fixed |
data-menu-position="scrollable"
|
To set menu position Scrollable |
data-header-position="fixed"
|
To set header position Fixed |
data-header-position="scrollable"
|
To set header position Scrollable |
data-vertical-style="closed"
|
To set sidemenu layout style Closed - *Does not work for horizontal |
data-vertical-style="icontext"
|
To set sidemenu layout style Icon Text - *Does not work for horizontal |
data-vertical-style="overlay"
|
To set sidemenu layout style Icon Overlay - *Does not work for horizontal |
data-vertical-style="detached"
|
To set sidemenu layout style Detached - *Does not work for horizontal |
data-vertical-style="doublemenu"
|
To set sidemenu layout style Double Menu - *Does not work for horizontal |
loader="enable"
|
To enable loader by default |
General Style
Step 1:
Go To style.scss (\public\assets\scss\styles.scss )
if you want to change another font-family Go to the site Google Fonts And Select One font Family and import in to styles.scss file
How to Select font Family
Example:

Step 2:
And paste Your Selected font-family in style.scss
Example:

Step 3:
And add the Your Selected font-family in _variables.scss(\public\assets\scss\_variables.scss)
Example:
--default-font-family: "Montserrat", sans-serif;
By default menu icons are in the from remix icon if you want to change the icons please follow below steps
Step 1 :
To change Menu icons, open nav.tsx page
Path: shared\layout-components\sidebar\nav.tsx and go through app-sidebar section, in that section you will find
icontag, there you can replace previous icon with your icon. Example as shown in below
Go To "src/assets/images/brand-logos" folder and replace your logo with Previous Logos within in image size. note: Please don't increase logo sizes. Replace your logo within given image size. otherwise the logo will not fit in particular place it disturbs the template design.
To change Layout Theme
open reducer.tsx path:(shared\redux\reducer.tsx).
Theme Array Documentation
The theme array provided below is designed to control the layout and styling of a web application. By modifying the values in this array, you can change the visual appearance and behavior of various components in the application. The array includes settings related to color schemes, layout styles, header and menu styles, and more.
Initial State
The initial state of the theme array defines the default values for different aspects of the application's appearance and behavior. These values are used as a starting point and can be dynamically modified using the provided functions.
let initialState = {
lang: "en", // Default language
dir: "ltr", // Default text direction (ltr or rtl)
dataThemeMode: "light", // Default color scheme (light or dark)
dataMenuStyles: "light", // Default menu style (dark, light, color, gradient, transparent)
dataNavLayout: "vertical", // Default navigation layout (vertical or horizontal)
dataHeaderStyles: "transparent", // Default header style (light, dark, color, gradient, transparent)
dataVerticalStyle: "overlay", // Default vertical menu style (overlay, icon-text, detached, doublemenu)
toggled: "", // Default menu toggle state (open or closed)
dataNavStyle: "", // Default navigation style (menu-click, menu-hover, icon-click, icon-hover)
dataPageStyle: "regular", // Default page style (regular or classic)
dataWidth: "default", // Default page width (fullwidth or boxed)
dataMenuPosition: "fixed", // Default menu position (fixed or scrollable)
dataHeaderPosition: "fixed",// Default header position (fixed or scrollable)
loader:"disable", / Default loader (enable or disable)
iconOverlay: "", // Default icon overlay state (empty)
colorPrimaryRgb: "", // Default primary color (RGB format)
colorPrimary: "", // Default primary color (space-separated RGB values)
bodyBg1: "", // Default body background color1 (empty)
bodyBg2: "", // Default body background color2 (empty)
Light: "", // Default body background color (empty)
Formcontrol: "", // Default body background color (empty)
inputBorder: "", // Default dark inputBorder color (empty)
Graycolor: "", // Default dark background color (empty)
bgImg: "", // Default background image (empty)
iconText: "", // Default icon text style (empty)
body: "" // Default body class (empty)
};
Note:
Make sure to clear the localStorage when changing the state to prevent it from affecting the applied state.
Disabling Switcher
Step1:
Open header.tsx component shared\layout-components\header\header.tsx
To remove switcher section as shown below.
<Link scroll={false} href="#!" className="header-link switcher-icon" data-bs-toggle="offcanvas" data-bs-target="#switcher-canvas" onClick={toggleSwitcher}>
<svg xmlns="http://www.w3.org/2000/svg" className="header-link-icon" width="32" height="32" fill="#000000" viewBox="0 0 256 256">
<path d="M230.1,108.76,198.25,90.62c-.64-1.16-1.31-2.29-2-3.41l-.12-36A104.61,104.61,0,0,0,162,32L130,49.89c-1.34,0-2.69,0-4,0L94,32A104.58,104.58,0,0,0,59.89,51.25l-.16,36c-.7,1.12-1.37,2.26-2,3.41l-31.84,18.1a99.15,99.15,0,0,0,0,38.46l31.85,18.14c.64,1.16,1.31,2.29,2,3.41l.12,36A104.61,104.61,0,0,0,94,224l32-17.87c1.34,0,2.69,0,4,0L162,224a104.58,104.58,0,0,0,34.08-19.25l.16-36c.7-1.12,1.37-2.26,2-3.41l31.84-18.1A99.15,99.15,0,0,0,230.1,108.76ZM128,168a40,40,0,1,1,40-40A40,40,0,0,1,128,168Z" opacity="0.1">
</path>
<path d="M128,80a48,48,0,1,0,48,48A48.05,48.05,0,0,0,128,80Zm0,80a32,32,0,1,1,32-32A32,32,0,0,1,128,160Zm109.94-52.79a8,8,0,0,0-3.89-5.4l-29.83-17-.12-33.62a8,8,0,0,0-2.83-6.08,111.91,111.91,0,0,0-36.72-20.67,8,8,0,0,0-6.46.59L128,41.85,97.88,25a8,8,0,0,0-6.47-.6A111.92,111.92,0,0,0,54.73,45.15a8,8,0,0,0-2.83,6.07l-.15,33.65-29.83,17a8,8,0,0,0-3.89,5.4,106.47,106.47,0,0,0,0,41.56,8,8,0,0,0,3.89,5.4l29.83,17,.12,33.63a8,8,0,0,0,2.83,6.08,111.91,111.91,0,0,0,36.72,20.67,8,8,0,0,0,6.46-.59L128,214.15,158.12,231a7.91,7.91,0,0,0,3.9,1,8.09,8.09,0,0,0,2.57-.42,112.1,112.1,0,0,0,36.68-20.73,8,8,0,0,0,2.83-6.07l.15-33.65,29.83-17a8,8,0,0,0,3.89-5.4A106.47,106.47,0,0,0,237.94,107.21Zm-15,34.91-28.57,16.25a8,8,0,0,0-3,3c-.58,1-1.19,2.06-1.81,3.06a7.94,7.94,0,0,0-1.22,4.21l-.15,32.25a95.89,95.89,0,0,1-25.37,14.3L134,199.13a8,8,0,0,0-3.91-1h-.19c-1.21,0-2.43,0-3.64,0a8.1,8.1,0,0,0-4.1,1l-28.84,16.1A96,96,0,0,1,67.88,201l-.11-32.2a8,8,0,0,0-1.22-4.22c-.62-1-1.23-2-1.8-3.06a8.09,8.09,0,0,0-3-3.06l-28.6-16.29a90.49,90.49,0,0,1,0-28.26L61.67,97.63a8,8,0,0,0,3-3c.58-1,1.19-2.06,1.81-3.06a7.94,7.94,0,0,0,1.22-4.21l.15-32.25a95.89,95.89,0,0,1,25.37-14.3L122,56.87a8,8,0,0,0,4.1,1c1.21,0,2.43,0,3.64,0a8,8,0,0,0,4.1-1l28.84-16.1A96,96,0,0,1,188.12,55l.11,32.2a8,8,0,0,0,1.22,4.22c.62,1,1.23,2,1.8,3.06a8.09,8.09,0,0,0,3,3.06l28.6,16.29A90.49,90.49,0,0,1,222.9,142.12Z">
</path>
</svg>
</Link>
Step2:
Remove the switcher component from the main layout follow the path Path: \shared\layout-components\layout\contentlayout.tsx
import Switcher from "@/shared/layout-components/switcher/switcher"
<Switcher isSwitcherOpen={isSwitcherOpen} toggleSwitcher={toggleSwitcher} />
Step3:
Now remove the switcher component and switcherData file from the root folder, follow the path Switcher component shared\layout-components\switcher\switcher.tsx and
switcherdata file from /shared\data\switcherdata
Step1:
Open ecommerceheader.tsx component \shared\layout-components\ecommerceheader\ecommerceheader.tsx
To remove switcher section as shown below.
<Link scroll={false} onClick={toggleSwitcher} href="#!" className="categories-icon switcher-icon" data-bs-toggle="offcanvas" data-bs-target="#switcher-canvas">
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 256 256"><rect width="256" height="256" fill="none"/><path d="M207.86,123.18l16.78-21a99.14,99.14,0,0,0-10.07-24.29l-26.7-3a81,81,0,0,0-6.81-6.81l-3-26.71a99.43,99.43,0,0,0-24.3-10l-21,16.77a81.59,81.59,0,0,0-9.64,0l-21-16.78A99.14,99.14,0,0,0,77.91,41.43l-3,26.7a81,81,0,0,0-6.81,6.81l-26.71,3a99.43,99.43,0,0,0-10,24.3l16.77,21a81.59,81.59,0,0,0,0,9.64l-16.78,21a99.14,99.14,0,0,0,10.07,24.29l26.7,3a81,81,0,0,0,6.81,6.81l3,26.71a99.43,99.43,0,0,0,24.3,10l21-16.77a81.59,81.59,0,0,0,9.64,0l21,16.78a99.14,99.14,0,0,0,24.29-10.07l3-26.7a81,81,0,0,0,6.81-6.81l26.71-3a99.43,99.43,0,0,0,10-24.3l-16.77-21A81.59,81.59,0,0,0,207.86,123.18ZM128,168a40,40,0,1,1,40-40A40,40,0,0,1,128,168Z" opacity="0.2"/><circle cx="128" cy="128" r="40" fill="none" stroke="currentColor" strokeLinecap="round" strokeLinejoin="round" strokeWidth="16"/><path d="M41.43,178.09A99.14,99.14,0,0,1,31.36,153.8l16.78-21a81.59,81.59,0,0,1,0-9.64l-16.77-21a99.43,99.43,0,0,1,10.05-24.3l26.71-3a81,81,0,0,1,6.81-6.81l3-26.7A99.14,99.14,0,0,1,102.2,31.36l21,16.78a81.59,81.59,0,0,1,9.64,0l21-16.77a99.43,99.43,0,0,1,24.3,10.05l3,26.71a81,81,0,0,1,6.81,6.81l26.7,3a99.14,99.14,0,0,1,10.07,24.29l-16.78,21a81.59,81.59,0,0,1,0,9.64l16.77,21a99.43,99.43,0,0,1-10,24.3l-26.71,3a81,81,0,0,1-6.81,6.81l-3,26.7a99.14,99.14,0,0,1-24.29,10.07l-21-16.78a81.59,81.59,0,0,1-9.64,0l-21,16.77a99.43,99.43,0,0,1-24.3-10l-3-26.71a81,81,0,0,1-6.81-6.81Z" fill="none" stroke="currentColor" strokeLinecap="round" strokeLinejoin="round" strokeWidth="16"/></svg>
</Link>
Step2:
Remove theLandingSwitcher component from the main layout follow the path shared\layout-components\layout\ecommercelayout.tsx
import Landingswitcher from '@/shared/layout-components/switcher/landingswitcher'
<Landingswitcher isSwitcherOpen={isSwitcherOpen} toggleSwitcher={toggleSwitcher} />
Step3:
Now remove the landingswitcher component from the root folder, follow the path \shared\layout-components\switcher\landingswitcher.tsx and
Note: The landingswitcher component is used in ecommercelayout, while landinglayout utilizes the same landingswitcher.
Refer following links for usage:
| Icons | References |
|---|---|
| Bootstrap Icons | https://icons.getbootstrap.com/ |
| Boxicons | https://boxicons.com/ |
| Remix Icons | https://remixicon.com/ |
| Feather Icons | https://feathericons.com/ |
| Tabler Icons | https://tabler-icons.io/ |
| Line Awesome Icons | https://icons8.com/line-awesome |
| phosphor Icons | https://phosphoricons.com/ |
Used Plugins & Reference Links
All plugins are react integrated with npm.
1. You need to add these files to make it work.
| Type | URL |
|---|---|
| Plugin Link | https://swiperjs.com/get-started/ |
1. You need to add these files to make react-apexchart work.
| Type | URL |
|---|---|
| Plugin Link | https://apexcharts.com/react-chart-demos/ |
1. You need to add these files to make basic react-suneditor work.
| Type | URL |
|---|---|
| Plugin Link | https://www.npmjs.com/package/suneditor-react |
1. You need to add these files to make basic react-datePicker work.
| Type | URL |
|---|---|
| Plugin Link | https://www.npmjs.com/package/react-flatpickr |
1. You need to add these files to make basic react-select work.
| Type | URL |
|---|---|
| Plugin Link | https://www.npmjs.com/package/react-select |
1. You need to add below files to make basic gridjs table work.
| Type | URL |
|---|---|
| Plugin Link | https://www.npmjs.com/package/gridjs-react |
1. You need to add these files to make basic default table work.
1. You need to add these files to make react toastify work.
| Type | URL |
|---|---|
| Plugin Link | https://www.npmjs.com/package/react-toastify |
1. You need to add these files to make react rating work.
| Type | URL |
|---|---|
| Plugin Link | https://mui.com/material-ui/react-rating/ |
1. You need to add these files to make alerts work.
1. You need to add these files to make buttons work.
1. You need to add these files to make badges work.
1. You need to add these files to make button group work.
1. You need to add these files to make cards work.
1. You need to add these files to make breadcrumb work.
1. You need to add these files to make dropdown work.
1. You need to add these files to make tooltipss work.
1. You need to add these files to make yaireo/dragsort work.
1. You need to add these files to make Progress work.
1. You need to add these files to make List Group work.
1. You need to add these files to make toast work.
1. You need to add these files to make accordions work.
1. You need to add these files to make carousel work.
Please follow the below steps to change Primary Color
Step 1 :
To change Primary Color you have to open _variables.scss file and replace what color you want as shown in below
Rootpath : _variables.scss (\public\assets\scss\_variables.scss )
npm run sass command.
Please follow the below steps to change Dark body Color
Step 1 :
Make sure the theme is set completely to dark mode by adding the following attributes to the html tag data-theme-mode="dark" data-header-styles="dark" data-menu-styles="dark"
Step 2 :
To change Dark body Color you have to open _variables.scss file and replace what color you want as shown in below
Rootpath : _variables.scss (src/assets/scss/_variables.scss )
Step 3 :
Also Change the following variable colors to the desired theme background accordingly in [data-theme-mode="dark"]
--light-rgb : --form-control-bg : --input-border : --gray-3 : Note: After making the changes, run the npm run sass command.