FAQ (Frequently Asked Questions)

Q: Which Node.js version is required?

We recommend using the latest LTS version of Node.js (v18 or above). Using older versions may cause dependency issues.

Q: The dev server does not start after npm run dev. What should I do?

Make sure all dependencies are installed correctly. Delete the node_modules folder and package-lock.json, then run npm install again. If the problem persists, ensure you are using Node.js v18+.

Q: How do I change the logo?

Replace the files inside public/images:
- glint-logo-icon.png (sidebar icon)
- glint-text-logo.png (text logo)
Or update the paths in Sidebar.tsx under the .glint-brand section.

Q: How do I add a new language?

Create a new folder inside public/locales with your language code (e.g., es for Spanish). Add a translation.json file with your translated keys. i18next will automatically load it when you switch the language.

Q: How do I enable RTL mode?

RTL is enabled automatically when selecting a right-to-left language (e.g., Arabic or Hebrew). You can also manually call the applyDirection('ar', 'rtl') function in the Customizer.

Q: Can I use Glint with Next.js?

Glint is built with React + Vite. While it is not directly configured for Next.js, most components and styles can be reused with minimal changes. You would need to adjust routing and build settings for Next.js.

Q: How do I update theme colors?

Go to assets/scss/custom/custom-variables.scss and modify Bootstrap variable overrides. For example, change $primary color to your brand color. Recompile SCSS to apply changes globally.

Q: Is the Customizer required in production?

No. The Customizer is mainly for demo purposes. You can remove it completely or keep parts of it if you want theme switching for your users.

Q: Does Glint support API integration?

Yes. Most components (tables, charts, cards) are data-driven and already use JSON structures. You can easily replace JSON imports with API calls (using Axios or Fetch).