Hi there,

Thanks for using our template! Unfortunately, it looks like we don’t have a “not found” page for the Tailwise theme at the moment.

Let us know if there’s anything else we can help with!

Best regards

Hi there,

Thanks for reaching out!

Unfortunately, that’s not possible at the moment.

Hi,

Email sent, please check your email..

Hi there,

Yep, dark mode is on our list of updates, but we haven’t started working on it just yet. With our current workload, we can’t confirm exactly when the dark mode version will be released, but it’s definitely in the pipeline.

Best regards

Hi there,

Absolutely, this template can be used in a React application!

However, detailing the steps would take some time and isn’t covered in the item support package. If you need a React version, you might want to check out the Tailwise React version available at this link.

https://themeforest.net/item/tailwise-react-typecript-admin-dashboard-template/51856970

We can also send you the compiled CSS version. Please share your email address for that.

Best regards,

Hi there,

Could you please provide more details about the difficulties you’re experiencing? Have you installed the dependencies and run the compiler?

The Tailwise template files are indeed extensive due to our current 11 themes. If you can elaborate on your specific challenges, we’ll be better equipped to assist you.

Best regards

Hi there,

I appreciate your message, and I’m here to help you get started with the template. It seems like there might be some confusion about how to use it effectively. Let me provide you with some guidance:

Understanding Tailwind CSS Compilation:

1. Dynamic Utility Classes: The template you purchased is designed using Tailwind CSS, a utility-first CSS framework. Tailwind relies on dynamic utility classes to style elements. This approach offers flexibility and customization without the need for writing custom CSS.

2. Build Process: Unlike traditional CSS frameworks, Tailwind doesn’t include a precompiled CSS file in the source code. Instead, it utilizes a build process to generate the final CSS file. This process ensures that only the necessary styles are included based on the utility classes used in your HTML.

Getting Started:

1. Install Dependencies: Make sure you have Node.js and npm installed on your machine. These are required for managing project dependencies.

2. Navigate to Project Directory: Open a terminal or command prompt and navigate to the directory where you have the template files.

3. Install Node Modules: Run npm install to install the project-specific dependencies, including Tailwind CSS.

4. Run Build Command: Execute the build command to compile the Tailwind CSS. The command might look something like:

yarn run build

This command processes your stylesheets, applies the utility classes, and outputs the final CSS file.

5. Development Mode (Optional): If you’re making changes to the template, you can use a watch command that automatically recompiles the CSS when changes are detected:

yarn run dev

Locating Assets:

After running the build command, look for the compiled CSS and JS files in the project directory. Update your HTML files to reference these files. The specific paths may vary based on your project structure.

If you have any specific questions or encounter issues at any step, feel free to reach out. I’m here to assist you in getting the most out of the template.

Best regards

The build is taking too long to compile. How long is the average time?

Hey,

Thanks for the heads-up!

So, the build time can be a bit unpredictable. It really depends on how fast your computer is processing along. On our end, we’ve seen it take anywhere from 8 to 10 seconds.

Running “yarn run dev” in development mode definitely helps speed things up big time. But if you’re still stuck waiting forever, try this trick: only mess with the HTML files for the theme you’re into. They all start with the theme’s name, like “dagger-dashboard-overview-1.html” for the “dagger” theme. Trim out the files for other themes, and you might just shave off some time.

Hit me up if you need more help or have other questions.

Best regards

Thanks!

Hi there,

I appreciate your message, and I’m here to help you get started with the template. It seems like there might be some confusion about how to use it effectively. Let me provide you with some guidance:

Understanding Tailwind CSS Compilation:

1. Dynamic Utility Classes: The template you purchased is designed using Tailwind CSS, a utility-first CSS framework. Tailwind relies on dynamic utility classes to style elements. This approach offers flexibility and customization without the need for writing custom CSS.

2. Build Process: Unlike traditional CSS frameworks, Tailwind doesn’t include a precompiled CSS file in the source code. Instead, it utilizes a build process to generate the final CSS file. This process ensures that only the necessary styles are included based on the utility classes used in your HTML.

Getting Started:

1. Install Dependencies: Make sure you have Node.js and npm installed on your machine. These are required for managing project dependencies.

2. Navigate to Project Directory: Open a terminal or command prompt and navigate to the directory where you have the template files.

3. Install Node Modules: Run npm install to install the project-specific dependencies, including Tailwind CSS.

4. Run Build Command: Execute the build command to compile the Tailwind CSS. The command might look something like:

yarn run build

This command processes your stylesheets, applies the utility classes, and outputs the final CSS file.

5. Development Mode (Optional): If you’re making changes to the template, you can use a watch command that automatically recompiles the CSS when changes are detected:

yarn run dev

Locating Assets:

After running the build command, look for the compiled CSS and JS files in the project directory. Update your HTML files to reference these files. The specific paths may vary based on your project structure.

If you have any specific questions or encounter issues at any step, feel free to reach out. I’m here to assist you in getting the most out of the template.

Best regards

You don’t answer questions, your service is very bad

Hello,

Thank you for reaching out, and I apologize for the delay in my response.

I understand your concern, and I want to assure you that I’m here to assist you promptly. As per our policy, our response time can take up to 2 business days.

Regarding your inquiry about styling input file elements, I’ve included an example code snippet below that you can use:

<input id="regular-form-6" type="file" placeholder="Input file" class="disabled:bg-slate-100 disabled:cursor-not-allowed dark:disabled:bg-darkmode-800/50 dark:disabled:border-transparent [&[readonly]]:bg-slate-100 [&[readonly]]:cursor-not-allowed [&[readonly]]:dark:bg-darkmode-800/50 [&[readonly]]:dark:border-transparent transition duration-200 ease-in-out w-full text-sm border-slate-200 shadow-sm rounded-md placeholder:text-slate-400/90 focus:ring-4 focus:ring-primary focus:ring-opacity-20 focus:border-primary focus:border-opacity-40 dark:bg-darkmode-800 dark:border-transparent dark:focus:ring-slate-700 dark:focus:ring-opacity-50 dark:placeholder:text-slate-500/80 [&[type='file']]:border file:mr-4 file:py-2 file:px-4 file:rounded-l-md file:border-0 file:border-r-[1px] file:border-slate-100/10 file:text-sm file:font-semibold file:bg-slate-100 file:text-slate-500/70 hover:file:bg-200 group-[.form-inline]:flex-1 group-[.input-group]:rounded-none group-[.input-group]:[&:not(:first-child)]:border-l-transparent group-[.input-group]:first:rounded-l group-[.input-group]:last:rounded-r group-[.input-group]:z-10">

You can also view the example directly at the following link: https://tailwise-html.vercel.app/echo-regular-form.html

If you have any further questions or need additional assistance, please feel free to reach out. Thank you for your understanding.

Best regards

Hi there,

I hope this message finds you well. I noticed your concerns about the HTML version not working locally and the page loading without styles, scripts, or functions. Allow me to clarify a few key points to ensure a smooth experience running the HTML version on your local environment.

1. Tailwind CSS Compilation: The HTML version utilizes Tailwind CSS, a popular utility-first CSS framework. Tailwind CSS relies on a build process to generate the final CSS file that includes all the styles based on the utility classes used in your HTML. It doesn’t include a precompiled CSS file in the source code to keep the project flexible and allow for customization.

2. Build Commands: To compile Tailwind CSS and generate the necessary assets, you should run the build command. In a typical development setup, you might have a command like: `yarn build` or `npm build` This command processes your stylesheets, applies the utility classes, and outputs the final CSS file. Ensure you have Node.js installed and the required dependencies in your project.

3. Development Mode: During development, you may want to use a watch command that monitors your files for changes and automatically recompiles the CSS. For example: `yarn run dev` or `npm run dev` This keeps your styles in sync with your changes and ensures a dynamic development experience.

4. Locally Running the HTML Version: After running the build commands, make sure your HTML files reference the correct paths to the compiled CSS and JavaScript files. The paths may vary based on your project structure.

5. Dependencies: Double-check that you have all the required dependencies installed, including Node.js, npm, and any other project-specific dependencies.

If you encounter any issues or have further questions, please don’t hesitate to reach out. I’m here to assist you in getting the HTML version up and running smoothly on your local environment.

Best regards

Hi there,

I appreciate your message, and I’m here to help you get started with the template. It seems like there might be some confusion about how to use it effectively. Let me provide you with some guidance:

Understanding Tailwind CSS Compilation:

1. Dynamic Utility Classes: The template you purchased is designed using Tailwind CSS, a utility-first CSS framework. Tailwind relies on dynamic utility classes to style elements. This approach offers flexibility and customization without the need for writing custom CSS.

2. Build Process: Unlike traditional CSS frameworks, Tailwind doesn’t include a precompiled CSS file in the source code. Instead, it utilizes a build process to generate the final CSS file. This process ensures that only the necessary styles are included based on the utility classes used in your HTML.

Getting Started:

1. Install Dependencies: Make sure you have Node.js and npm installed on your machine. These are required for managing project dependencies.

2. Navigate to Project Directory: Open a terminal or command prompt and navigate to the directory where you have the template files.

3. Install Node Modules: Run npm install to install the project-specific dependencies, including Tailwind CSS.

4. Run Build Command: Execute the build command to compile the Tailwind CSS. The command might look something like:

yarn run build

This command processes your stylesheets, applies the utility classes, and outputs the final CSS file.

5. Development Mode (Optional): If you’re making changes to the template, you can use a watch command that automatically recompiles the CSS when changes are detected:

yarn run dev

Locating Assets:

After running the build command, look for the compiled CSS and JS files in the project directory. Update your HTML files to reference these files. The specific paths may vary based on your project structure.

If you have any specific questions or encounter issues at any step, feel free to reach out. I’m here to assist you in getting the most out of the template.

Best regards

Hi there,

Absolutely, let’s dive into a more detailed integration process to ensure everything aligns perfectly. Below are step-by-step instructions:

1. Step 1: Create Laravel Project

composer create-project --prefer-dist laravel/laravel your-laravel-project
cd your-laravel-project

2. Copy Assets and Configuration Files to Laravel

- /src
- /esbuild.config.js 
- /postcss.config.js 
- /tailwind.config.js

3. Adjust `package.json` from Tailwise HTML to the Laravel project.

4. Configure output files in `esbuild.config.js` to Laravel public directory.

5. Install dependencies `yarn install`.

6. Run compiler `yarn run dev`.

7. Include necessary asset files in blade file.

8. Start the Laravel development server:

php artisan serve

Visit http://localhost:8000 in your browser to view your Laravel application with the integrated Tailwise Template.

Hi there,

The issue has been resolved, and our preview site is back up and running!

You can now explore the template, check out the files, and dive into the awesomeness. If you have any more questions or if there’s anything specific you’d like assistance with, just drop me a message. We’re here to make sure you have a seamless experience.

Thanks for your patience and understanding. If there’s anything else you need, feel free to reach out.

Dear jjonthan,

Thank you for bringing this to our attention. We apologize for any inconvenience you may have experienced. Regarding the missing icons in the Figma file, we’d like to clarify that the icons in the Tailwise template are sourced from the Lucide icon set.

To access and download the Lucide icons, please visit the official Lucide website:

https://lucide.dev/

You can explore the collection, find the specific icons you need, and download them directly from the Lucide website.

If you have any further questions or need assistance, feel free to reach out. We appreciate your understanding and patience.

Best regards

Hi,

Absolutely! Tailwise is already mobile-responsive, ensuring a seamless experience across different devices.

If you have any more questions or need further assistance, feel free to ask!

Cheers

Hello,

We hope this message finds you well!

We’re reaching out to let you know that we’ve addressed the issue you reported. Specifically, we’ve added the required CSS file to the project. For the latest updates, we kindly recommend to re-download the project.

Thank you for your patience and happy coding!

Now i got the same error for ’”hurricane-landing-page.html’

Hello there!

Thank you for bringing this to our attention. We’re delighted to share that we’ve just released an update with ESBuild, eliminating the need for manual page registration during HTML file compilation. You can now enjoy a smoother experience without encountering this issue again.

For more detailed information, please refer to the updated documentation file. To make sure you have all the latest enhancements, we recommend downloading the most recent package.

Hi befine,

Thank you for the positive feedback! Currently, we don’t have plans to release a Svelte version. However, if there’s an increasing demand from our users, we’ll certainly consider it for future releases. Your input is valuable to us, and we appreciate your interest.

Feel free to reach out if you have any more suggestions or questions!

Best regards

Hi JLesuperb,

Thanks for reaching out! Currently, we’re not able to assist with direct integration into Angular. However, if you encounter any issues or run into errors during the integration process, feel free to get in touch. We’d be happy to provide assistance and help troubleshoot any challenges you might come across.

Thanks for your understanding, and we’re here to help however we can!

Cheers