`bower install foundation`和`foundation new MY_PROJECT`有什么区别？

On the foundation github page the recommended way to install foundation is bower install foundation yet in their documentation they suggest using foundation new MY_PROJECT. On the documentation page the first method is only listed under the "using a task runner" section. Both methods give different file structures. Are both ways correct and if so then why do they give different file structures.

在基础github页面上,推荐的安装基础的方法是bower安装基础,但在他们的文档中他们建议使用基础新的MY_PROJECT。在文档页面上,第一种方法仅列在“使用任务运行器”部分下。两种方法都提供不同的文件结构两种方式都是正确的,如果是这样,那么为什么它们提供不同的文件结构

1 个解决方案

#1

I looked a little more into it:

我看了一下:

1. If you type bower install foundation you download the Foundation library as an asset to your existing project. There you have to take care of including the right files, setting up the build pipeline and wiring all up to your project. This is particularly good if you already have an opinion on how projects should be structured and integrated into your production pipeline / continuous integration.

   如果键入bower install foundation,则将Foundation库作为资产下载到现有项目中。在那里,您必须注意包括正确的文件,设置构建管道并连接所有项目。如果您已经就如何构建项目并将其集成到生产管道/持续集成中,那么这一点尤其有用。

2. Say that you want to create an entirely new project and have no starting conditions whatsoever. This project should not be "your project using Foundation" but "a Foundation project" inheriting all the opinions Zurb has on creating projects. If you are up for this road, then foundation new project is the way to go. This sets up all the assets, dependencies and build-chains for you. Actually this setup might even include the foundation bower component you would install otherwise. You will not have to worry about anything, but you will have a lot more to learn if you want to change things.

   假设您想要创建一个全新的项目并且没有任何启动条件。这个项目不应该是“你的项目使用基金会”,而是“基础项目”继承了Zurb在创建项目时的所有意见。如果你想要走这条路,那么基础新项目就是你要走的路。这为您设置了所有资产,依赖关系和构建链。实际上,这种设置甚至可能包括您将安装的基础凉亭组件。你不必担心任何事情,但如果你想改变一些事情,你还需要学习更多东西。