tidy-up, removing licenses, relinking

This commit is contained in:
Jen Looper
2020-11-14 15:34:22 -05:00
parent a02eea3f47
commit 2cf8b1ee31
17 changed files with 87 additions and 174 deletions

View File

@@ -1,8 +1,8 @@
# HTML Templates and Routes in a Web App
# Build a Banking App Part 1: HTML Templates and Routes in a Web App
<!-- ![video](video-url) -->
## Pre-Lecture Quiz
## [Pre-lecture quiz](.github/pre-lecture-quiz.md)
[Pre-lecture quiz](/7-bank-project/1-template-route/.github/pre-lecture-quiz.md)
### Introduction
@@ -282,7 +282,9 @@ Now try to use the back and forward buttons of your browsers, and check that the
Add a new template and route for a third page that shows the credits for this app.
## [Post-lecture quiz](.github/post-lecture-quiz.md)
## Post-Lecture Quiz
[Post-lecture quiz](/7-bank-project/1-template-route/.github/post-lecture-quiz.md)
## Review & Self Study
@@ -290,4 +292,4 @@ Routing is one of the surprisingly tricky parts of web development, especially a
## Assignment
[Improve the routing](assignment.md)
[Improve the routing](/7-bank-project/1-template-route/assignment.md)

View File

@@ -1,6 +1,8 @@
# Build a Login and Registration Form
# Build a Banking App Part 2: Build a Login and Registration Form
## [Pre-lecture quiz](.github/pre-lecture-quiz.md)
## Pre-Lecture Quiz
[Pre-lecture quiz](/7-bank-project/2-forms/.github/pre-lecture-quiz.md)
### Introduction
@@ -275,7 +277,9 @@ Here's an example of what the final login page can look like after a bit of styl
![Screenshot of the login page after adding CSS styles](./images/result.png)
## [Post-lecture quiz](.github/post-lecture-quiz.md)
## Post-Lecture Quiz
[Post-lecture quiz](/7-bank-project/2-forms/.github/post-lecture-quiz.md)
## Review & Self Study
@@ -283,4 +287,4 @@ Developers have gotten very creative about their form building efforts, especial
## Assignment
[Style your bank app](assignment.md)
[Style your bank app](/7-bank-project/2-forms/assignment.md)

View File

@@ -1,10 +1,12 @@
# Methods of Fetching and Using Data
# Build a Banking App Part 3: Methods of Fetching and Using Data
## [Pre-lecture quiz](.github/pre-lecture-quiz.md)
## Pre-Lecture Quiz
[Pre-lecture quiz](/7-bank-project/3-data/.github/pre-lecture-quiz.md)
### Introduction
At the core of every web application there's *data*. Data can take many forms, but the end goal here is always to display information to the user. With web apps becoming increasingly interactive and complex, how the user access and interact with information is now a key part of web development.
At the core of every web application there's *data*. Data can take many forms, but its main purpose is always to display information to the user. With web apps becoming increasingly interactive and complex, how the user accesses and interacts with information is now a key part of web development.
In this lesson, we'll see how to fetch data from a server asynchronously, and use this data to display information on a web page without reloading the HTML.
@@ -315,8 +317,10 @@ Here's an example of a styled dashboard page:
![Screenshot of an example result of the dashboard after styling](../images/screen2.png)
## [Post-lecture quiz](.github/post-lecture-quiz.md)
## Post-Lecture Quiz
[Post-lecture quiz](/7-bank-project/3-data/.github/post-lecture-quiz.md)
## Assignment
[Refactor and comment your code](assignment.md)
[Refactor and comment your code](/7-bank-project/3-data/assignment.md)

View File

@@ -1,10 +1,12 @@
# Concepts of State Management
# Build a Banking App Part 4: Concepts of State Management
## [Pre-lecture quiz](.github/pre-lecture-quiz.md)
## Pre-Lecture Quiz
[Pre-lecture quiz](/7-bank-project/4-state-management/.github/pre-lecture-quiz.md)
### Introduction
As a web application grows, it becomes a challenge to keep track of all data flows. Which code gets the data, what page consumes it, where and when does it need to be updated...it's easy to end up with messy code, difficult to maintain. This is especially true when you need to share data among different pages of your app, for example user data. The concept of *state management* has always existed in all kinds of programs, but as web apps keep growing in complexity it's now a key point to think about during development.
As a web application grows, it becomes a challenge to keep track of all data flows. Which code gets the data, what page consumes it, where and when does it need to be updated...it's easy to end up with messy code that's difficult to maintain. This is especially true when you need to share data among different pages of your app, for example user data. The concept of *state management* has always existed in all kinds of programs, but as web apps keep growing in complexity it's now a key point to think about during development.
In this final part, we'll look over the app we built to rethink how the state is managed, allowing support for browser refresh at any point, and persisting data across user sessions.
@@ -266,11 +268,13 @@ Now that we reload the account data every time the dashboard is loaded, do you t
Try working together to change what is saved and loaded from `localStorage` to only include what is absolutely required for the app to work.
## [Post-lecture quiz](.github/post-lecture-quiz.md)
## Post-Lecture Quiz
[Post-lecture quiz](/7-bank-project/4-state-management/.github/post-lecture-quiz.md)
## Assignment
[Implement "Add transaction" dialog](assignment.md)
[Implement "Add transaction" dialog](/7-bank-project/4-state-management/assignment.md)
Here's an example result after completing the assignment: