Hey Gonzalo,

Thanks for reaching out. Please extend your item support license to get assistance with the issue you’re experiencing.

Best

Thanks, how can I contact you privately?

actually I think what I need is the same as @mo7amedmo2nes comment

Hi,

Thanks for reaching out. Please contact us at leftforcode@gmail.com for further assistance. We’ll be happy to help with your request!

Best

Hi there,

Thank you for choosing Midone. We actually recommend building the assets locally on your computer. This way, whenever you make changes to the utility classes, the CSS assets will be regenerated automatically.

However, if you still require a version with precompiled assets, please reach out to us at leftforcode@gmail.com.

Best regards

thanks for your respond i have sent the email please review it

Hi,

We replied to your request via email a few days ago. Please check your inbox. 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

Hi there,

Sure! Please provide your email address so that we can send you the compiled version of the clean HTML files.

I send

File sent, thanks!

Hi there,

Thanks for reaching out. Actually, those classes aren’t just sitting there in the CSS file waiting to be used. They’re generated on the fly when you compile your code with Tailwind.

To get those classes to show up, make sure you’re running the Tailwind compiler. Once it’s up and running, it’ll generate all the classes you need based on your code and Tailwind configuration.

Please check this link for more details.

If you need a hand setting up the compiler, just give me a shout. Happy to help!

Best regards

Hi there,

Thanks for reaching out. It sounds like the issue might be caused by the plugin being initialized before your AJAX request to generate the options is completed. To fix this, you’ll need to ensure that the plugin initialization is placed after your AJAX callback.

Please take a look at the file related to this issue: ”/src/js/components/base/tom-select.js”. You may need to adjust the code so that the plugin initialization occurs after the AJAX callback is executed.

Let me know if you need further assistance or clarification.

Best regards

Hey,

So, using subdirectories on a web server, like in your case with “http://127.0.0.1/midoen/Source/”, might not fly as smoothly because we tend to add a ”/” to each external asset called from within the HTML file by default. Our dev team rolls with a virtual domain setup like “http://tailwise-html.test/index.html”, so this issue didn’t pop up earlier.

But hey, good news! We’ve dropped an update to remove the ”/” from all loaded assets, and we’ve also ditched ‘type=”module”’ from the JS asset loading tag, which was gumming up the works for drag-and-drop opening in the browser.

Now, you should be able to open the file directly in the browser (via drag-and-drop) without using a web server. Just grab the latest update by downloading the template files again.

Best regards

I confirm, everything works. Thank you.

Great to hear that everything is working well for you! If you have any more questions or need further assistance in the future, feel free to reach out. Have a fantastic day!

Hey there,

Thanks for your interest in Enigma! I appreciate you reaching out with your question. Currently, we don’t have a version of Enigma where the top menu is placed within the blue bar instead of below it. It’s a great suggestion though, and I’ll make sure to pass it along to our development team for consideration.

We’re always looking for ways to improve our themes based on feedback from customers like you. If you have any other questions or if there’s anything else I can assist you with as you consider purchasing the template, feel free to let me know. I’m here to help!

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,

Thank you for reaching out to us,

You can apply a refund as long as the item has not been downloaded. Please visit this link to submit the refund request.

Hope this helps.

Hi,

The CSS template file won’t be available unless you run the compiler because Tailwind needs to scan the required classes on each page to generate the necessary utility classes.

If you have completed your development mode, you can execute the command `yarn run build` to generate the CSS file suitable for production. The resulting build file will be located in the `/dist` directory. You can transfer all the build files to your hosting server or local machine for execution. Make sure not to place them in a subdirectory since the default asset loaded is the static path.

Feel free to check out the following video for a more comprehensive demonstration.

Hi,

To assist you better, could you please provide more details about the specific problems you’re encountering?

Hello there!

We’ve just rolled out the latest version with Vite. Could you kindly let us know if you are currently using the Laravel Mix version?

Hi,

Yes, a new theme, “Invoker,” is in the pipeline and will be released soon. Stay tuned for updates, and thank you for your interest!

If you have any more questions or if there’s anything else we can help you with, feel free to let us know.

Best regards.

Hi,

Could you provide more detailed information on why you’re unable to download the file? This will help us better understand and assist you in resolving the issue.

Thank you for your cooperation!

Hi,

Integration with specific frameworks or languages is not within our direct support scope. However, we can provide references to assist you. Ensure that the content configuration in your tailwind.config.js matches your project directory so that the Tailwind compiler can recognize the class names used in your project.

If you have further questions or need additional guidance, feel free to ask.

Best regards.

Hi,

Thank you for reaching out to us,

Yes, this template is designed to work completely without jQuery. It utilizes modern web standards and native JavaScript to ensure compatibility with a wide range of environments and reduces dependencies on external libraries. If you have any specific concerns or questions regarding the template’s functionality, feel free to let us know, and we’ll be happy to assist!

I try include Tailwind CSS via <script src=”https://cdn.tailwindcss.com”></script> – but not working .

Hi,

Thank you for contacting us. In the previous version (using Laravel Mix), all JS assets were imported in “app.js,” so you needed to configure it manually to separate JS files needed for each page. We have just released the latest version with Vite.

In this latest version, we have separated each JS file for 3rd party libraries, plugin initialization, pages, and more, resulting in smaller JS file sizes for each page.