AP Week Tasks | Ayman

[aymankazi9]

Week 1

Information Pages (FAQ), Login/Signup Template and Backend

• Complete the FAQ page with frontend and backend elements
• [x] Have relevant questions to the topic
• [x] Fit the theme (frontend)
• [ ] Move text to backend through the use of Jinja variables
• [x] Backend File for login
• [x] Storing signup in database
• [x] Templates for both

Tangibles:

• FAQ Page
• Testing backend variables
• Login Template
• Register Template
• Storing in DB

  ---

Week 2

Create Task Completion

• Work to complete the AP CSP portfolio and fulfill all of its requirements
• [x] Create a new task.py file which includes the algorithms I have worked on , adding an interface for a user input, and adding comments to show development
• [x] Work on the Write Up and finish all parts
• [x] Submit Program Code
• [x] Make video displaying program running

  Tangibles

• New task.py used for video and write up

---

Week 3

Information Pages (cont. including Prevention), Feedback page

• [x] Feedback with link to DB
• [x] Prevention Page

Tangibles

• Completed Prevention Page
• Experimenting with backend (classes and functions)
• Hotspot Page
• Feedback Template
• Backend for feedback

---

Week 4

Information Pages (cont. including Causes page), Hotspot Pages, Blueprint Redesign

• [x] Causes Page
• [ ] Hotspot Page also using data
• [ ] Blueprint Redesign (matches theme of site)

  Tangibles

• Completed causes page which fits theme of other info pages

[aymankazi9]

Jigger Tickets

• Issue on Review Column: 1/1
• Card with name, tangibles, comment: 1/1
• Clarity and Quality: 1/1
• Total Score (Confirmed by Navodit Maheshwari): 3/3

[jm1021]

Glad to see the mix of front end and backend work. I don't really like so much stuff on one issue, it is better for me to see a smaller goal and accomplishment. 3/3

[Navodit1603]

Prevention tips look great and I see that you started with backend parts. Keep working on those.

[PragadeeshRaj]

The hardcoding of the prevention page was not a great choice for the frontend, however, it's great to see you moving into an algorithmic approach with the backend and using the model file. I see the small issues you are having with the class implementation, but that's a great goal for you to focus on next week.

[mustafasharaf04]

Looks great. Hopefully later on we can incorporate some front end code as well and make sure to reorganize the blueprint when you get the chance.

[Ali-Saad]

Looks good so far and I really like the progress. As Pragadeesh mentioned, class implementation on a ticket like this (perfected) would be ideal so I think that would be a good goal to work towards.

[Navodit1603]

Great to see the information you have for our newsletter. In these final days lets try to finalize everything. You can work on your blueprints and match the theme of the site. Hotspot page is one of the last things left so we can work together to finish that.

[PragadeeshRaj]

I like to see more pages added to the information pages. It adds another level of informative factor to the website. A suggestion would be to include runtimes for this page in the tangibles. I'm interested to see how you will be redesigning your blueprint, it's definitely and important aspect on this week's horizon.

[mustafasharaf04]

Be sure to finish your Hotspot page as well as your blueprint redesign. You need to make sure that you complete your goals soon.

[Ali-Saad]

The informational pages look great! Runtimes links on the README file would have been ideal but I'm quite proud of your blueprint redesigning as it looks to be a great accomplishment for this week. Mustafa did mention a great point about those hotspots as well.