Welcome to the Billy project.
First you need to set up the database user, the spring configuration expects to login with the following user:
CREATE USER "groep2" WITH CREATEDB PASSWORD 'groep2-password';
Next the database needs to be created, for that you can use this script:
CREATE DATABASE "v2b2-prfed" OWNER "groep2";
For this project we used three branches:
This is the main branch, every release gets merged into this branch.
Every feature branch eventually gets merged into this branch and every pull happens from this branch.
These are branches made for specific features, they are based on the development branch and when the feature is fully implemented this branch gets merged with development and deleted.
This iteration we worked on three user stories:
This was divided into a few issues:
- Adding a user to an article
- Displaying the user on the article
As a system administrator, I want the ability to rollback to previous versions, so no information is lost.
This was divided into a few issues:
- Adding a table on every article's history tab
- Getting the history of an article and filling the table
- Adding a button that changes the article back to that state
This was divided into a few issues:
- Creating a request that gets you all article titles
- Creating a search suggestion bar
There was another issue we worked on for this iteration. It was related to adding information to the database:
- Adding a button that shows a popup for creating an article
This iteration we worked on four user stories:
As a user, I want the wiki to be divided into the matrix of categories, so the information I am looking for is findable.
This was divided into a few issues:
- Saving articles into the backend database
- Adding matrix categories to the wiki
This was divided into a few issues:
- Wireframe Edit modal
- HTML Edit modal
- CSS Edit modal
- JS Edit modal
As a system administrator, I want that only registered users are able to edit the wiki, so there are no unwanted edits.
This was divided into a few issues:
- Add a check before the editing process to see if the user is allowed to edit
As a user, I want to be able to turn on accessibility mode, so I can still get information with a disability.
This was divided into a few issues:
- Add three buttons for changing the font size
- Adding functionality to those buttons
- Add dark mode
There were some other issues we worked on for this iteration. They were related to the creation and accessibility of information:
- Setup of Heroku
- Dummydata for the database
This iteration we worked on two user stories:
This was divided into a few issues:
- Wireframe Indexpage
- HTML Indexpage
- CSS Indexpage
- JS Indexpage
This was divided into a few issues:
- Wireframe Loginpage
- HTML Loginpage
- CSS Loginpage
- JS Loginpage
There were some other issues we worked on for this iteration. They were related to the startup of the project:
- Creation of the database
- Spring backend setup