DEV Community

ethan
ethan

Posted on

Week 10: Scoping out the Project

The following was written by my partner, I assisted and drove the coding part:

Writing the 1st article in a series about the scope of what your going to be building
from base card to new project we will be adapting the information to the new ones. this could include individual data for the new cards in the search engine. these individual cards also need to have the scalibility to be individually manipulated. we're also going to need to implement the search engine with a drop down menu that will help break down exatly what the user is searching for so that not everything is displayed and only the cards in that category.

Include images of how you are conceiving the API for the elements involved and the names
we are unsure of how to respond to this

What properties do you think you'll need
badge name, badge icon, badge color accent , badge creator, badge category

What sort of information will need to come from the backend to make this work?
need information like what to search for in the frontend

Either using a screen cast, taking screen shots, links to your code, show how you'll apply concepts from the Homework
https://i.imgur.com/DIyNwrA.png
https://i.imgur.com/JEkxfBR.png

Relate it to what you'll have to do in order to pull this off for Project 2
the card from p1 to p2 will need to be its own individual property with enough customizability that it can be individually edited while maintaining its shape along with the ability to individually be brought up/taken away from the search criteria

Article one is a focus on scope and the activity we did in class. What is the project, what will things be named, how will you initially conceive of attacking the problem
the project is the search menu with the cards. things will be named generally enough so that we can call a group of cards. an example of this could be badges_energydrinks, badges_juices, and these will all be individualized but within the same category.

Top comments (0)