plixa

Vue 3 Project

This is a Vue 3 project that utilizes the following technologies for styling:

• Tailwind CSS: Tailwind CSS is used for styling components, providing a utility-first approach to CSS.

• Flowbite: Flowbite is employed for a more streamlined and efficient CSS workflow.

Figma File

The Figma file related to this project is attached here: (https://www.figma.com/file/Wu9NFHOMynq54SIZigCKpw/Plixa-web-app?type=design&node-id=269%3A101&mode=design&t=AZzXJnFgbDKlP6Db-1)

Project Description

The name "Plix" is a combination of the words "easy pay" and "clear." The "pl" in "Plix" is derived from "pay," while the "ix" is derived from "clear." The name suggests a simple and straightforward payment process that is free of any obstacles or confusion. It aligns with the business description of eliminating payment hurdles and receipt outage, making it an appropriate and memorable name for a business in the payment processing industry.

Contributing

1. Find an Issue: Take a look at our (https://github.com/saintmalik/plixa/issues/) to find tasks and issues that need attention. These issues are labeled and organized to help you identify what needs to be done.

2. Claim an Issue: If you find an issue that you'd like to work on, leave a comment on the issue to let others know that you're working on it. This helps avoid duplicate efforts.

3. UI Design: We have provided UI designs (Figma link in the main README) that should guide you in implementing the user interface for the issues you're working on. Ensure that your contributions align with the provided design.

4. Branching: Create a new branch for your work. It's a good practice to name your branch descriptively, like feature/issue-number or bugfix/issue-number.

5. Code and Test: Write your code, following the coding guidelines and best practices outlined in the project. Don't forget to thoroughly test your changes to ensure they work as expected.

6. Pull Request: When your work is complete, open a Pull Request (PR) to the main branch. Make sure to provide a clear description of what your PR does and reference the issue it addresses.

7. Code Review: Your PR will undergo code review by the maintainers and other contributors. Be prepared to make any necessary changes based on the feedback received.

8. Merge: Once your PR is approved, it will be merged into the main branch, and your contributions will become a part of the project.