Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It should be safe to delete the CSS folder you don't need in /content #378

Open
Wolfr opened this issue Jun 17, 2021 · 1 comment
Open

Comments

@Wolfr
Copy link
Contributor

Wolfr commented Jun 17, 2021

“In the content area you will find two folders: postcss and sccs. The one you will use depends on your preference in your configuration. It should be safe to delete the folder you don't need.”

Test this.

@Wolfr
Copy link
Contributor Author

Wolfr commented Jul 15, 2021

So when you would use postcss, it is actually not possible to delete the scss folder entirely. You need to keep _br-variables-override.scss because the core folder depends on it.

This file is used to customize the styles in Bedrock's styleguide.

This leads to a situation where someone might be confused by having two types of CSS folders in content:

.
├── data
├── docs
├── fonts
├── icon-font-source
├── icons
├── images
├── js
├── postcss
├── scss
└── templates

Ideally you only want the folder from the CSS technique you use.

I guess by now people might also be confused what a tailwind.config.js is doing in the root of the project when they don't use tailwind at all.

A project scaffolding wizard which generates certain files might be an answer, but that's complex to implement and maintain .

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

No branches or pull requests

1 participant