Skip to content

TEAMNOTES.MD

Latest commit

 

History

History
61 lines (48 loc) · 4.18 KB

TEAMNOTES.MD

File metadata and controls

61 lines (48 loc) · 4.18 KB

# In-class assignments

10/19/2021 - Questions/Answers

  1. What did you learn from Chuck's example? - We learned that utilizing the render function will improve our code. We also learned that we could use vh and vw variables to avoid fixed solutions.
  2. What approaches can you leverage from his example to enhacne your teams elements? - CSS styles and responsive/proportions design
  3. How could you take his approach and envision a more flexible version? - Slot within a slot and making it more modular as stated by the professor.
  4. What are your next steps? - Get together and align our sections of code in order to fully develop the icons, body, and headers necessary to design the cards. From there we will break off and continue on our own after the parameters are set.

10/5/2021 - Questions/Answers

  1. Characteristics: Colored Banner, Icon, Header/Subheader, Content Body,
  2. Design Considerations: Flexibility of card design for reusability, font-size, card size, heading overflow spillage, color, responsiveness
  3. Accessibility Concerns: Readability, Color-Blindness, Having correct tagging/titles for blind accessability/Proper labeling, Contrast, Being able to access HTML content separately through tab, Typography hierarchy/heading order, be able to have test translated/ i18n(internationalization)
  4. Security Concerns: people's ability to modify content, icon is actually svg and we need to be able to load svg
  5. Card States: Hover, Disabled(not necessarily needed), Inverted, Click (click to show content), Focus(if there's like a link)
  6. What's it Called: pjc-card
  7. Where to Account for Flexible Content: Text areas (depending on how much text), card size
  8. Additional Resuable Atoms [4]: Icon, Body, Title, Banner 8a. What to Call Each: pjc-icon, pjc-body, pjc-title, pjc-head,

#In-class Participation 10/14/2021 Our groups all have very similar elements (if not the exact same) that we have broken the learning cards into [icon, body, banner, scaffolding]. We all discussed how we are planning on taking pieces and molding from the template that was given to us in class. Additionally we all chose to separate work by components so each individual team member took a component to work on to spred the workload. We are all very early on in the process so we still have a lot of work to complete, but our next steps are to implement simple colors and work towards Sunday check-in.

Team notes

This is for maintaining communication about your team's working meetings to "ship" the project.

Meeting notes

These are notes to be maintained PER date that you meet. What you did and what the next steps are

Meeting Date

What we did:

What we'll do next

Status check ins

These are dedicated status check-ins as this is a multi-week project

Check-in 1

  • Group met over the weekend forgot to update teamnotes
  • Names (referenced from above except for last part) : pjc-icon, pjc-body, pjc-title, pjc-scaff
  • planning to distribute work evenly, researching more about html slotted part Elements/Key Considerations/Properties/etc.
  • pjc-icon: svg icon, color, size, must consider reusability
  • pjc-body: styling and flexibility
  • pjc-title: (this is the banner part) flexibility for text, font, color, spacing
  • pjc-scaff: (entire card including banner and body) size

Check-in 2

  • The group is individually splitting up the work with Liam working on the icon element, Liz working on the banner element, and Julian working on the body element.
  • We're having issues with pushing our code to github for some reason but we can't figure out what's going wrong. It's something with husky but we aren't familiar with it so we've been struggling trying to put our code together.
  • Next steps are looking towards troubleshooting with husky and finishing up bringing our pieces together.

Check-in 3

  • Fixed (or at least temporarily fixed) merging, committing, pushing, and pulling errors that we had.
  • Liam made progress on card scaffolding and body.
  • Liz made progress on the banner/header.
  • Working on being more familiar with github, and working around husky related issues.

Check-in 4

  • Group went to office hours on Friday and we finished most of the front-end work. All that is left is the storybook and tests.