Skip to content

Commit b87311b

Browse files
committed
docs(developing): fix images, add link to adding a route
1 parent e5104b9 commit b87311b

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed

docs/content/developing/01_Adding_a_Route.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ angular.element(document)
5151

5252
Now that we've imported our new Angular module and added it to the dependency list of our root Angular module, we should be able to navigate to `http://localhost:3000/foo` and see our new route:
5353

54-
<img src="../images/foo-route.jpg" alt="Foo route screenshot">
54+
<img src="/assets/foo-route.jpg" alt="Foo route screenshot">
5555

5656
It's not a very impressive page right now, but it works.
5757

@@ -89,6 +89,6 @@ export default angular.module('directives.navbar', [])
8989

9090
Easy enough. Now we should see our entry for 'Foo' in our navbar. It should also be highlighted if you're still on the '/foo' route.
9191

92-
<img src="../images/foo-route-navbar.jpg" alt="Foo route screenshot">
92+
<img src="/assets/foo-route-navbar.jpg" alt="Foo route screenshot">
9393

9494
You can read about all the other subgenerators that are available in the [Generators](../Generators) section of the docs.

docs/content/developing/index.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ webpack: bundle is now VALID.
8585
And then our default browser should open up to the app:
8686

8787

88-
<img src="../images/afs-screenshot.png" alt="App Screenshot">
88+
<img src="../assets/afs-screenshot.png" alt="App Screenshot">
8989

9090

9191
Fantastic! We're now up and running with our Full-Stack Angular web application! So what can it do?
@@ -95,7 +95,7 @@ Fantastic! We're now up and running with our Full-Stack Angular web application!
9595
Assuming you scaffolded with a back-end database, you should see some 'features'. If you scaffolded with socket.io, you should see 'x' buttons next to each, and an input box. Try opening two browser windows to the same page side-by-side, and hitting the 'x' on one of the features. You should see the feature get removed on both web pages. Neat! This is because these database object changes are communicated to clients using socket.io.
9696

9797

98-
<img src="../images/socket.io-demo.gif" alt="Socket.io demo screenshot">
98+
<img src="../assets/socket.io-demo.gif" alt="Socket.io demo screenshot">
9999

100100

101101
Neat. Let's see what else we can do.
@@ -117,7 +117,9 @@ You should see inputs for an email address and a password. When running your pro
117117

118118
Go ahead and log in with the admin account, so we can see the extra admin bits too. You should then get sent back to the home page, but should notice that the navbar looks a bit different:
119119

120-
<img src="../images/logged-in.jpg" alt="Logged in as admin screenshot">
120+
<img src="../assets/logged-in.jpg" alt="Logged in as admin screenshot">
121121

122122

123123
First, at the top right, we see a greeting for our username, a cog icon (for user settings), and a logout button. Then, since we're an admin, we see a new 'Admin' state on the navbar. The admin section lists users and allows you to delete them. The user settings page allows you to change your password.
124+
125+
[Next: Adding a Route](01_Adding_a_Route)

0 commit comments

Comments
 (0)