https://github.com/chingu-voyages/v49-tier2-team-17

Color Explorer | Voyage-49 | https://chingu.io/
https://github.com/chingu-voyages/v49-tier2-team-17

groq-api react tailwindcss

Last synced: 2 months ago
JSON representation

Color Explorer | Voyage-49 | https://chingu.io/

• Host: GitHub
• URL: https://github.com/chingu-voyages/v49-tier2-team-17
• Owner: chingu-voyages
• Created: 2024-05-04T16:32:18.000Z (9 months ago)
• Default Branch: main
• Last Pushed: 2024-07-01T03:07:55.000Z (7 months ago)
• Last Synced: 2024-07-05T13:51:55.937Z (7 months ago)
• Topics: groq-api, react, tailwindcss
• Language: JavaScript
• Homepage: https://v49-tier2-team-17.netlify.app/
• Size: 948 KB
• Stars: 1
• Watchers: 4
• Forks: 3
• Open Issues: 14
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# voyage-tasks

Your project's `readme` is as important to success as your code. For

this reason you should put as much care into its creation and maintenance

as you would any other component of the application.

If you are unsure of what should go into the `readme` let this article,

written by an experienced Chingu, be your starting point -

[Keys to a well written README](https://tinyurl.com/yk3wubft).

And before we go there's "one more thing"! Once you decide what to include

in your `readme` feel free to replace the text we've provided here.

> Own it & Make it your Own!

## Team Documents

You may find these helpful as you work together to organize your project.

- [Team Project Ideas](./docs/team_project_ideas.md)

- [Team Decision Log](./docs/team_decision_log.md)

Meeting Agenda templates (located in the `/docs` directory in this repo):

- Meeting - Voyage Kickoff --> ./docs/meeting-voyage_kickoff.docx

- Meeting - App Vision & Feature Planning --> ./docs/meeting-vision_and_feature_planning.docx

- Meeting - Sprint Retrospective, Review, and Planning --> ./docs/meeting-sprint_retrospective_review_and_planning.docx

- Meeting - Sprint Open Topic Session --> ./docs/meeting-sprint_open_topic_session.docx

## Our Team

Everyone on your team should add their name along with a link to their GitHub

& optionally their LinkedIn profiles below. Do this in Sprint #1 to validate

your repo access and to practice PR'ing with your team _before_ you start

coding!

- Oleg Klyufinskyy [GitHub](https://github.com/olegklyufinskyy) / [LinkedIn](https://www.linkedin.com/in/oleg-klyufinskyy/)

- Shruti Salunkhe [GitHub](<[https://github.com/](https://github.com/salunkhesshruti)>) / [LinkedIn](https://www.linkedin.com/in/shruti-b/)

- Nicole Schiewer: [GitHub](https://github.com/NicoleSchiewer) / [LinkedIn](https://linkedin.com/in/nicoleschiewer)

- Aseel Shakra [GitHub](https://github.com/asiill)

- Alta Gong: [GitHub](https://github.com/altagong) / [LinkedIn](https://www.linkedin.com/in/altagong/)

- Karen Jean Louis [GitHub](https://github.com/Limebee) / [LinkedIn](https://www.linkedin.com/in/karen-jean-louis-391007200/)

- Danyal Imran [GitHub](https://github.com/imRanDan) / [LinkedIn](https://www.linkedin.com/in/danyalimran/)

- José Bonilla [GitHub](https://github.com/jy-bonilla) / [LinkedIn](https://www.linkedin.com/in/bonillacodes/)

- Teammate name #n: [GitHub](https://github.com/ghaccountname) / [LinkedIn](https://linkedin.com/in/liaccountname)