You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: contributing/proposals/js-node-restructure.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,13 +51,13 @@ This is schemas for current module structures. I will use the same **color-codin
51
51
52
52
Introduce small reusable logic/function tasks already in the final week (e.g., calculating prices, transforming arrays) and encourage saving the code — these will be reused in API or frontend in later modules.
53
53
54
-
### 2. Module: Web Architecture 101
54
+
### 2. Module: Intro to Web Architecture
55
55
56
56
**Duration**: 1 week\
57
57
**Purpose**: Introduce shared concepts between frontend and backend. Creates a unified mental model before Introductions for specialisations and removes duplicates from modules (like API explanations).\
58
58
**Note**: It, probably, will require some new material there (we didn’t have architecture before), but we can always just stick to the topics that was introduced before in old modules.
59
59
60
-
#### Topics for Web Architecture 101[not limited to]
60
+
#### Topics for Intro to Web Architecture [not limited to]
61
61
62
62
- Client vs Server
63
63
- What is Backend?
@@ -74,7 +74,7 @@ Introduce small reusable logic/function tasks already in the final week (e.g., c
74
74
75
75
**Duration**: 1 week\
76
76
**Purpose**: Provide a hands-on primer to backend development. Enables learners to build a basic working backend (simple CRUD server or even less).\
77
-
**Reasoning**: Placing backend first in hands-on development allows learners to apply their JavaScript fundamentals while reinforcing their understanding of APIs introduced in Web Architecture 101. This progression is both natural and confidence-building: learners already know how to write logic, and now they can wrap it in endpoints (basically, another level of functions). Starting here also clarifies the API before they consume it from the frontend side.
77
+
**Reasoning**: Placing backend first in hands-on development allows learners to apply their JavaScript fundamentals while reinforcing their understanding of APIs introduced in Intro to Web Architecture. This progression is both natural and confidence-building: learners already know how to write logic, and now they can wrap it in endpoints (basically, another level of functions). Starting here also clarifies the API before they consume it from the frontend side.
78
78
79
79
#### Topics for Introduction to Backend
80
80
@@ -173,6 +173,6 @@ Introduce small reusable logic/function tasks already in the final week (e.g., c
173
173
174
174
_Option 1_: It might be natural to introduce separate files in «Introduction to Backend», and then mention in «Introduction to Frontend» how it is solved there.
175
175
176
-
_Option 2_: Introduce idea of structuring files (and import/export) on «Web Architecture 101» session.
176
+
_Option 2_: Introduce idea of structuring files (and import/export) on «Introduction to Web Architecture» session.
177
177
178
178
_Option 3_: Not to give this concept in Foundation, because it seems like it can be done in one file, and later they will have to have separate files in React / Node anyway.
Copy file name to clipboardExpand all lines: courses/foundation/intro-to-web-architecture/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Web Architecture 101
1
+
# Intro to Web Architecture
2
2
3
3
The purpose of this module is to provide a mental model of how web sites work, some of the key terminology and how these concepts relating to the coming modules on the course.
Copy file name to clipboardExpand all lines: courses/foundation/intro-to-web-architecture/preparation.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
5
5
Before the session, please read/watch these materials to get familiar with the basic concepts:
6
6
7
-
-[Web Architecture 101](https://medium.com/storyblocks-engineering/web-architecture-101-a3224e126947) - Comprehensive introduction to web architecture fundamentals
7
+
-[Intro to Web Architecture](https://medium.com/storyblocks-engineering/intro-to-web-architecture-a3224e126947) - Comprehensive introduction to web architecture fundamentals
8
8
-[Everything You Need to Know to Become a Junior Web Developer](https://medium.com/geeks-for-tech/everything-you-need-to-know-to-become-a-junior-web-developer-7ff429df477) - Explains client-server model and roles
9
9
-[Client server model](https://www.youtube.com/watch?v=L5BlpPU_muY) (6 min)
10
10
-[The structure of a web application](https://www.freecodecamp.org/news/how-the-web-works-part-ii-client-server-model-the-structure-of-a-web-application-735b4b6d76e3/) - Read up until the "That's all folks! (Well, sorta…)" part
0 commit comments