Discussion on Tailux - React Tailwind Admin Template (React 19)

Discussion on Tailux - React Tailwind Admin Template (React 19)

Cart 1,288 sales
Recently Updated
Well Documented

PiniaStudio supports this item

Supported

This author's response time can be up to 2 business days.

213 comments found.

I want to develop with Laravel. Do you have the HTML, CSS, and JavaScript files?

Hi, This is React template, for HTML/Laravel, you can check https://themeforest.net/item/lineone-multipurpose-admin-and-webapp-ui-kit-based-on-tailwind-css/38247812

Best Regards

Request for Technical Architecture & Library Details – React Template

Hello,

I hope you’re doing well.

I am planning to build a large-scale, production-grade application using React, and I am currently evaluating templates on ThemeForest for long-term use. Your template stood out to me, and I am very interested in purchasing it.

Before proceeding, I wanted to understand a bit more about the technical foundation to ensure it aligns with my project requirements. Specifically, I would appreciate it if you could share details on:

Overall frontend architecture and folder structure

State management approach (e.g., Redux, Zustand, Context API, etc.)

Routing strategy

Styling solution used (CSS modules, styled-components, Tailwind, etc.)

Major third-party libraries and their purpose

Scalability considerations and best practices followed

TypeScript usage (if applicable)

Testing setup (if included)

My goal is to choose a template that is maintainable, scalable, and suitable for enterprise-level development.

Thank you for your time and support. I look forward to your response and hopefully working with your template.

Best regards, Hiren

Hi Hiren,

Thank you for your message and for your interest in our React template, we’re glad it caught your attention.

We actively maintain and update the theme with long-term support, including compatibility updates and improvements over time.

Here are the technical details you requested:

Frontend architecture & folder structure: The project follows a modular and scalable folder structure. Each feature/module is organized separately, making it easy to add, modify, or remove modules as your application grows. Shared components, layouts, and utilities are clearly separated to support enterprise-level maintainability.

State management: We use the React Context API by default. This keeps the core lightweight and makes it easy to integrate any external state management library such as Redux, Zustand, or others if your project requires more advanced patterns.

Routing strategy: Routing is implemented using React Router.

Styling solution: We use Tailwind CSS for styling.

Third-party libraries: A curated set of commonly used and production-ready libraries is included for UI, forms, charts, and utilities. You can find the full and up-to-date list here: https://tailux.piniastudio.com/docs/attributions.

Scalability & best practices: The template is built with reusability and scalability in mind, including modular design, reusable UI components, separation of concerns, and configurable layouts.

TypeScript support: We provide two editions: TypeScript and JavaScript. You can choose the version that best fits your workflow and team requirements.

For more detailed documentation and structure overview, please see: https://tailux.piniastudio.com/docs/getting-started.

If you have any additional technical questions, I’ll be happy to clarify them.

Best regards

infra66

infra66 Purchased

Hello Tailux Support Team,

I hope you’re doing well. I’m currently using the Tailux multi-select/autocomplete component in my project and have also built a custom personal component for comparison (screenshots attached). I wanted to ask if it would be possible for your team to either update the existing component or introduce a new variant with the following improvements: 1. Selected Items Count Display When multiple values are selected: Automatically calculate the total selected items Display the count (e.g., “3 selected”, “5 selected”) instead of, or in addition to, listing all selected values inside the input This would greatly improve readability when many items are selected. 2. Clear Search Input After Selection (UX Improvement) Currently, when I: Type a search term (e.g., “w”) Select an option from the dropdown The search text remains in the input, requiring the user to manually backspace and clear it before performing another search. This feels a bit unintuitive from a UX perspective. In my custom component, the search input automatically clears after selection, allowing users to continue searching immediately, which provides a smoother experience. It would be great if the Tailux component could: Automatically clear the search input after an item is selected Keep focus in the input for faster multi-selection Since I’ve purchased an additional support plan, I wanted to check if these enhancements are feasible or planned for a future update. Thank you for your time and support. I appreciate your work on Tailux and look forward to your guidance. Best regards, RS.

Hello RS,

Thank you for reaching out, and for the detailed explanation. We truly appreciate the time you took to share thoughtful feedback. There are not any screenshots, can you send your screenshots in piniahelp@gmail.com ?

Will I get lifetime updates with this theme?

Hi, Yes.

Hi Team, Can you please share UX design for this template

Hi, we dont have figma files.

Can I get figma along with the theme for mobile view?

Hi, we currently don’t have the Figma designs available. Best regards,

saulol

saulol Purchased

Where can I find the project figma? with the components?

Hi, we currently don’t have the Figma designs available. Best regards,

Hi! Is there a landing page that comes with this? I love the page at https://tailux-landing.vercel.app but I’m not able to find it in the demo app.

Hi! Thanks for your purchase and your comment.

The demo landing page is built with Next.js and React.js. It’s only meant to showcase Tailux features and isn’t part of the commercial package, so support for it isn’t included.

However, if you’d like access to the source code, just share your GitHub username and I’ll add you to the landing page demo repo

Best Regards

That would be amazing! Thanks! My GitHub username is primetheus

Invited

I recently purchased Tailux. I’m trying to compile the demo and starter with `npm run build`, but it’s generating errors and not completing the process in both JavaScript and TypeScript. Could you please help me with this?

papa@salmos:/workspace/tailux/ts/demo$ npm run dev

> react-tailux-ts-vite@1.3.2 dev > vite

0:08:23 [vite] (client) Re-optimizing dependencies because vite config has changed ^C papa@salmos:/workspace/tailux/ts/demo$ ls eslint.config.js node_modules package-lock.json public src tsconfig.json vercel.json index.html package.json prettier.config.js README.md tsconfig.app.json tsconfig.node.json vite.config.ts papa@salmos:/workspace/tailux/ts/demo$ npm run build

VITE v7.2.2  ready in 1463 ms
➜  Local:   http://localhost:5173/
➜  Network: use --host to expose
➜  press h + enter to show help

> react-tailux-ts-vite@1.3.2 build > tsc -b && vite build

src/app/pages/dashboards/cms-analytics/PageViews/Statistics.tsx:34:9 – error TS2322: Type ‘Dispatch<SetStateAction<Page>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Page>’.

34 onChange={setSelectedPage} ~~~~

node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
  21     onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
         ~~~~
  The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'

src/app/pages/forms/KYCForm/components/DocumentType.tsx:45:9 – error TS2322: Type ‘DocumentType | null’ is not assignable to type ‘DocumentType | undefined’. Type ‘null’ is not assignable to type ‘DocumentType | undefined’.

45 value={documentTypes.find((doc) => doc.key === value) || null} ~~~

node_modules/@headlessui/react/dist/components/radio-group/radio-group.d.ts:13:5
  13     value?: TType;
         ~~~
  The expected type comes from property 'value' which is declared here on type 'IntrinsicAttributes & CleanProps<"div", "value" | "disabled" | "form" | "defaultValue" | "onChange" | "name" | "by" | RadioGroupPropsWeControl> & OurProps<...> & { ...; } & { ...; } & { ...; }'

src/app/pages/forms/autocomplete/Styled.tsx:32:9 – error TS2322: Type ‘Dispatch<SetStateAction<Person>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Person>’.

32 onChange={setSelected} ~~~~

node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
  21     onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
         ~~~~
  The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'

src/app/pages/forms/autocomplete/StyledError.tsx:33:9 – error TS2322: Type ‘Dispatch<SetStateAction<Person[]>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Person[]>’.

33 onChange={setSelected} ~~~~

node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
  21     onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
         ~~~~
  The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'

src/app/pages/forms/autocomplete/StyledHighlight.tsx:32:9 – error TS2322: Type ‘Dispatch<SetStateAction<Person[]>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Person[]>’.

32 onChange={setSelected} ~~~~

node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
  21     onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
         ~~~~
  The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'

src/app/pages/forms/autocomplete/StyledMultiple.tsx:32:9 – error TS2322: Type ‘Dispatch<SetStateAction<Person[]>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Person[]>’.

32 onChange={setSelected} ~~~~

node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
  21     onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
         ~~~~
  The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'

src/components/shared/table/FilterSelector.tsx:100:7 – error TS2322: Type ‘(list: FilterOption[]) => void’ is not assignable to type ‘(value: (FilterOption | undefined)[]) => void’. Types of parameters ‘list’ and ‘value’ are incompatible. Type ‘(FilterOption | undefined)[]’ is not assignable to type ‘FilterOption[]’. Type ‘FilterOption | undefined’ is not assignable to type ‘FilterOption’. Type ‘undefined’ is not assignable to type ‘FilterOption’.

100 onChange={handleChange} ~~~~

node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
  21     onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
         ~~~~~
  The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & CleanProps<"div", "value" | "invalid" | "multiple" | "disabled" | "form" | "onClose" | "defaultValue" | "onChange" | "name" | "by" | "__demoMode" | "nullable" | "immediate" | "virtual"> & OurProps<...> & { ...; } & { ...; } & { ...; }'

Found 7 errors.

So, can you send me your github username, I will add you in repo… there are latest version

Thank you so much. @alemormez

Invited

Hi,

The tailux admin source files do not run the same as the demo, is there an update that is coming for me to wait and download?

the sidebar menu is not the same, its using the earlier one instead of the one used in the demo. And i prefer the new one.

here is my github @giantiss

Looks you should change your layout, there are we have 2 layout: https://tailux.piniastudio.com/docs/getting-started#layouts

Please change it and clear your ‘localstorage’.

Thanks.

I purchased the theme and installed it, but I don’t see all the menus and examples from the demo. I only see a blank layout.

How can I see the sample tables and other components?

Could you please confirm which folder you ran? demo or starter?

Hi bro, I have purchased React version. Do you have next js version..? If yes i will buy immediately

i want to confirm that does it in react js only?

Hi, this is built with React and include both JavaScript and TypeScript editions. Tailwind is used for styling.

aem37

aem37 Purchased

Amazing work!

For the datatables provided, it would add significant value if you could also add some “view” and “edit” page templates.

Hello, could you please invite me to the github repo? “sippakorn”

Thanks

Hi, invited

Good morning, sir.

I’d like to know if there’s any news about the Next.js version. We would be very grateful if you could give us an approximate date for when this extension/version will be available. We would subsequently be interested in purchasing the extended licence.

We would be very grateful. Keep up the good work!

Best regards

Purchased, please invite me to the repo: @cgcb. Also, your page at https://tailux.piniastudio.com/docs/changelogs has “Invalid Date” for each version making it difficult to understand when releases were made.

Hi, invited, Invalid Date? Are you sure?

Yes. When I visit that URL I see Invalid Date. I have screenshot but can’t post here. Also, do you have a repo for the jsx version? That’s what I’m using. Thank you.

by
by
by
by
by
by

Tell us what you think!

We'd like to ask you a few questions to help improve ThemeForest.

Sure, take me to the survey