chingu-voyages / v48-tier2-team-12 Goto Github PK

Feature Description
Display news about recent dinosaur discovery, using News API

ToDo:

Major User Stories/tasks

• User Story or Task #1
• User Story or Task #2
• Additional User Stories or Tasks as necessary

Additional Considerations
Include anything else that may be helpful. For example, links to external resources.

Task Description
If you have questions about Chingu or the Voyage process join one or both of the Chingu Roundtable sessions held every:

• Wednesday @ 2:00 p.m. GMT -6 (Chicago)
• Saturday @9:00 a.m. GMT -6 (Chicago)

These sessions give you the opportunity to ask your questions in real time with a member of the Chingu team

Technical Considerations
These are held in our Discord community in the #townhall-chat & #townhall-voice channels.

Additional Considerations
You may also ask questions anytime in the #admin-feedback channel in Discord or by opening a support ticket in the #open-support-ticket channel.

Member of Epic: #15

Task Description
Home Page - Add Container for Discover

Technical Considerations
Use React Components?

Additional Considerations
NA

User Story: #32

Task Description

• Each team member should add their ideas to the Project Vision & Feature Planning template before the team meeting
• Prioritize each feature - Must Have, Should Have, Nice to Have
• Meet with the team to review each feature & refine priorities

Technical Considerations
N/a

Additional Considerations
All Must Have tasks will make up your MVP. Make sure that you control the scope of the project by limiting the number of Must Have features to the ones you can reasonably complete by the end of Sprint 6.

Remember that you can always add new features once you complete the MVP.

Resources
Choose a Project & create a Vision Statement (Chingu Handbook)
Define & Prioritize MVP features (Chingu Handbook)

Member of Epic: #16

Task Description
Create Navbar Component for Dinopedia

Describe the problem
An error on console, on homepage:
Each child in a list should have a unique "key" prop.
Check the render method of CategoryTiles.

To Reproduce
Steps to reproduce the behavior:

1. Refresh homepage
2. Open devtools / console

Additional Information
Same problem reported on DinoCardGrid.
Used:
key={index}

Can this be used here?

Task Description
Create CategoryTiles component for filtering

Feature Description
Children Mode

ToDo:

Major User Stories/tasks

• User Story or Task #1
• User Story or Task #2
• Additional User Stories or Tasks as necessary

Additional Considerations
Include anything else that may be helpful. For example, links to external resources.

Feature Description
When app is accessed on different devices (Phone, Tablet, Desktop) Web UI must scale well:
The dynamic elements must be loaded correctly
The images must be displayed right

ToDo:

Major User Stories/tasks

• User Story or Task #1
• User Story or Task #2
• Additional User Stories or Tasks as necessary

Additional Considerations
Include anything else that may be helpful. For example, links to external resources.

Task Description
Describe the task to be completed.

Technical Considerations
Include any technical considerations including architecture (e.g. API), required libraries, etc.

Additional Considerations
Any supplemental information including unresolved questions, links to external resources, screenshots, etc.

Feature Description
Display two charts (pie chart and doughnut chart) illustrating the distribution of general dinosaur diet and type data.

ToDo:

Major User Stories/tasks

• User Story or Task #1
• User Story or Task #2
• Additional User Stories or Tasks as necessary

Additional Considerations
Include anything else that may be helpful. For example, links to external resources.

Task Description
Create Pages and Set Up Routes in a React

Add react-router-dom to the project
Define the Routes

Question:
Should it be created a new file called Routes.js in the root folder in your React app?
Separating routes in their own file, is it a good practice?

Technical Considerations
NA
Additional Considerations
NA

Task Description

• Watch the How to Create a Project Backlog video
  
• Identify & prioritize features
• Create an epic for each feature
• Choose the highest priority epics & divide them into user stories
• Add your epics & user stories to a backlog tool. You may use any project management tool your team prefers. For example, Jira, Miro, Zenhub, GitHub Projects, etc.
• Prioritize the user stories

Technical Considerations
N/a

Additional Considerations
During the Voyage you’ll refine the Project Backlog and in every Sprint you’ll move tasks from it to the Sprint Backlog. This is part of the Agile process helps you and your team concentrate only on the tasks that must be completed in that Sprint.

If you are using ZenHub don't forget you'll need to install its browser extension before you can see the ZenHub tab in your GitHub repo.

Resources
Create a Project Backlog (Chingu Handbook)

Member of Epic: #16

Feature Description
Chingu has created a process for you to follow during the Voyage. This process helps you to get off on a solid start.

Major User Stories/tasks

• 🤝 #5
• 🧑‍🤝‍🧑 #6
• 👍 #7
• 📤 #8
• 📋 #9
• 📝 #14
• ⚙️ #10

Additional Considerations

Learn more in the Voyage Guide:

• Sprint 1 - Getting off to a solid start
• Sprint 2 - Getting off to a Solid Start

Task Description
Search Behavior for Filter Pane

Feature Description
Select one of two themes:

• Dark
• Light

ToDo:
Major User Stories/tasks

• User Story or Task #1
• User Story or Task #2
• Additional User Stories or Tasks as necessary

Additional Considerations
Include anything else that may be helpful. For example, links to external resources.

Feature Description
Search, filter and sort feature allowing users to search for dinosaurs by name, weight, length, country and diet.
Search functionality should be case-insensitive and allow partial matching of dinosaur names.

ToDo:

Major User Stories/tasks

• User Story or Task #1
• User Story or Task #2
• Additional User Stories or Tasks as necessary

Additional Considerations
Include anything else that may be helpful. For example, links to external resources.

Feature Description
Display dinosaurs' name, weight, length, country, diet and corresponding images sourced from the provided API data.
Each dinosaur entry should be clickable to view full details.

ToDo:

Major User Stories/tasks

• User Story or Task #1
• User Story or Task #2
• Additional User Stories or Tasks as necessary

Additional Considerations
Include anything else that may be helpful. For example, links to external resources.

Task Description

• Familiarize yourself with the Chingu Agile Methodology used in a Voyage
• Learn more about Agile Methodologies in general by reading Agile Methodology 101

Technical Considerations
N/a

Additional Considerations
N/a

Member of Epic: #15

Display Home Page

As a User
I want to start with a Home Page
So I can view suggestions and navigate to the other pages

Steps to Follow (optional)

• Create the Page
• #35
• #36
• #37
• #38
• #39

Additional Considerations

• This will be the Home Page
• First version should be Mobile oriented (Following the Mobile First decision)

Task Description
Add Filter button to Home Page

Technical Considerations
NA
Additional Considerations
NA

User Story: #32

Task Description
Create DinoCard component

JSON data: {
"id": 1,
"name": "Aardonyx",
"imageSrc": "https://www.nhm.ac.uk/resources/nature-online/life/dinosaurs/dinosaur-directory/images/reconstruction/small/aardonyx.jpg",
"typeOfDinosaur": "prosauropod",
"length": 8,
"weight": "N/A",
"diet": "herbivorous",
"whenLived": "Early Jurassic, 199-189 million years ago",
"foundIn": "South Africa",
"taxonomy": "Dinosauria, Saurischia, Sauropodomorpha, Prosauropoda, Anchisauria",
"namedBy": "Yates, Bonnan, Neveling, Chinsamy and Blackbeard 2010 (2009)",
"typeSpecies": "celestae",
"description": "Aardonyx is known from 2 immature individuals. Adults would have been much larger, probably over 10m.Aardonyx would have been largely bipedal (walking on 2 legs) but also capable of walking on all 4 legs. This and its way of feeding are transitional features between those of basal sauropodomorphs and the more derived sauropods (large dinosaurs that walked on all fours) that came later."
},

Task Description
Create subfolders on /src:

• /src/pages: contains a new file for each page required for the app.
• /src/components: Components reused across multiple functionalities or features.
• /src/utils: - General utility functions serving various features.

Technical Considerations
NA
Additional Considerations
Related with US #41

Task Description
Using News API

Technical Considerations
Newsapi.org - this is limited to local host - look for an alternative

Additional Considerations
Any supplemental information including unresolved questions, links to external resources, screenshots, etc.

Task Description
Label, search bar input and button

User Story Description

As a User
I want to start a SPA with a Home Page
So I can view suggestions and navigate to the other pages

Related with Epic 01 - #40

Task Description

• Using everyone's availability posted to When2Meet schedule a Kickoff meeting
• Use the Kickoff meeting template in the shared document directory we've provided to guide the discussion and to record notes, decisions, and assignments
• Set a time for your next meeting for later in the week

Technical Considerations
N/a

Additional Considerations
N/a

Resources
Conduct Kickoff Meeting (Chingu Handbook)

Member of Epic: #16

Task Description

• Review the Voyage Process to prepare for your upcoming Voyage.
• Watch the Welcome to YOUR Voyage video

Technical Considerations
N/a

Additional Considerations
Voyage Guide section of the Chingu Handbook

Member of Epic: #15

Task Description
Delete Test-ShowDinos.tsx - used for testing proposes only

Objective

Establish a common understanding across the team of what information is in each screen and the actions that may be invoked from each screen.

How

• Using the features you added to the the Feature Planning template in step 4 identify the screens you’ll need and the information on each one.
• Map the actions users will be able to perform from each screen and the navigation from screen-to-screen
• Create a low-fidelity wireframe using a tool like [Figma](https://www.figma.com/) or even pencil and paper.

Resources

How To Wireframe A Website in 3 Easy Steps
Create a low fidelity wireframe (Chingu Handbook)

Member of Epic: #16

TBD

Feature Description
Describe what the feature is intended to accomplish & why it's important

Major User Stories/tasks

• User Story or Task #1
• User Story or Task #2
• Additional User Stories or Tasks as necessary

Additional Considerations
Include anything else that may be helpful. For example, links to external resources.

Task Description
Home Page - Add Search input

Technical Considerations
NA

Additional Considerations
NA

User Story: #32

Task Description
Accessing data from API: https://chinguapi.onrender.com/dinosaurs

More Info
https://www.freecodecamp.org/news/how-to-consume-rest-apis-in-react/

Feature Description
Prepare for your Voyage by becoming familiar with the Chingu practices & procedures.

Major User Stories/tasks

• #11
• #2
• #3
• #4

Additional Considerations

Learn more in the Voyage Handbook:

• How to prepare for your Voyage
• The Voyage Process

Task Description
Create DinosaurOfTheDay component. It has to show random image from api

Feature Description
Dinosaur of the day section (To be further discussed)

Major User Stories/tasks

• User Story or Task #1
• User Story or Task #2
• Additional User Stories or Tasks as necessary

Additional Considerations
Include anything else that may be helpful. For example, links to external resources.

Feature Description
Interactive Quiz (To be further discussed)

Major User Stories/tasks

• User Story or Task #1
• User Story or Task #2
• Additional User Stories or Tasks as necessary

Additional Considerations
Include anything else that may be helpful. For example, links to external resources.

Task Description

• Decide on the coding standards the team must follow.
• Define the characteristics of your repo including the number of branches, branch names, & the workflow everyone must follow.
• Agree on the format of commit messages, how Pull Requests will be reviewed, and GitHub branch protection rules.
• Decide on where you’ll deploy your app and the branch to be considered as ‘production’ you’ll be deploying from.
• Decide on what meetings you’ll need each week and to save time, schedule them as recurring meetings. You might want to look ahead to Reaching your MVP to learn more about the types of meetings you’ll need.

Technical Considerations
N/a

Additional Considerations
Setup Your Team Workflow (Chingu Handbook)
Javascript Style Guides
Defining a Git Workflow (Chingu Handbook)
Git Branches (Chingu Handbook)
Git Pull Requests (Chingu Handbook)

Member of Epic: #16

Task Description
Create the page only - not behavior

Technical Considerations
Include any technical considerations including architecture (e.g. API), required libraries, etc.

Additional Considerations
Any supplemental information including unresolved questions, links to external resources, screenshots, etc.

Task Description
DinoCard - On Click naviagate to a DinoPage with information about selected Dino

Technical Considerations
Additional API calls on DinoPage should be avoided.
Dino info (from the card) should be passed to DinoPage

Task Description
Create BottomBar component

Technical Considerations
Current location is highlighted in green to show the user where they are

Task Description
Tier 1 & Tier 2 teams will be assigned a project. Tier 3 teams have the choice of creating a project from specifications provided by Chingu or choosing your own project. Check your team channel for more information on which project you are asked to complete.

For Tier 3 teams who choose to create their own project:

• Watch the How to Select a Voyage Project video
  
• Collect ideas from the team
• Brainstorm with your team
• Vote to select one idea
• Decide on the technical stack you’ll use to build your project

Technical Considerations
N/a

Additional Considerations
Use the Project Vision and Feature Planning template to gather & vote on everyone's idea

Resources
Choose a Project & create a Vision Statement (Chingu Handbook)

Member of Epic: #16

Task Description

• Meet your team by adding your introduction to the Team Channel
• Start getting to know one another
• Start discussing what projects you would like to create
• Watch the Voyage Team Roles video to learn about the different roles members of your team may have signed up to fill.
  
• Watch the How to Select a Voyage Project video
  

Technical Considerations
N/a

Additional Considerations
Meet Your team (Chingu Handbook)

Use When2Meet to identify days & times when everyone on the team is available to meet.

Member of Epic: #16

Feature Description
Interactive map with dinosaurs location

ToDo:

Major User Stories/tasks

• User Story or Task #1
• User Story or Task #2
• Additional User Stories or Tasks as necessary

Additional Considerations
Include anything else that may be helpful. For example, links to external resources.

Feature Description
Color Blind Design (To be further discussed)

Major User Stories/tasks

• User Story or Task #1
• User Story or Task #2
• Additional User Stories or Tasks as necessary

Additional Considerations
Include anything else that may be helpful. For example, links to external resources.

Task Description

• Check out apps that Voyage teams have created in prior Voyage by reviewing the Project Showcase
• Come up with 1 to 3 ideas for projects you'd like to build so you can discuss them with the rest of the team when the Voyage starts.
• Think about what technical stack you'd like to use to build that app. Similarly, you'll discuss this as a team at the start of the Voyage.

Technical Considerations
N/a

Additional Considerations
N/a

Resources
Choose a project & create a Vision Statement (Chingu Handbook)

Member of Epic: #15

Task Description
On Home Page
Add Container for Dinosaur of the day

Technical Considerations
Can be a React Component?

Additional Considerations
NA

User Story: #32