From daa71db37499715efd810347c981d5cba9368d7a Mon Sep 17 00:00:00 2001 From: EduardSkibidiEdger Date: Tue, 15 Oct 2024 19:37:19 +0300 Subject: [PATCH] test! --- CS/L6.html | 113 +++++++++++------- CS/ProblemSolvingProcess/content.md | 32 +++++ CS/ProblemSolvingProcess/index.html | 126 ++++++++++++-------- CS/ProblemSolvingProcess/test.html | 175 ---------------------------- CS/index.html | 1 + projects.html | 1 + 6 files changed, 183 insertions(+), 265 deletions(-) delete mode 100644 CS/ProblemSolvingProcess/test.html diff --git a/CS/L6.html b/CS/L6.html index ebd5481..5e70b98 100644 --- a/CS/L6.html +++ b/CS/L6.html @@ -5,50 +5,101 @@ Lesson 6 - +
+ +
-

Calculator: Add, Divide by 2, and Check Even/Odd

@@ -60,10 +111,7 @@
-
- -

Number Guessing Game

@@ -73,48 +121,31 @@
- - diff --git a/CS/ProblemSolvingProcess/content.md b/CS/ProblemSolvingProcess/content.md index e69de29..03f2251 100644 --- a/CS/ProblemSolvingProcess/content.md +++ b/CS/ProblemSolvingProcess/content.md @@ -0,0 +1,32 @@ +# Problem Solving Process + +## 1. Define + +**Definition:** Clearly understand and define the problem. Identify the root cause and gather all the necessary information. + +**Example:** +The machine on the assembly line keeps stopping randomly. + +**Define:** +Understand that the issue is the machine’s unexpected stops. Gather data on when and how it happens. + +## 2. Prepare + +**Definition:** Plan potential solutions. Brainstorm ideas, gather resources, and consider possible approaches. + +**Example:** +Brainstorm possible causes like faulty wiring, overheating, or software glitches. Plan to inspect the machine's components and test each hypothesis. + +## 3. Try + +**Definition:** Implement the solution. Test the planned solution in a controlled environment or apply it step by step. + +**Example:** +Test by replacing a faulty component or adjusting software settings. Monitor if the machine stops unexpectedly after the changes. + +## 4. Reflect + +**Definition:** Assess the outcome of the solution. Did it work? What could be improved? Reflect on how effective the solution was. + +**Example:** +After a week of testing, determine whether the machine continues to operate smoothly. If it still malfunctions, revisit the Prepare phase for further investigation. diff --git a/CS/ProblemSolvingProcess/index.html b/CS/ProblemSolvingProcess/index.html index 3c8c0ce..17e1111 100644 --- a/CS/ProblemSolvingProcess/index.html +++ b/CS/ProblemSolvingProcess/index.html @@ -1,7 +1,7 @@ - + Problem Solving Process Poster @@ -32,9 +32,16 @@ box-shadow: 0 0 20px rgba(0, 0, 0, 0.1); border-radius: 10px; padding: 2em; + opacity: 0; + transition: opacity 0.5s ease-in-out; } - h1 { + .poster.visible { + opacity: 1; + } + + /* Styling for dynamically generated content */ + .poster h1 { text-align: center; color: #b657ff; /* Lilac color for header */ margin-bottom: 1.5em; @@ -42,7 +49,7 @@ font-weight: bold; } - h2 { + .poster h2 { color: #a29dfa; /* Softer lilac color */ border-bottom: 2px solid #b657ff; /* Lilac border */ padding-bottom: 0.5em; @@ -50,17 +57,13 @@ font-size: 1.5em; } - p { + .poster p { font-size: 1em; line-height: 1.6; margin-top: 0.5em; color: #e0ceed; /* Light text color */ } - .section { - margin-bottom: 1.5em; - } - .example { background-color: #211d26; /* Dark lilac tone for example box */ padding: 1em; @@ -75,29 +78,29 @@ /* Responsive Typography */ @media (max-width: 768px) { - h1 { + .poster h1 { font-size: 1.8em; } - h2 { + .poster h2 { font-size: 1.3em; } - p { + .poster p { font-size: 0.95em; } } @media (max-width: 480px) { - h1 { + .poster h1 { font-size: 1.5em; } - h2 { + .poster h2 { font-size: 1.2em; } - p { + .poster p { font-size: 0.9em; } @@ -106,43 +109,68 @@ } } + + + -
-

Problem Solving Process

- -
-

1. Define

-

Definition: Clearly understand and define the problem. Identify the root cause and gather all the necessary information.

-
-

Example: The machine on the assembly line keeps stopping randomly.

-

Define: Understand that the issue is the machine’s unexpected stops. Gather data on when and how it happens.

-
-
- -
-

2. Prepare

-

Definition: Plan potential solutions. Brainstorm ideas, gather resources, and consider possible approaches.

-
-

Example: Brainstorm possible causes like faulty wiring, overheating, or software glitches. Plan to inspect the machine's components and test each hypothesis.

-
-
- -
-

3. Try

-

Definition: Implement the solution. Test the planned solution in a controlled environment or apply it step by step.

-
-

Example: Test by replacing a faulty component or adjusting software settings. Monitor if the machine stops unexpectedly after the changes.

-
-
- -
-

4. Reflect

-

Definition: Assess the outcome of the solution. Did it work? What could be improved? Reflect on how effective the solution was.

-
-

Example: After a week of testing, determine whether the machine continues to operate smoothly. If it still malfunctions, revisit the Prepare phase for further investigation.

-
-
+
+
+ + diff --git a/CS/ProblemSolvingProcess/test.html b/CS/ProblemSolvingProcess/test.html deleted file mode 100644 index c16fc14..0000000 --- a/CS/ProblemSolvingProcess/test.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - - - Problem Solving Process Poster - - - - - -
- -
- - - - diff --git a/CS/index.html b/CS/index.html index 1cada20..13964fa 100644 --- a/CS/index.html +++ b/CS/index.html @@ -51,6 +51,7 @@
diff --git a/projects.html b/projects.html index efed3b1..4216f50 100644 --- a/projects.html +++ b/projects.html @@ -52,6 +52,7 @@

  • ./

  • CS/
  • Problem Solving Process
    • +
  • L6