Skip to content

Commit 9e61f27

Browse files
DanielRosa74DanielRosa74
authored
feat(curriculum): add Block 18 of the B1 stage of the English Curriculum (freeCodeCamp#59670)
1 parent eeeeb03 commit 9e61f27

File tree

130 files changed

+13313
-24
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

130 files changed

+13313
-24
lines changed

‎curriculum/challenges/_meta/learn-about-adverbial-phrases/meta.json‎

Lines changed: 515 additions & 3 deletions
Large diffs are not rendered by default.

‎curriculum/challenges/english/24-b1-english-for-developers/learn-about-adverbial-phrases/6660a229268f4469af6af407.md‎

Lines changed: 177 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
id: 6660a229268f4469af6af407
3-
title: "Dialogue 1: I'm Tom"
3+
title: "Dialogue 1: Optimizing Daily Huddle Meetings"
44
challengeType: 21
5-
dashedName: dialogue-1-im-tom
5+
dashedName: dialogue-1-optimizing-daily-huddle-meetings
66
---
77

88
# --description--
@@ -11,47 +11,203 @@ Watch the video below to understand the context of the upcoming lessons.
1111

1212
# --assignment--
1313

14-
Watch the video
14+
Watch the video.
1515

1616
# --scene--
1717

1818
```json
1919
{
2020
"setup": {
21-
"background": "chaos.png",
21+
"background": "company2-boardroom.png",
2222
"characters": [
2323
{
24-
"character": "David",
25-
"position": {"x":50,"y":80,"z":8},
26-
"opacity": 0
24+
"character": "Bob",
25+
"position": { "x": -25, "y": 0, "z": 1 }
26+
},
27+
{
28+
"character": "Sarah",
29+
"position": { "x": 125, "y": 0, "z": 1 }
2730
}
2831
],
2932
"audio": {
30-
"filename": "1.1-1.mp3",
31-
"startTime": 1,
32-
"startTimestamp": 5.7,
33-
"finishTimestamp": 6.48
34-
}
33+
"filename": "B1_18-1.mp3",
34+
"startTime": 1
35+
},
36+
"alwaysShowDialogue": true
3537
},
3638
"commands": [
3739
{
38-
"character": "David",
39-
"opacity": 1,
40+
"character": "Bob",
41+
"position": { "x": 25, "y": 0, "z": 1 },
4042
"startTime": 0
4143
},
4244
{
43-
"character": "David",
45+
"character": "Sarah",
46+
"position": { "x": 70, "y": 0, "z": 1 },
47+
"startTime": 0.5
48+
},
49+
{
50+
"character": "Bob",
4451
"startTime": 1,
45-
"finishTime": 0.78,
52+
"finishTime": 7.16,
53+
"dialogue": {
54+
"text": "Today, I want to focus on optimizing our daily huddle meetings to ensure we're using our time effectively.",
55+
"align": "left"
56+
}
57+
},
58+
{
59+
"character": "Bob",
60+
"startTime": 7.66,
61+
"finishTime": 11.24,
62+
"dialogue": {
63+
"text": "First off, let's discuss the frequency of our updates.",
64+
"align": "left"
65+
}
66+
},
67+
{
68+
"character": "Bob",
69+
"startTime": 11.92,
70+
"finishTime": 16.2,
71+
"dialogue": {
72+
"text": "Sarah, can you tell me how often the team currently discusses back-end development?",
73+
"align": "left"
74+
}
75+
},
76+
{
77+
"character": "Sarah",
78+
"startTime": 17.1,
79+
"finishTime": 20,
80+
"dialogue": {
81+
"text": "Currently we meet every morning to review progress and issues.",
82+
"align": "right"
83+
}
84+
},
85+
{
86+
"character": "Sarah",
87+
"startTime": 20.32,
88+
"finishTime": 24.62,
89+
"dialogue": {
90+
"text": "But to be honest, we often end up talking about details that haven't changed from the day before.",
91+
"align": "right"
92+
}
93+
},
94+
{
95+
"character": "Bob",
96+
"startTime": 25.36,
97+
"finishTime": 28.76,
98+
"dialogue": {
99+
"text": "That's a valid concern. Let's think about reducing redundancy.",
100+
"align": "left"
101+
}
102+
},
103+
{
104+
"character": "Bob",
105+
"startTime": 28.76,
106+
"finishTime": 34.26,
107+
"dialogue": {
108+
"text": "How about we switch to biweekly detailed updates unless there's a significant development?",
109+
"align": "left"
110+
}
111+
},
112+
{
113+
"character": "Bob",
114+
"startTime": 34.72,
115+
"finishTime": 37.76,
116+
"dialogue": {
117+
"text": "For daily meetings, a quick status check should be enough.",
118+
"align": "left"
119+
}
120+
},
121+
{
122+
"character": "Sarah",
123+
"startTime": 38.42,
124+
"finishTime": 40.14,
125+
"dialogue": {
126+
"text": "That sounds like a good approach to me.",
127+
"align": "right"
128+
}
129+
},
130+
{
131+
"character": "Sarah",
132+
"startTime": 40.3,
133+
"finishTime": 45.1,
134+
"dialogue": {
135+
"text": "Limiting our full team updates to twice a week, we can concentrate on changes or urgent issues.",
136+
"align": "right"
137+
}
138+
},
139+
{
140+
"character": "Sarah",
141+
"startTime": 45.62,
142+
"finishTime": 50.14,
143+
"dialogue": {
144+
"text": "We might also consider having weekly updates for part of the project where changes are less frequent.",
145+
"align": "right"
146+
}
147+
},
148+
{
149+
"character": "Bob",
150+
"startTime": 50.86,
151+
"finishTime": 55.64,
152+
"dialogue": {
153+
"text": "I like that approach. You know what? We should set specific times for these updates.",
154+
"align": "left"
155+
}
156+
},
157+
{
158+
"character": "Bob",
159+
"startTime": 56,
160+
"finishTime": 62.14,
46161
"dialogue": {
47-
"text": "I'm Tom.",
48-
"align": "center"
162+
"text": "How about scheduling the detailed biweekly meetings for Tuesdays and Thursdays at 9 a.m.?",
163+
"align": "left"
49164
}
50165
},
51166
{
52-
"character": "Tom",
53-
"opacity": 0,
54-
"startTime": 1.28
167+
"character": "Sarah",
168+
"startTime": 62.14,
169+
"finishTime": 67.58,
170+
"dialogue": {
171+
"text": "That works perfectly. I'll keep track of how these changes impact our workflow and compile a report by the end of the month.",
172+
"align": "right"
173+
}
174+
},
175+
{
176+
"character": "Bob",
177+
"startTime": 68.18,
178+
"finishTime": 72.08,
179+
"dialogue": {
180+
"text": "Excellent, Sarah. We'll review your report and feedback from the team",
181+
"align": "left"
182+
}
183+
},
184+
{
185+
"character": "Bob",
186+
"startTime": 72.08,
187+
"finishTime": 77.1,
188+
"dialogue": {
189+
"text": "to see if these adjustments meet our needs or if further modifications are necessary.",
190+
"align": "left"
191+
}
192+
},
193+
{
194+
"character": "Bob",
195+
"startTime": 77.66,
196+
"finishTime": 81.14,
197+
"dialogue": {
198+
"text": "It's crucial that our meetings are as productive as possible.",
199+
"align": "left"
200+
}
201+
},
202+
{
203+
"character": "Sarah",
204+
"position": { "x": 125, "y": 0, "z": 1 },
205+
"startTime": 81.64
206+
},
207+
{
208+
"character": "Bob",
209+
"position": { "x": -25, "y": 0, "z": 1 },
210+
"startTime": 82.14
55211
}
56212
]
57213
}

‎curriculum/challenges/english/24-b1-english-for-developers/learn-about-adverbial-phrases/67f8317b94735744f65b1599.md‎

Lines changed: 103 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,103 @@
1+
---
2+
id: 67f8317b94735744f65b1599
3+
title: Task 1
4+
challengeType: 22
5+
dashedName: task-1
6+
---
7+
8+
<!-- (Audio) Bob: Today, I want to focus on optimizing our daily huddle meetings to ensure we're using our time effectively. -->
9+
10+
# --instructions--
11+
12+
Listen to the audio and complete the sentence below.
13+
14+
# --fillInTheBlank--
15+
16+
## --sentence--
17+
18+
`Today, I want to focus on optimizing our daily BLANK meetings to ensure we're using our time BLANK.`
19+
20+
## --blanks--
21+
22+
`huddle`
23+
24+
### --feedback--
25+
26+
This is used to describe a short, informal meeting, especially in a team. It's often used in sports and business.
27+
28+
---
29+
30+
`effectively`
31+
32+
### --feedback--
33+
34+
This means in a way that gets good results.
35+
36+
# --explanation--
37+
38+
`Huddle` means a quick and focused group meeting, often used to align on tasks or goals. For example:
39+
40+
`Let's have a quick huddle before the client call.` – The team is planning to meet briefly to coordinate before talking to a client.
41+
42+
`Effectively` is an adverb that means doing something in a way that works well or gets good results. It differs from `effective`, which is an adjective and describes something that produces the desired result. For example:
43+
44+
- `The team worked together effectively to complete the project.` – This shows the team performed in a good and organized way. It shows how the team worked.
45+
46+
- `That was an effective strategy for reducing bugs.` – The strategy worked well to reduce bugs. `Effective` qualifies a thing (in this case, the `strategy`), not the action and how it was performed.
47+
48+
# --scene--
49+
50+
```json
51+
{
52+
"setup": {
53+
"background": "company2-boardroom.png",
54+
"characters": [
55+
{
56+
"character": "Bob",
57+
"position": {
58+
"x": 50,
59+
"y": 15,
60+
"z": 1.2
61+
},
62+
"opacity": 0
63+
}
64+
],
65+
"audio": {
66+
"filename": "B1_18-1.mp3",
67+
"startTime": 1,
68+
"startTimestamp": 0,
69+
"finishTimestamp": 6.16
70+
}
71+
},
72+
"commands": [
73+
{
74+
"character": "Bob",
75+
"opacity": 1,
76+
"startTime": 0
77+
},
78+
{
79+
"character": "Bob",
80+
"startTime": 1,
81+
"finishTime": 4.94,
82+
"dialogue": {
83+
"text": "Today, I want to focus on optimizing our daily huddle meetings",
84+
"align": "center"
85+
}
86+
},
87+
{
88+
"character": "Bob",
89+
"startTime": 4.94,
90+
"finishTime": 7.16,
91+
"dialogue": {
92+
"text": "to ensure we're using our time effectively.",
93+
"align": "center"
94+
}
95+
},
96+
{
97+
"character": "Bob",
98+
"opacity": 0,
99+
"startTime": 7.66
100+
}
101+
]
102+
}
103+
```

0 commit comments

Comments
 (0)