Skip to content
This repository was archived by the owner on Oct 20, 2026. It is now read-only.
This repository was archived by the owner on Oct 20, 2026. It is now read-only.

Multiple "Site" directory #907

Closed
Closed

Description

@SaumilNagariya

Describe the feature you'd like to request

Hi Team,

I have setup an additional "Site" directory in next commerce - bigcommerce setup:

Root:
_ _site
_ _ _ _tailwind.config.js
_ _site_a
_ _ _ _tailwind.config.js
_ _site_b
_ _ _ _tailwind.config.js

the setup is working fine, but facing one issue regarding "tailwind.config.js" [in terms of UI]
I want to load tailwind.config.js file respective to the "site" directory. Can you please guide me on this or suggest some additional configuration?

Activity

  1. cond0r commented on Dec 6, 2022

    @cond0r
    Contributor

    Hi @SaumilNagariya, you can accomplish that by using Tailwind presets https://tailwindcss.com/docs/presets.

    Since this project is a monorepo, you can look at these two examples of how you create sharable Tailwind presets as a local package, and then you can add that to package.json & tailwind.config.js for each site:
    https://github.com/vercel/turbo/tree/main/examples/with-tailwind
    https://github.com/vercel/examples/tree/main/solutions/microfrontends

  2. leerob commented on Apr 18, 2023

    @leerob
    Contributor

    Hey there! Thank you for your contribution. We have decided to take Next.js Commerce in a new direction and will be closing out current PRs and issues due to this change. Please see this PR for more details: #966

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions