Skip to content

Commit 23d3738

Browse files
committed
docs(gettingStarted): fill-out Getting Started section more
1 parent 5bb43be commit 23d3738

File tree

5 files changed

+150
-9
lines changed

5 files changed

+150
-9
lines changed

Diff for: docs/01_Getting_Started/01_Prerequisites.md

-9
Original file line numberDiff line numberDiff line change
@@ -21,12 +21,3 @@ Make a new directory, and `cd` into it:
2121
```bash
2222
mkdir myapp && cd $_
2323
```
24-
25-
Run `yo angular-fullstack`, optionally passing an app name:
26-
```bash
27-
yo angular-fullstack
28-
```
29-
30-
You'll then be asked a series of questions regarding options for the generated app. Such things include using JavaScript or TypeScript,
31-
HTML or Pug, Bootstrap, SQL, and so on. If you don't know what to answer for a question, just hitting `ENTER` will use the default options
32-
for that question, and move on to the next one.

Diff for: docs/01_Getting_Started/02_Installation.md

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
## Installation
2+
3+
Run `yo angular-fullstack` (optionally passing an app name):
4+
```bash
5+
yo angular-fullstack
6+
```
7+
8+
You'll then be asked a series of questions regarding options for the generated app. Such things include using JavaScript or TypeScript,
9+
HTML or Pug, Bootstrap, SQL, and so on. If you don't know what to answer for a question, or just want to use our preferred options,
10+
hitting `ENTER` will use the default options for that question, and move on to the next one.
11+
12+
Once you've answered all the questions, a project will be scaffolded for you according to the options you entered. Then, npm dependencies
13+
will automatically be installed. Once that's all complete, you're ready to get started with your app!
14+

Diff for: docs/01_Getting_Started/03_Running_Your_New_App.md

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
## Running Your New App
2+
3+
You can start your new app by running `gulp serve`. This will do some preliminary things like clean out temporary
4+
files, lint your scripts, inject any new CSS files into your main one, apply environment variables, and download
5+
any new TypeScript definitions. It will then start up a new development server, which will kick off a Webpack build.
6+
it uses Browser Sync to facilitate front-end development. Your files will also be watched for changes. Any front-end
7+
changes will kick off another webpack build. Any back-end changes will restart the back-end server, cleaning the
8+
development database and re-seeding it as well.
9+
10+
Once the `serve` tasks are complete, a browser tab should be opened to your new app server.

Diff for: docs/01_Getting_Started/03_Running_the_Generator.md

Whitespace-only changes.

Diff for: docs/01_Getting_Started/04_Project_Overview.md

+126
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,126 @@
1+
## Project Overview
2+
3+
What follows is an overfiew of the files/folders in your newly generated project.
4+
5+
### Project Root
6+
7+
* .babelrc - configuration for [Babel], a JavaScript transpiler
8+
* .editorconfig - config file used to keep conistent file editing across text editors
9+
* .eslintrc - all of the rules applying to the ESLint JavaScript linter
10+
* .travis.yml - a sample configuration file for Travis CI
11+
* .yo-rc.json - a configuration file for the Angular Full-Stack Generator
12+
* gulpfile.babel.js - Gulp task runner file
13+
* karma.conf.js - Karma browser testing configuration
14+
* mocha.conf.js - Mocha test framework configuration
15+
* mocha.global.js - teardown file for Mocha
16+
* package.json - npm manifest, contains information for all project dependencies
17+
* protractor.conf.js - configuration for Protractor e2e test framework
18+
* README.md - a readme file generator based on your options, for your scaffolded project
19+
* spec.js - test file for Webpack used by Karma
20+
* webpack.make.js - main file for Webpack configuration
21+
* The following export the config from `webpack.make.js` for their respective build targets:
22+
* webpack.dev.js
23+
* webpack.test.js
24+
* webpack.build.js
25+
26+
### `client/`
27+
28+
```
29+
│ .eslintrc // eslint config for client files
30+
│ polyfills.js // imports of polyfills
31+
│ _index.html // template for the root HTML file of your app
32+
33+
├───app
34+
│ │ app.config.js // contains app-wide configuration code
35+
│ │ app.constants.js // gets injected with constants from `server/config/environment/shared.js`
36+
│ │ app.{js,ts} // root JavaScript file of your app
37+
│ │ app.{css,scss,stylus,less} // root CSS file of your app
38+
│ │
39+
│ ├───account // pages related to login / signup / user settings
40+
│ │ │ account.routes.js // route information
41+
│ │ │ index.js // account module root
42+
│ │ │
43+
│ │ ├───login
44+
│ │ ├───settings
45+
│ │ └───signup
46+
│ │
47+
│ ├───admin // site admin page
48+
│ │
49+
│ └───main // main component, homepage
50+
51+
├───assets // where static assets are stored
52+
53+
└───components
54+
├───auth
55+
│ auth.module.js // module containing auth components
56+
│ auth.service.js // authentication service
57+
│ interceptor.service.js // intercepts requests and adds tokens if needed. Also redirects 401s to the login page.
58+
│ router.decorator.js // facilitates auth-based routing configuration
59+
│ user.service.js // user resource service
60+
61+
├───footer
62+
63+
├───modal
64+
65+
├───navbar
66+
67+
├───oauth-buttons // buttons for oauth login on signup / login pages
68+
69+
├───socket
70+
│ socket.mock.js // mock service for unit testing
71+
│ socket.service.js // service for Socket IO integration
72+
73+
├───ui-router
74+
│ ui-router.mock.js // mock service for unit testing
75+
76+
└───util // general utility service
77+
```
78+
79+
### `server/`
80+
81+
```
82+
│ .eslintrc // server-specific ESLint config, imports rules from root file
83+
│ app.js // root server module
84+
│ index.js // imports `app.js`. Enables Babel require hook when in development mode.
85+
│ routes.js // imports / config for server endpoints
86+
87+
├───api
88+
│ ├───thing
89+
│ │ index.js // root module
90+
│ │ index.spec.js // root module tests
91+
│ │ thing.controller.js // endpoint logic
92+
│ │ thing.events.js // endpoint events (save, delete, etc) logic
93+
│ │ thing.integration.js // integration tests
94+
│ │ thing.model.js // Mongoose / Sequelize data model
95+
│ │ thing.socket.js // Socket IO logic / config
96+
│ │
97+
│ └───user // API for Users
98+
99+
├───auth
100+
│ │ auth.service.js
101+
│ │ index.js // imports local/oauth auth modules
102+
│ │
103+
│ ├───local // regular auth, signed up directly via your site
104+
│ ├───google // Google OAuth
105+
│ └───<etc...>
106+
107+
└───config
108+
│ express.js // Express server setup
109+
│ local.env.js // ignored by Git
110+
│ local.env.sample.js // sensitive environment variables are stored here, and added at server start. Copy to `local.env.js`.
111+
│ seed.js // re-seeds database with fresh data
112+
│ socketio.js // Socket IO configuration / imports
113+
114+
└───environment
115+
development.js
116+
index.js
117+
production.js
118+
shared.js // config constants shared with the client code
119+
test.js
120+
```
121+
122+
### `e2e/`
123+
124+
End-To-End testing files (use by [Protractor](https://github.com/angular/protractor) with [Mocha](https://github.com/mochajs/mocha))
125+
126+
[Babel]: https://babeljs.io/

0 commit comments

Comments
 (0)