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

Creating New Zurb Foundation Project doesn't use source folder #318

Closed
TC72 opened this issue Feb 17, 2017 · 1 comment
Closed

Creating New Zurb Foundation Project doesn't use source folder #318

TC72 opened this issue Feb 17, 2017 · 1 comment

Comments

@TC72
Copy link

TC72 commented Feb 17, 2017

I’ve used the menu item “Apply Best Defaults for Using Build Folders” but when I use “New Zurb Foundation Project…” I end up with a build folder but no source folder.

I'd expected to see this at the root of my project:
.bowerrc
bower_components
bower.json
config.codekit3
build
source

what I got was:
.bowerrc
CHANGELOG.md
README.md
bower.json
bower_components
build
config.codekit3
css
index.html
js
package.json
scss

I tried to force it by creating a build and source folder first but it removed them when it pulled zurb from git.

You also end up with bower_components and associated file like bower.json automatically added to the build folder.

@bdkjones
Copy link
Owner

Yea, the reason for this is that Zurb Foundation is opinionated about where things go. CodeKit simply clones the Zurb repo and then follows their installation script to get everything wired up correctly. If I altered that, I'd constantly be fighting Zurb when they make changes, etc.

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

No branches or pull requests

2 participants