chingu-voyages / v51-tier2-team-25

Slice, an expense splitter and tracking app that offers a simple, clear, and fair solution for managing shared costs. | Voyage-51 | https://chingu.io/ | Twitter: https://twitter.com/ChinguCollabs
https://islice.netlify.app/expenses-user
0 stars 5 forks source link

Project Name - Slice

Chosen logo

Project Description

Slice, an expense-splitting app tailored specifically for roommates and friends. Slice helps users manage and divide expenses such as rent, utilities, subscription services, groceries, and more. Our target demographic is the 18-30 age group, which includes students and early professionals who need an easy way to handle finances among roommates and friends.

Our product vision is to revolutionize how roommates and friends manage their finances. Slice is designed to effortlessly track and divide costs for rent, utilities, and groceries, making shared living more stress-free. Homepage _ Expenses you're in


Getting Started with React, Vite, and Tailwind CSS

This project is set up using React and Vite to provide a minimal configuration for a smooth development experience with Hot Module Replacement (HMR) and ESLint rules. We are also using Tailwind CSS, a utility-first CSS framework, to streamline styling and ensure a responsive, modern UI.

Tools Used

How to Run

  1. Clone the repository.
  2. Install dependencies: npm install
  3. Start the development server: npm run dev
  4. Build the project for production: npm run build

Feel free to customize this setup according to your project needs.


Tailwind CSS Integration

We’ve integrated Tailwind CSS for efficient and customizable styling. You can start using the utility classes provided by Tailwind in your React components right away. For more information on how to use Tailwind, check the official documentation.

To modify the Tailwind configuration, edit the tailwind.config.js file located at the root of the project.


Team and Collaboration

This project is built by a talented team. You can find their GitHub and LinkedIn profiles below. In Sprint #1, team members should validate their repo access by adding their information and practicing PRs.

Our Team


Key Documents

Throughout the project, we have several key documents to assist with planning, communication, and organization. These documents can be found in the /docs directory.

Important Documents

Meeting Agendas

These documents are intended to help the team stay aligned and organized throughout the development process.


Make the README Yours

Remember, your project's README is as crucial as the code itself. Feel free to modify and expand this README to make it uniquely suited to your team's needs and project goals. For inspiration, check out this guide: Keys to a well-written README.