Skip to content

Commit cb70fce

Browse files
Merge branch 'code-differently:main' into feat/lesson_26
2 parents 90a841d + 38a5d4e commit cb70fce

File tree

398 files changed

+59089
-9
lines changed

Some content is hidden

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

398 files changed

+59089
-9
lines changed

capstone/README.md

Lines changed: 116 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,116 @@
1+
# Capstone Project
2+
3+
For the next two weeks, you and your team will ideate and implement a working software system. You will have the opportunity to apply the skills that you have learned to solve an interesting problem or contribute a meaningful tool that improves our lives.
4+
5+
### Changelog
6+
- 4/24 @anthonydmays Published initial version
7+
8+
### Technical Requirements
9+
10+
Your project submission must include the following elements:
11+
12+
* All work must be submitted in your team's assigned GitHub repository. Your team must track issues, bugs, pull requests, and features. See [Lesson 05][lesson-05] for a refresh.
13+
* Each team member must contribute *at least two* submitted pull requests containing working code and tests. See [Lesson 15][lesson-15] for a refresh.
14+
* Write unit tests achieving 80% code coverage (using JaCoCo for Java or Jest for Typescript).
15+
* Must have a working front-end that interacts with a back-end web service to retrieve and persist data.
16+
* Your app must be publicly accessible. It is recommended that you use [Vercel](https://vercel.com) or [Fly.io](https://fly.io) to deploy your apps.
17+
* The system must incorporate one third-party API.
18+
* Your repo must include a README with the following elements:
19+
* The team
20+
* Screenshot
21+
* A description of the app
22+
* Demo link
23+
* Installation instructions
24+
* Known issues
25+
* Roadmap features
26+
* Credits
27+
* It is **HIGHLY** recommended that you maintain a clean `Main` branch and only merge changes via pull requests (we've been using squashed merges for the main repo to simplify commit history). Don't forget to use [Conventional Commits][conventional-commits-link].
28+
29+
### Important Milestones
30+
31+
To ensure the timely completion of your project, you will need to complete the following milestone tasks.
32+
33+
<table>
34+
<thead>
35+
<th>Milestone</th>
36+
<th>Date</th>
37+
</thead>
38+
<tbody>
39+
<tr>
40+
<td>Submit user stories to your repo as GitHub issues</td>
41+
<td>Thurs, May 8</td>
42+
</tr>
43+
<tr>
44+
<td>
45+
Obtain project sign-off from instructor/TAs<br>
46+
<a href="https://calendar.google.com/calendar/u/0/appointments/schedules/AcZssZ1dD0ruj64FcykMfPBo7qQaV6AqZ58O7ON8Z3ld-xwNEbFmy0JGyLuwIwxJZjoGoEuz1U9bRZqu">
47+
Schedule a review meeting here
48+
</a>
49+
</td>
50+
<td>Fri, May 9</td>
51+
</tr>
52+
<tr>
53+
<td>Hold Sprint planning meeting</td>
54+
<td>Mon, May 12</td>
55+
</tr>
56+
<tr>
57+
<td>Begin implementing your designs</td>
58+
<td>Mon, May 12</td>
59+
</tr>
60+
<tr>
61+
<td>Update your meeting notes document</td>
62+
<td>Daily</td>
63+
</tr>
64+
<tr>
65+
<td>
66+
Practice presentation sessions
67+
</td>
68+
<td>Wed-Thurs, May 21-22</td>
69+
</tr>
70+
<tr>
71+
<td>Presentations due</td>
72+
<td>Thurs, May 22, EOD</td>
73+
</tr>
74+
<tr>
75+
<td>Final presentations</td>
76+
<td>Fri, May 23</td>
77+
</tr>
78+
</tbody>
79+
</table>
80+
81+
### Helpful Resources
82+
83+
Here are some links to tools and templates that can help you work together effectively.
84+
85+
* [TODO App (fullstack NextJS app in TypeScript)](/lib/javascript/fullstack_demo)
86+
* [TODO App (fullstack React + Java Spring app in TypeScript/Java)](/lib/java/fullstack_demo)
87+
* [v0 (chatbot for generating UI and web applications)](https://v0.dev)
88+
* [A Short Guide to Effective Daily Standups (Nave)](https://getnave.com/blog/short-guide-daily-standups/)
89+
* [Team Meeting Notes template (Google Docs)](https://docs.google.com/document/d/1rL-Zm2w0hABuGkIMSPzmXcJHDQxmIeA-mlipt8kDA9E/edit)
90+
* [Crafting Effective User Stories: A Guide to Good and Bad Versions (Visual Paradigm)](https://guides.visual-paradigm.com/crafting-effective-user-stories-a-guide-to-good-and-bad-versions/)
91+
* [Third-party APIs (MDN)](https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Client-side_web_APIs/Third_party_APIs)
92+
* [GitHub Flow (GitHub.com)](https://docs.github.com/en/get-started/using-github/github-flow)
93+
* The Software Engineer's Guidebook, Chapter 10, "Tools of the Productive Software Engineer."
94+
95+
### Presentation Guidelines
96+
97+
For your presentation, you will be given up to 20 minutes to feature your project. Each person on the team should have a speaking role. Here's what your presentation will contain:
98+
99+
1. Up to four slides of content, then a live demo walkthrough.
100+
2. Your presentation should cover the following items, in order:
101+
- [ ] Introduce team members and their roles
102+
- [ ] State the problem your attempting to solve
103+
- [ ] State how your app is designed to solve the problem
104+
- [ ] Show your demo
105+
- [ ] Discuss how you'd like to enhance in the future
106+
- [ ] Lastly, talk through technical challenges and features.
107+
3. You will be given 5 minutes for Q&A and take questions from the audience.
108+
109+
### Academic Integrity
110+
111+
Please refer to the [Academic Integrity][academic-integrity-link] section of the syllabus regarding the use of third-party code and resources that you have used for your project. Give credit to where credit is due!
112+
113+
[conventional-commits-link]: https://www.conventionalcommits.org/en/v1.0.0/
114+
[academic-integrity-link]: /syllabus/README.md#academic-integrity
115+
[lesson-05]: /lesson_05/README.md
116+
[lesson-15]: /lesson_15/README.md

lesson_17/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Your task for this assignment is add enhancements to an ATM simulator. The [Bank
2626
### Functional Requirements
2727

2828
* We want to support a `SavingsAccount` that works just like the `CheckingAccount`, but doesn't allow you to write checks against the account.
29-
* We want the `BankAtm` class to support the concept of a `BusinessCheckingAccount`. A business account requires that at least one of the owning accounts is a business.
29+
* We want the `BankAtm` class to support the concept of a `BusinessCheckingAccount`. A business account requires that at least one of the owners is a business.
3030
* In addition to supporting checks and cash, we also want to support the concept of another monetary instrument called a `MoneyOrder`. Unlike a `Check`, a `MoneyOrder` withdraws funds from a source account immediately on creation for the purposes of this simulation..
3131
* For traceability, all of the transactions in the `BankAtm` class should logged. Create an `AuditLog` class that keeps a record of all debits and credits to any account and integrate it with the `BankAtm` class.
3232
* ~~For the `depositFunds` method that accepts a cash amount, we'd like the ability to deposit funds in a variety of currencies. Add a parameter that accepts a currency type and a new object that encapsulates the currency converter logic for converting a cash amount to the account currency type.~~
Lines changed: 214 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,214 @@
1+
/* Import Google Fonts */
2+
@import url('https://fonts.googleapis.com/css2?family=Montserrat:wght@700&family=Poppins:wght@400;600&display=swap');
3+
4+
/* Global Styles */
5+
body {
6+
margin: 0;
7+
padding: 0;
8+
font-family: 'Poppins', sans-serif;
9+
background-color: white;
10+
color: #000;
11+
font-size: 90px;
12+
}
13+
14+
/* Header */
15+
.header-top-menu li {
16+
list-style: none;
17+
margin: 0;
18+
padding: 0;
19+
}
20+
21+
.header-top-menu li a {
22+
position: relative;
23+
text-decoration: none;
24+
padding: 10px 20px;
25+
font-size: 16px;
26+
font-weight: 600;
27+
font-family: 'Poppins';
28+
color: #3c3c3c;
29+
30+
}
31+
32+
.header-top-menu li a::after {
33+
content: '';
34+
position: absolute;
35+
left: 0;
36+
bottom: 0;
37+
height: 2px;
38+
width: 0;
39+
background-color: #f39e61;
40+
transition: width 0.3s ease;
41+
}
42+
43+
.header-top-menu li a:hover::after {
44+
width: 100%;
45+
}
46+
.header {
47+
display: flex;
48+
justify-content: space-between;
49+
align-items: center;
50+
padding: 20px 40px;
51+
background-color: white;
52+
color: #000;
53+
}
54+
55+
.header-logo img {
56+
height: 300px;
57+
}
58+
59+
.header-top-menu {
60+
list-style: none;
61+
display: flex;
62+
gap: 30px;
63+
margin: 0;
64+
padding: 0;
65+
}
66+
.header-top-menu li {
67+
list-style: none;
68+
margin: 0;
69+
padding: 0;
70+
}
71+
72+
.header-top-menu li a {
73+
position: relative;
74+
text-decoration: none;
75+
padding: 10px 20px;
76+
font-size: 16px;
77+
font-weight: 600;
78+
font-family: 'Poppins';
79+
color: #3c3c3c;
80+
81+
}
82+
83+
.header-top-menu li a::after {
84+
content: '';
85+
position: absolute;
86+
left: 0;
87+
bottom: 0;
88+
height: 2px;
89+
width: 0;
90+
background-color: #f39e61;
91+
transition: width 0.3s ease;
92+
}
93+
94+
.header-top-menu li a:hover::after {
95+
width: 100%;
96+
}
97+
.header-top-menu li a {
98+
text-decoration: none;
99+
color: #ffffff;
100+
font-weight: 600;
101+
transition: color 0.3s;
102+
}
103+
104+
.header-top-menu li a:hover {
105+
color: #f39e61;
106+
}
107+
108+
.header-cta .sign-up-button {
109+
background-color: hsl(24, 98%, 47%);
110+
color: #ffffff;
111+
padding: 10px 20px;
112+
text-decoration: none;
113+
border-radius: 5px;
114+
font-weight: 600;
115+
transition: background-color 0.3s;
116+
}
117+
.header-cta .sign-up-button {
118+
background-color: #f47d26;
119+
color: white;
120+
padding: 0.5rem 1rem;
121+
border-radius: 6px;
122+
text-decoration: none;
123+
}
124+
.header-cta .sign-up-button:hover {
125+
background-color: hsl(24, 98%, 47%);
126+
}
127+
128+
/* Hero Section */
129+
.hero-section {
130+
background: url('hero.jpg') center/cover no-repeat;
131+
color: white;
132+
padding: 4rem 2rem;
133+
position: relative;
134+
min-height: 60vh;
135+
padding-left: 0;
136+
137+
}
138+
139+
.hero-overlay {
140+
position: absolute;
141+
top: 0;
142+
left: 0;
143+
right: 0;
144+
bottom: 0;
145+
background-color: rgba(0, 0, 0, 0.5);
146+
}
147+
148+
.hero-content {
149+
position: relative;
150+
z-index: 1;
151+
max-width: 800px;
152+
}
153+
154+
.hero-title {
155+
font-size: 2.5rem;
156+
margin-bottom: 1rem;
157+
}
158+
159+
.highlight {
160+
color: #f47d26;
161+
}
162+
163+
.hero-text {
164+
font-size: 20px;
165+
font-family: 'poppins';
166+
background-color: #243e90;
167+
padding-top: 3%;
168+
padding-bottom: 3%;
169+
padding-right: 8%;
170+
padding-left: 8%;
171+
}
172+
173+
/* Programs Section */
174+
.programs-section ul.programs {
175+
width: 60%;
176+
text-decoration: none;
177+
color: #3c3c3c;
178+
font-family: "Montserrat";
179+
font-size: 18px;
180+
font-weight: 600;
181+
font-family: "Poppins";
182+
display: grid;
183+
grid-template-columns: repeat(2, 1fr);
184+
gap: 1.5rem;
185+
}
186+
187+
.programs-section ul li {
188+
list-style: none;
189+
margin: 0;
190+
padding: 0;
191+
display: flex;
192+
flex-wrap: wrap;
193+
align-items: center;
194+
width: 50%;
195+
color: #a9a9a9;
196+
font-weight: 100;
197+
}.program h3 {
198+
font-size: 22px;
199+
font-weight: 900;
200+
color: #3c3c3c;
201+
padding: 0 20px;
202+
}
203+
204+
/* Footer */
205+
.footer {
206+
background-color: #111111;
207+
text-align: center;
208+
padding: 20px;
209+
font-size: 14px;
210+
background-color: white;
211+
color: #000;
212+
font-size: 25px;
213+
}
214+

lesson_22/JBey-CD-Clone/hero.jpg

329 KB
Loading

0 commit comments

Comments
 (0)