Skip to content

Commit 13a4e4f

Browse files
authored
docs(getting-started): write out the rest of the getting started page
[skip ci]
1 parent 13f20ba commit 13a4e4f

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

Diff for: docs/getting-started/step1-overview.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
[#STUB]
2-
31
# Project Overview
42

53
Now that you've got a Full-Stack Angular project scaffolded, lets go over how everything is structured.
@@ -15,8 +13,10 @@ Now find the `gulpfile.babel.js`. Pretty much everthing you do with your app fro
1513
running different test commands, running your server, building your code for distribution, and on and on.
1614
Let's go over some of the most important Gulp tasks:
1715

18-
* `serve` -
19-
* `build` -
20-
* `test` -
16+
* `gulp serve` - This will build the code for development use, run a dev server, and open up the application in your default browser.
17+
* `gulp build` - This will build the code into the `dist/` folder, which you can then distribute to your production servers.
18+
* `gulp test` - This will run client and server unit + integration tests.
19+
20+
## Webpack
2121

22-
[webpack]
22+
Webpack is a module bundler for front-end web applications. Basically it takes all of your front-end files (JavaScript source + libs, CSS, HTML, etc) and bundles them all up into intelligently laid-out JavaScript bundles. It uses CommonJS to `import`/`export` modules/assets. The takeaway here is that instead of loading your JS files directly in the browser, instead you'll be loading the webpack bundles. Also, instead of everything naively using the global browser scope, you'll need to `import`/`export` anything you'd like to use. We'll look into this in greater detail later.

0 commit comments

Comments
 (0)