Project Information

🌠 Meteor Shower App: Your Ultimate Meteor Adventure 🚀

Meteor Shower App is the optimal app for meteorite enthusiasts of all levels. With its intuitive search tools and advanced exploration capabilities, you can easily discover the wonders of meteorite impacts from around the world. 🌍

Dive into Cosmic Thrills 🌌

Immerse yourself in the enchanting universe of meteorites, where curiosity knows no bounds. Explore the latest news and discoveries and learn about the different types of meteorites.

Effortless Discovery ✨

Unveil the wonders of meteorite impacts effortlessly using our Meteor Shower App's intuitive search tool. Whether you are searching by date, location, or simply your interests, you will find the information you need at your fingertips. 🚀🔬

Advanced Exploration 🌟

Elevate your journey with Meteor Shower Page's advanced search capabilities. Filter your results by name, year of impact, meteorite composition, and mass range. Delve deeper into the aspects that intrigue you the most. 🔍

Beyond Search Limits 🛰️

Meteor Shower Page offers more than just search functionality. Save your frequently used search criteria for swift access. Visualize results through interactive maps and rows. Seamlessly sort data to unveil hidden patterns. 📊💡

Knowledge Empowerment 📚

Empower yourself with instant data definitions right within the app. Quickly grasp the significance of each column, eliminating the need for external research. 💪🧠

Discover Deeper Insights 🌟

Embark on uncharted paths and reveal extraordinary insights. From total strike counts to average masses, Meteor Shower Page showcases comprehensive information, ensuring you're in the know. 📊✨

Ready to explore the mysteries of meteorites? ⭐🌠

Let’s go!

Live Link!!

User Stories Trello

MVP (Must Have)

Wireframe

As a Developer I want to have a wireframe So that I can easily follow the desired design

Acceptance Criteria

• The wireframe should contain:
  • logo
  • background
  • search component
  • results display part
  • map
  • buttons
  • Header
  • Footer

Responsive Optimization

As a user I want the app to be responsive So that I can see it both on my phone and PC

Acceptance Criteria

• The app must be responsive for 1920 x 1080 pixels and 720 x 1280

Search Button

As a user I want to see a search button that triggers the search operation So that I can easily surf through the data

As a user I want to see the result of my search in rows and map So that I can clearly see the resulted data

Acceptance Criteria

• Each record of the database should display in a row
• The display should be filtered on the map too
• While hovering over the map, the data should also be displayed on a small pop-up
• There should be a paragraph with the numbers of meteorite strikes
• There should be a scrollable detailed data display that shows meteorite strike history based on the search criteria

…To see more User Stories and all related documents check our Trello

Tech Stack

HTML, CSS, VanillaJS, Leaflet.js

Git Strategy

Pull Requests & Merging

All Pull Requests and code merging will take place in the project's Github repo. To reduce merge conflicts, the destination branch should be pulled into the merging branch prior to opening a pull request. To test changes and review a PR locally before approving it, read modifying an active pull request locally. For the purposes of testing, just use the commands in "Step 1" which brings the PR local. After testing, you can go back to Github and approve or comment on the PR.

Development Branch

Working branches will be merged into the development branch during weekly development. At least one team member other than the requester must review and approve a request before it can be merged. After the merge has been approved, the requester will perform the merge on Github and delete the merged branch from the repository upon a successful merge. If any merge conflicts occur, the requester must work with the author of the conflicting code to resolve them and re-submit the PR for approval.

Master Branch

A PR to merge to the master should reflect the goals of the prior week's sprint and produce an updated MVP. This PR will typically take place following the weekly sprint meeting. All team members must approve a request for merging into the master branch.

🚀 Development Workflow

A three-level hierarchy of branches is used, through which changes are promoted.

Working branches:

Individual branches created by each developer when they are working on changes and bug fixes. The type can be one of these types:

• feature: a new feature
• fix: a bug fix
• docs: changes to documentation
• style: formatting, missing semi colons, etc; no code change
• refactor: refactoring production code
• test: adding tests, refactoring test; no production code change
• chore: updating build tasks, package manager configs, etc; no production code change basic types of branches:

Development:

Reflects the code for the next release. Developers work in working branches, which are then pulled into this branch. All code pulled into this branch must be tested and undergo peer review as part of the PR process.

Master:

Only updated from the development branch Pull Requests. This branch always reflects the current production release that is seen by live users.

Meteor Shower Team

The Meteor Shower Team initiated this project within the Chingu community with the goal of gaining valuable teamwork experience and enhancing our skill set. Our commitment to effective communication, adaptability, and constant innovation allowed us to deliver a well-crafted project that aligns with our collective goals and aspirations.

Our team comprised 5 Developers and 2 Product Owners.The project spanned 6 weeks, aligning with Chingu's guidelines and Agile methodology.

Developers: Ana Popovic, Isaac Anim, Eva Langerova, Mustapha Anthonio, Vruti Shah

Developers Lead: Ana Popovic

UI/UX Designer: Vruti Shah

Product Owners: Petre Circeag, Zahra Motlagh

Agile Coach: Christopher Maxwell

Chingu Coach, Chingu Guide: Jim Medlock , Bahareh Amali