Feedball is a social interaction and opinion sharing platform for football fans. The platform contains multiple high-end functionalities for both admins and users.
Admins: Can monitor user profiles, delete accounts, ban and unban users from the platform, can inform fans on the date and time of upcoming matches, create and de-activate polls, post news to reach public opinion.
Users: Can sign-in, modify profile information, pick their favouirte teams, delete accounts, read and like/dislike news (these news are provided to the users based on their previously selected favorite teams), answer polls, send live messages, rate messages. By liking/disliking news, liking messages and answering polls users can gain points and advance in the leaderboard to later earn awards.
The software requires no installation. You can start enjoying FeedBall the minute you sign up! You can access the app by following this link.
The user clicks the site URL / searches the site name on their internet browser to enter the platform and use it accordingly after the sign up and login processes.
Sign in process: Firstly, the user needs to create an account by entering a valid e-mail address (a validation e-mail is sent to the provided e-mail to complete the validation process), a valid password (a valid password contains a minimum of 6 characters) (the password needs to be entered twice on a separate field to prevent mistakes), name, surname, date of birth in MM/DD/YYYY format, gender and prefered team information.
The sign up process is finished once the valid information is entered and the user pushes the sign up button.
Login process: After an account is succesfully created, the user enters the previously selected e-mail and password infromation on the respected fields. The login process is finished by pushing the "Login now" button.
Go to https://github.com/SU-CS308-22FA/Group-13-FeedBall, find Issues tab and post an issue regarding the bug experienced.
You can write a short description of the bug experienced as title, the circumstances in which you experienced the bug as body, select the label as "bug" and submit the issue.
The issues are periodically checked by the team to provide adequate customer service.
There are no known bugs at the moment. This page is updated periodically.
We use the same document for both the backend and the frontend of the web app, and this said code could be found within our GitHub Repository.
There are two ways to obtain the code:
1- Cloning the repo using the URL that is obtained from the green “Code” button in GitHub. Then, you take the HTTPS link for the GitHub repo, and choose the directory in which you want to view the source code. Then, using git clone and the https that is obtained, you clone the repository to your local device within the directory you want.
2- Downloading the code as a zip file from GitHub. The code is downloaded from the green “Code” button, clicks the download ZIP. The file should then be unzipped. Then you open your chosen Integrated Development Environment and open the unzipped code file to view the source code.
The directory is mostly self-explanatory. Every page that you are redirected to has its own separate folder.
The docs folder contains the images that are used within the code, for example the logo and the custom headers within the main page. The biggest folder is the src, which contains app, assets, and environments.
In the app folder, there are the pages, each having their own css, html and ts file. The models files are crucial when creating a new collection within the database. It contains every collection we’re keeping track of (matches, messages, news, polls). Shared\services are responsible for keeping track of the database implementation and sending/receiving data from our database. App-routing module is for creating paths within the web app and app.module is where we initialize our declarations and export them as necessary.
(We used Vercel to deploy our server, which uses your Git account to access the projects within. Vercel is also in sync with the project, meaning every change you make within the source code that you push the GitHub will automatically be deployed to Vercel as well.)
This project was generated with Angular CLI version 14.1.2.
Run ng serve for a dev server. Navigate to http://localhost:4200/. The application will automatically reload if you change any of the source files.
redadmemd eski hali
Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.
Run ng build to build the project. The build artifacts will be stored in the dist/ directory.
Run ng test to execute the unit tests via Karma.
Run ng e2e to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.
To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.