Introduction

Before we dive into how my group will deal with this web-component I want to shed some light on the subject so that any reader can understand the basics that go into creating it.

1.) Characteristics

Simply put what does this web-component have to it? Things like color, size, text, icons, placement, etc... anything that describes the component and gives it meaning.

2.) Accessibility

Can a regular use it? How about someone who is color-blind? What about someone who is blind? Can you use the keyboard to navigate the page? When it comes to creating something you have to consider anyone who might come across it.

3.) Security Concerns

This is more back end but you cannot have your webpage being manipulated by anyone online. You want to make sure that icons are secure and data related to the page are secure. How can this be done?

4.) State

When it comes to the state of the component each element must blend and cater to the topics covered on the webpage. States relate to things like math, science, and history or even lesson 1, lesson 2, and lesson 3. Each state covers different information.

Approach to Web-Component

The web-component in discussion will be a card. My team will be sectioning this component into individual tasks and then regrouping to collaborate and critique and improve each others work. Some of the the tasks will be regarding the major elements such as the icon, banner, scaffold, and card.

Managing Inconsistency

Since the work will be divided the code might seem inconsistent due to each persons coding preference. In order to maintain consistency each member will include notes within their portion of the code so that it can be followed regardless of how it is written. If someone writes something and the group decides there is a better way to write it then it will be updates but otherwise it will be left alone.

Difficulties

Generally communication and production of the cards on schedule will be hard. This is from my point of view due to the lack of coding strength from myself. The project as a whole will require exponentially more effort and collaboration in order to maintain integrity. As stated above there is also the concern of inconsistency which can be negated as long as each member documents their code and what it does.

What is more manageable due to last project

What should be more manageable is the documentation of code and the storybook which addresses the content of the project to anyone who decides to run it.