Hey there,

Thanks for the kind words! It’s great to hear you’re enjoying the template.

To make the login page the start page, simply open the file “src/router/index.ts” and change the component for the path ”/” from ”../pages/DashboardOverview1.vue” to ”../pages/Login.vue”.

As for a good Vue.js tutorial, I recommend checking out Vue Mastery or Vue School for comprehensive courses.

If you need further assistance, feel free to reach out.

Best

Hi there,

Thanks for your question! We might consider it in the future. Stay tuned!

Hi Luis,

Thanks for reaching out and sorry for the delayed response. We realized there was some missing code in our example on the “File Upload” page. We’re working on updating it soon. In the meantime, here’s an example code snippet to get the list of uploaded files:

<script setup lang="ts">
import Dropzone, { type DropzoneElement } from "@/components/Base/Dropzone";
import { onMounted, ref, provide } from "vue";

const dropzoneSingleRef = ref<DropzoneElement>();

provide("bind[dropzoneSingleRef]", (el: DropzoneElement) => {
  dropzoneSingleRef.value = el;
});

onMounted(() => {
  const elDropzoneSingleRef = dropzoneSingleRef.value;
  if (elDropzoneSingleRef) {
    elDropzoneSingleRef.dropzone.on("success", () => {

      // Show uploaded files
      console.log(elDropzoneSingleRef.dropzone.files);
    });
    elDropzoneSingleRef.dropzone.on("error", () => {
      alert("No more files please!");
    });
  }
});
</script>

Please check link below for more details.
https://docs.dropzone.dev/configuration/basics/methods

Hope this helps! Let us know if you need any more assistance.

Hello,

Thank you for choosing our Midone – Tailwind CSS Vuejs 3 Admin Dashboard Template!

Yes, you can absolutely install and test the template in your local environment before moving it online for production. Please follow these steps to get started:

1. Download and unzip the template files. 2. Navigate to the template directory in your terminal. 3. Install dependencies:

npm install

4. Run the development server:

npm run dev

This will start a local server and you can view the template in your browser. If you need any further assistance, feel free to reach out.

Thanks again for using our template!

Best regards

Below is the error we got running npm install and npm run dev on our local environment. Kindly assist.

C:\iworkspace\nportal\Source>npm install -(node:5292) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit (Use `node—trace-warnings …` to show where the warning was created)

up to date, audited 305 packages in 15s

51 packages are looking for funding run `npm fund` for details

1 high severity vulnerability

Some issues need review, and may require choosing a different dependency.

Run `npm audit` for details.

C:\iworkspace\nportal\Source>npm run dev

> midone-vue@0.0.0 dev > vite X [ERROR] Unterminated string literal

node_modules/@ckeditor/ckeditor5-build-classic/build/ckeditor.js.map:1:287888:
    1 │ ...4uC,MAGnC+K,CACR,CAuBO,eAAAh1B,CAAiBy0B,GACvB,GAAKp5C,KAAK45C,eAAgBR,GAAe,CAGxC,IAAIS,EAAmB75C,KAAK2uC,MA
      ╵                                                                                                             ^

The source map "node_modules/@ckeditor/ckeditor5-build-classic/build/ckeditor.js.map" was
referenced by the file "node_modules/@ckeditor/ckeditor5-build-classic/build/ckeditor.js" here:

node_modules/@ckeditor/ckeditor5-build-classic/build/ckeditor.js:7:21:
  7 │ //# sourceMappingURL=ckeditor.js.map
    ╵                      ~~~~~~~

5:22:29 AM [vite] Pre-transform error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ 5:22:29 AM [vite] Pre-transform error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ (x2) 5:22:29 AM [vite] Pre-transform error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ (x3) 5:22:30 AM [vite] Pre-transform error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ (x4) 5:22:30 AM [vite] Pre-transform error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ (x5) 5:22:30 AM [vite] Pre-transform error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ (x6) 5:22:30 AM [vite] Pre-transform error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ (x7) 5:22:30 AM [vite] Pre-transform error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ (x8) 5:22:30 AM [vite] Pre-transform error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ (x9) 5:22:30 AM [vite] Pre-transform error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ (x10) 5:22:30 AM [vite] Pre-transform error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ (x11) 5:22:30 AM [vite] Pre-transform error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ (x12)

A PostCSS plugin did not pass the `from` option to `postcss.parse`. This may cause imported assets to be incorrectly transformed. If you’ve recently added a PostCSS plugin that raised this warning, please contact the package author to fix the issue. 5:22:31 AM [vite] Internal server error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ Plugin: vite:css File: C:/iworkspace/nportal/Source/node_modules/@left4code/tw-starter/dist/css/mixins/_media.css:3:2 1 | /* Breakpoint up / 2 | @mixin media-breakpoint-up($screen) { 3 | @media (min-width: calc(theme(“screens.#{$screen}”) – 1px)) { | ^ 4 | & { 5 | @content; at C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3 at Input.error (C:\iworkspace\nportal\Source\node_modules\postcss\lib\input.js:106:16) at AtRule.error (C:\iworkspace\nportal\Source\node_modules\postcss\lib\node.js:115:32) at Object.theme (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:207:28) at resolveVNode (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:133:45) at C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:141:9 at walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\walk.js:7:22) at walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\walk.js:10:13) at walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\walk.js:10:13) at ValueParser.walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\index.js:16:5) at resolveFunctions (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:140:39) 5:22:31 AM [vite] Internal server error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ Plugin: vite:css File: C:/iworkspace/nportal/Source/node_modules/@left4code/tw-starter/dist/css/mixins/_media.css:3:2 1 | / Breakpoint up / 2 | @mixin media-breakpoint-up($screen) { 3 | @media (min-width: calc(theme(“screens.#{$screen}”) – 1px)) { | ^ 4 | & { 5 | @content; at C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3 at Input.error (C:\iworkspace\nportal\Source\node_modules\postcss\lib\input.js:106:16) at AtRule.error (C:\iworkspace\nportal\Source\node_modules\postcss\lib\node.js:115:32) at Object.theme (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:207:28) at resolveVNode (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:133:45) at C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:141:9 at walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\walk.js:7:22) at walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\walk.js:10:13) at walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\walk.js:10:13) at ValueParser.walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\index.js:16:5) at resolveFunctions (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:140:39) (x2) 5:22:31 AM [vite] Internal server error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ Plugin: vite:css File: C:/iworkspace/nportal/Source/node_modules/@left4code/tw-starter/dist/css/mixins/_media.css:3:2 1 | / Breakpoint up / 2 | @mixin media-breakpoint-up($screen) { 3 | @media (min-width: calc(theme(“screens.#{$screen}”) – 1px)) { | ^ 4 | & { 5 | @content; at C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3 at Input.error (C:\iworkspace\nportal\Source\node_modules\postcss\lib\input.js:106:16) at AtRule.error (C:\iworkspace\nportal\Source\node_modules\postcss\lib\node.js:115:32) at Object.theme (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:207:28) at resolveVNode (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:133:45) at C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:141:9 at walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\walk.js:7:22) at walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\walk.js:10:13) at walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\walk.js:10:13) at ValueParser.walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\index.js:16:5) at resolveFunctions (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:140:39) (x3) 5:22:31 AM [vite] Internal server error: [postcss] C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ Plugin: vite:css File: C:/iworkspace/nportal/Source/node_modules/@left4code/tw-starter/dist/css/mixins/_media.css:3:2 1 | / Breakpoint up */ 2 | @mixin media-breakpoint-up($screen) { 3 | @media (min-width: calc(theme(“screens.#{$screen}”) – 1px)) { | ^ 4 | & { 5 | @content; at C:\iworkspace\nportal\Source\node_modules\@left4code\tw-starter\dist\css\mixins\_media.css:3:3 at Input.error (C:\iworkspace\nportal\Source\node_modules\postcss\lib\input.js:106:16) at AtRule.error (C:\iworkspace\nportal\Source\node_modules\postcss\lib\node.js:115:32) at Object.theme (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:207:28) at resolveVNode (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:133:45) at C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:141:9 at walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\walk.js:7:22) at walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\walk.js:10:13) at walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\walk.js:10:13) at ValueParser.walk (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\value-parser\index.js:16:5) at resolveFunctions (C:\iworkspace\nportal\Source\node_modules\tailwindcss\lib\lib\evaluateTailwindFunctions.js:140:39) (x4) C:\iworkspace\nportal\Source\node_modules\esbuild\lib\main.js:1472 let error = new Error(text); ^

Error: Build failed with 1 error: node_modules/@ckeditor/ckeditor5-build-classic/build/ckeditor.js.map:1:287888: ERROR: Unterminated string literal at failureErrorWithLog (C:\iworkspace\nportal\Source\node_modules\esbuild\lib\main.js:1472:15) at C:\iworkspace\nportal\Source\node_modules\esbuild\lib\main.js:945:25 at C:\iworkspace\nportal\Source\node_modules\esbuild\lib\main.js:1353:9 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) { errors: [Getter/Setter], warnings: [Getter/Setter] }

Node.js v20.5.0

Hi there,

Sorry for the delay in getting back to you. It seems like we’re not quite familiar with the error you’re experiencing. Could you please provide a step-by-step guide to reproduce the issue? It would be even more helpful if you could send a screen recording of the terminal errors so we can analyze the issue in more detail.

Thank you!

Hi,

If you need only the core template without Laravel, please check out the HTML version of our template at this link:

https://themeforest.net/item/midone-jquery-tailwindcss-html-admin-template/26366820

Thank you for choosing our template! If you have any other questions, feel free to reach out.

Best regards

Hi there,

Thank you for using our template!

Unfortunately, we don’t currently use Docker, so we’re unable to assist you with this.

Hey there,

Thanks for choosing our template! However, currently, our team primarily works with TypeScript. We find that the structured typing helps reduce errors in our applications.

One solution we can suggest for now is to enable the following configuration in “tsconfig.app.json”, where we configure TypeScript to allow regular JavaScript writing in the project:

{
  "extends": "@vue/tsconfig/tsconfig.dom.json",
  "include": ["env.d.ts", "src/**/*", "src/**/*.vue"],
  "exclude": ["src/**/__tests__/*"],
  "compilerOptions": {
    "allowJs": true,  // Allow JavaScript files to be included
    "checkJs": false, // Disable type checking for JavaScript files
    "verbatimModuleSyntax": false,
    "composite": true,
    "noEmit": true,
    "baseUrl": ".",
    "paths": {
      "@/*": ["./src/*"]
    }
  }
}

However, if you still require the JavaScript version of Midone, you’ll need to perform the conversion yourself.

Let us know if you have any other questions or concerns!

Thanks again!

Hi there,

Sorry for the delayed response. Could you please provide more details about the component you’re working on related to this issue? It would be helpful if you could share the complete code that’s causing the problem.

Thanks for your patience, and we look forward to helping you resolve this!

Thank you

It’s not a single component, it’s the full app. I converted the project to work without TS, and any page that I try to load, shows a full blank page and an error on headlessui “MISSING PARENT”

Hi there,

To help you with this issue, I need to know which part of the app you’re working on when this error occurs. You should debug the problem and provide more detailed information.

If you want to use JavaScript in a TypeScript project, you can modify the TypeScript configuration in “tsconfig.app.json” as follows, so you can write regular JavaScript without type checking:

{
  "extends": "@vue/tsconfig/tsconfig.dom.json",
  "include": ["env.d.ts", "src/**/*", "src/**/*.vue"],
  "exclude": ["src/**/__tests__/*"],
  "compilerOptions": {
    "allowJs": true,  // Allow JavaScript files to be included
    "checkJs": false, // Disable type checking for JavaScript files
    "verbatimModuleSyntax": false,
    "composite": true,
    "noEmit": true,
    "baseUrl": ".",
    "paths": {
      "@/*": ["./src/*"]
    }
  }
}

If you still want to transform the project to JavaScript, please note that this is not typically included in our support and would be your responsibility.

However, we are willing to assist if you can provide information on which part of the project is causing the error. Without any information, it’s challenging to help you debug the issue.

Hi there,

Thanks for mentioning this issue. We’ve added the CSS code you provided to our latest update. If you have any other questions or need further assistance, feel free to reach out.

Thank you!

Hi there,

Totally get where you’re coming from. While this is indeed an HTML template, Tailwind CSS operates a bit differently compared to traditional CSS frameworks. It generates CSS styles based on what’s used in your HTML, hence the need to run the Tailwind compiler.

Regarding where to run those commands, yup, usually from the root directory. But no worries, if you’re not familiar with Node.js or Visual Studio Code, we can help you out. We’ll send over the compiled version of the template to get you started on your project.

Just a heads up though, not all utility classes might be readily available from the Tailwind documentation. If you need additional ones, you’ll have to run the compiler again. We’re here to assist every step of the way!

Hi there,

Thank you for reaching out. The template utilizes Tailwind CSS, which means we need to run the Tailwind compiler to generate the necessary CSS utilities.

Here are the steps to resolve this issue:

1. Install Dependencies: You can install it via npm or yarn by running:

yarn install

or

npm install

2. 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.

3. 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,

In the Rubick version, the dropdown menu is intentionally designed to open to the side rather than below. If you have any further questions or need assistance with anything else, feel free to ask!

Hi,

Thank you for bringing this to our attention. We’ve recently updated the theme and replaced the <DarkModeSwitcher /> and <MainColorSwitcher /> components with the <ThemeSwitcher> component. To remove the switcher, you can open the file ”/src/themes/Layout.vue” and remove the <ThemeSwitcher> component initialization.

If you have any further questions or need assistance, please don’t hesitate to reach out. We’re here to help!

Hi there,

Thanks for reaching out and for the kind words about the template!

Regarding the message you’re seeing in the terminal, it’s a known issue caused by one of the PostCSS plugins used in the template. However, rest assured, it won’t affect the security of your code as it only occurs during development.

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

Best regards.

Hi there,

Sure thing! You can apply for a refund for the HTML version by clicking on this link:

https://help.market.envato.com/hc/en-us/articles/202821460-Can-I-Get-A-Refund

Let me know if you need any further assistance.

Best regards

Hi there,

Thanks for reaching out. Unfortunately, the Figma version of the Midone – Vuejs 3 Admin Dashboard Template + HTML Version template isn’t available at the moment. The materials are currently provided in .xd format.

Let me know if there’s anything else I can assist you with.

Best regards

Hey there,

Thanks for reaching out. I totally understand your situation, and I’m sorry for any inconvenience this might cause. As of now, we’ve merged all our themes, including the starter templates and full themes, into one comprehensive package.

However, I definitely hear you, and your feedback is important to us. While we don’t provide the starter version separately anymore, if we receive more requests from other buyers for it, we’ll definitely consider bringing it back.

In the meantime, if there’s anything else I can assist you with or if you have any other questions, feel free to let me know. I’m here to help!

Warm regards

Hello,

To make the HTML version work, please follow these steps:

Install Node.js: If you haven’t already, download and install Node.js from the official website: Node.js Download.

https://nodejs.org/en

1. Navigate to the Project Directory: Open a terminal or command prompt and navigate to the directory where you have downloaded the HTML version repository.

2. Install Dependencies: Run the following command to install the project dependencies:

npm install

3. Run Development Server: To run the development server and view the HTML version in your browser, use the following command:

npm run dev

This command will start a development server, compile the source code, and open the application in your default web browser. You can then view and interact with the HTML version.

4. Build for Production: If you want to build the project for production, run the following command:

npm run build

This command will compile the source code and produce optimized assets for deployment. You can then find the built assets in the `dist` directory.

If you encounter any issues or have any questions during the process, please don’t hesitate to ask. We’re here to assist you!

Best regards

Certainly,

Indeed, we plan to maintain the utilization of version numbers in our upcoming release. Additionally, we will include the starter version for your convenience. Thank you for your feedback and continued support. If you have any further questions or suggestions, feel free to let us know.

Best regards