Merge branch '56-create-readme' into 'master'

Resolve "Create Readme"

Closes #56

See merge request !56

README.md

 # idatt2106_2024_3_frontend
 
+<div align="center">
+  <h1 align="center">Sparesti</h1>
+  <h3 align="center">idatt2106_2024_3_frontend </h3>
+  <p align="center">
+  This is the frontend repository made by Magnus Rindal, Håkon Fredrik Fjellanger, Isak Kallestad Mandal, Sverre Frogner Haugen, Tini Tran, Torbjørn Antonsen, Vilde Min Vikan and Jens Martin Jahle, for the subject System Development with agile methods (IDATT2106) for the spring semester 2024.
+  </p>
+</div>
 
+## Description
 
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+Sparesti is a web application that helps users save money by providing a platform for users to
+create and manage savings goals, perform challenges, and track their progress.
+The application is designed to be user-friendly and intuitive, making it easy for users to save
+money and reach their financial goals.
 
-```
-cd existing_repo
-git remote add origin https://gitlab.stud.idi.ntnu.no/scrum_team_3/idatt2106_2024_3_frontend.git
-git branch -M main
-git push -uf origin main
-```
+This repository contains the frontend code for the Sparesti application. The frontend is built using Vue and TypeScript, and it provides the user interface for the application.
+The frontend is responsible for displaying the user interface, handling user input, and communicating with the backend API. 
+The frontend is designed to be responsive and accessible, making it easy for users to interact with the application on any device.
 
-## Integrate with your tools
 
-- [ ] [Set up project integrations](https://gitlab.stud.idi.ntnu.no/scrum_team_3/idatt2106_2024_3_frontend/-/settings/integrations)
+## Badges
 
-## Collaborate with your team
+<a href="https://gitlab.stud.idi.ntnu.no/scrum_team_3/idatt2106_2024_03_frontend/-/commits/master"><img alt="pipeline status" src="https://gitlab.stud.idi.ntnu.no/scrum_team_3/idatt2106_2024_03_frontend/badges/master/pipeline.svg" /></a>
 
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
 
-## Test and Deploy
+<a href="https://gitlab.stud.idi.ntnu.no/scrum_team_3/idatt2106_2024_03_frontend/-/commits/master"><img alt="coverage report" src="https://gitlab.stud.idi.ntnu.no/scrum_team_3/idatt2106_2024_03_frontend/badges/master/coverage.svg" /></a>
 
-Use the built-in continuous integration in GitLab.
+## Visuals
 
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+### Homepage
+![Homepage](src/assets/readmeImages/homepage.png)
+### Milestone Playthrough
+![ChallengePlaythrough](src/assets/readmeImages/challengePlaythrough.png)
+### Consumption Overview
+![ConsumptionOverview](src/assets/readmeImages/consumptionOverview.png)
 
-***
 
-# Editing this README
+## Installation and execution
 
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+> **Note:** The backend repository must be running in order for the frontend to work as intended.
+> The backend repository can be found [here](https://gitlab.stud.idi.ntnu.no/scrum_team_3/idatt2106_2024_03_backend).
 
-## Suggestions for a good README
+### Prerequisites
 
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+To run this program you need:
 
-## Name
-Choose a self-explaining name for your project.
+- Node.js
+- npm
 
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+### Installation
 
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+1. Clone the repository using Git:
+   ```sh
+   git clone https://gitlab.stud.idi.ntnu.no/scrum_team_3/idatt2106_2024_03_frontend
+    ```
+   
+2. Alternatively, you can download the ZIP file and extract it.
+    https://gitlab.stud.idi.ntnu.no/scrum_team_3/idatt2106_2024_03_frontend/-/archive/master/idatt2106_2024_03_frontend-master.zip
 
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+### Running the repository
 
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+1. Navigate to the root folder of the project
+2. Run the following command to install the necessary dependencies:
+   ```sh
+   npm install
+   ```
+3. Run the following command to start the frontend:
+   ```sh
+    npm run dev
+    ```
+4. The frontend should now be running on http://localhost:5173
 
 ## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
 
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
+To use the application, open a web browser and navigate to http://localhost:5173.
+You can now create an account, log in, and start saving money by creating savings goals and performing challenges.
+You need to have the backend running in order to use the application as intended.
+Also note that the logged-in user must have a connection to our mock bank in order to use the application as intended.
+Use our test user with the following credentials:
 
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+- Username: JohnSmith12
+- Password: password
 
 ## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
 
-## License
-For open source projects, say how it is licensed.
+This project was made by the following students at NTNU:
+
+Magnus Rindal,
+Håkon Fredrik Fjellanger,
+Isak Kallestad Mandal,
+Sverre Frogner Haugen,
+Tini Tran,
+Torbjørn Antonsen,
+Vilde Min Vikan and
+Jens Martin Jahle
 
 ## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+This project is currently finished and will not be maintained.
+There are no plans to continue development on this project in the future.
\ No newline at end of file