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: 1-getting-started-lessons/1-intro-to-programming-languages/README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -198,6 +198,9 @@ Compare some programming languages. What are some of the unique traits of JavaSc
198
198
199
199
Study a bit on the different languages available to the programmer. Try to write a line in one language, and then rewrite it in two others. What did you learn?
200
200
201
+
201
202
## Assignment
202
203
203
204
[Reading the Docs](assignment.md)
205
+
206
+
> Note: When selecting tools for your assignment, do not choose editors, browsers, or command line tools already listed above.
There are many tools that a web developer may need that are on the [MDN documentation for client-side tooling](https://developer.mozilla.org/docs/Learn/Tools_and_testing/Understanding_client-side_tools/Overview). Select 3 tools not covered in the lesson, explain why a web developer would use it, and search for a tool that falls under this category and share its documentation. Do not use the same tool example on MDN docs.
3
+
There are many tools that a web developer may need that are listed on the [MDN documentation for client-side tooling](https://developer.mozilla.org/docs/Learn/Tools_and_testing/Understanding_client-side_tools/Overview). Select **three tools** that are **not covered in this lesson** (excluding [list specific tools or refer to lesson content]), explain **why** a web developer would use each tool, and find a tool that fits each category. For each, share a link to its official documentation (not the example used on MDN).
4
+
5
+
**Format:**
6
+
- Tool name
7
+
- Why a web developer would use it (2-3 sentences)
8
+
- Link to documentation
9
+
10
+
**Length:**
11
+
- Each explanation should be 2-3 sentences.
6
12
7
13
## Rubric
8
14
9
15
Exemplary | Adequate | Needs Improvement
10
16
--- | --- | -- |
11
-
|Explained why web developer would use tool| Explained how, but not why developer would use tool| Did not mention how or why a developer would use tool |
17
+
Explained why web developer would use tool| Explained how, but not why developer would use tool| Did not mention how or why a developer would use tool |
Copy file name to clipboardExpand all lines: 2-js-basics/1-data-types/assignment.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,10 @@
2
2
3
3
## Instructions
4
4
5
-
Imagine you are building a shopping cart. Write some documentation on the data types that you would need to complete your shopping experience. How did you arrive at your choices?
5
+
Imagine you are building a shopping cart. Write documentation on the data types you would need to complete your shopping experience. For each data type, explain how and why you would use it, and provide an example. The six JavaScript data types are: String, Number, Boolean, Null, Undefined, and Object.
||The six data types are listed and explored in detail, documenting their use|Four datatypes are explored|Two data types are explored|
11
+
Data Types | All six data types are listed, explored in detail, and documented with examples | Four data types are explored with some explanation | Two data types are explored with minimal explanation |
Design and hand-code the HTML structure for a personal blog homepage. This exercise will help you practice semantic HTML, layout planning, and code organization.
2
6
3
7
## Instructions
4
8
5
-
Imagine you are designing, or redesigning, your personal web site. Create a graphical mockup of your site, and then write down the HTML markup you would use to build out the various elements of the site. You can do this on paper, and scan it, or use software of your choice, just make sure to hand-code the HTML markup.
9
+
1.**Design Your Blog Mockup**
10
+
- Sketch a visual mockup of your blog homepage. Include key sections such as header, navigation, main content, sidebar, and footer.
11
+
- You may use paper and scan your sketch, or use digital tools (e.g., Figma, Adobe XD, Canva, or even PowerPoint).
12
+
13
+
2.**Identify HTML Elements**
14
+
- List the HTML elements you plan to use for each section (e.g., `<header>`, `<nav>`, `<main>`, `<article>`, `<aside>`, `<footer>`, `<section>`, `<h1>`–`<h6>`, `<p>`, `<img>`, `<ul>`, `<li>`, `<a>`, etc.).
15
+
16
+
3.**Write the HTML Markup**
17
+
- Hand-code the HTML for your mockup. Focus on semantic structure and best practices.
18
+
- Include at least 10 distinct HTML elements.
19
+
- Add comments to explain your choices and structure.
20
+
21
+
4.**Submit Your Work**
22
+
- Upload your sketch/mockup and your HTML file.
23
+
- Optionally, provide a brief reflection (2–3 sentences) on your design decisions.
|| A blog layout is represented visually with at least 10 elements of markup displayed | A blog layout is represented visually with around 5 elements of markup displayed | A blog layout is represented visually with at most 3 elements of markup displayed |
| Visual Mockup | Clear, detailed mockup with labeled sections and thoughtful layout | Basic mockup with some labeled sections | Minimal or unclear mockup; lacks section labels |
30
+
| HTML Elements | Uses 10+ semantic HTML elements; demonstrates understanding of structure and best practices | Uses 5–9 HTML elements; some semantic structure | Uses fewer than 5 elements; lacks semantic structure |
31
+
| Code Quality | Well-organized, readable code with comments; follows HTML standards | Mostly organized code; few comments | Disorganized code; lacks comments |
32
+
| Reflection | Insightful reflection on design choices and challenges | Basic reflection | No reflection or lacks relevance |
33
+
34
+
## Tips
35
+
36
+
- Use semantic HTML tags for better accessibility and SEO.
37
+
- Organize your code with indentation and comments.
38
+
- Refer to [MDN HTML Elements Reference](https://developer.mozilla.org/en-US/docs/Web/HTML/Element) for guidance.
39
+
- Think about how your layout could be extended or styled in future assignments.
Refactor the terrarium project to use **Flexbox** or **CSS Grid** for layout. Update the HTML and CSS as needed to achieve a modern, responsive design. You do not need to implement draggable elements—focus on layout and styling only.
2
6
3
7
## Instructions
4
8
5
-
Restyle the terrarium using either Flexbox or CSS Grid, and take screenshots to show that you have tested it on several browsers. You might need to change the markup so create a new version of the app with the art in place for your refactor. Don't worry about making the elements draggable; only refactor the HTML and CSS for now.
9
+
1.**Create a new version** of the terrarium app. Update the markup and CSS to use Flexbox or CSS Grid for layout.
10
+
2.**Ensure the art and elements are in place** as in the original version.
11
+
3.**Test your design** in at least two different browsers (e.g., Chrome, Firefox, Edge).
12
+
4.**Take screenshots** of your terrarium in each browser to demonstrate cross-browser compatibility.
| Layout | Fully refactored using Flexbox or CSS Grid; visually appealing and responsive | Some elements refactored; partial use of Flexbox or Grid | Little or no use of Flexbox or Grid; layout unchanged |
20
+
| Cross-Browser | Screenshots provided for multiple browsers; consistent appearance | Screenshots for one browser; minor inconsistencies | No screenshots or major inconsistencies |
21
+
| Code Quality | Clean, well-organized HTML/CSS; clear comments | Some organization; few comments | Disorganized code; lacks comments |
22
+
23
+
## Tips
24
+
25
+
- Review [Flexbox](https://css-tricks.com/snippets/css/a-guide-to-flexbox/) and [CSS Grid](https://css-tricks.com/snippets/css/complete-guide-grid/) guides.
26
+
- Use browser developer tools to test responsiveness.
0 commit comments