The app allows users to post report bugs and suggests new features. The users can create an account to enable posting comments under bugs or features. There is a functionality to vote for the bugs, users can vote for the bug only once. Voting for functionalities require a fee of €50, which enables unlimited votes. Features with the highest number of votes will be developed and released in the next update. To inform users about the highest votes statistics there is a page displaying charts. The administrator of the website can mark bugs/features as following statuses: to do, doing, done.
The user needs to create an account to view/post features or bugs. After login to the app, the user is directed to a profile page where users’ bugs & features are displayed.
This page shows the statistics of features/bugs by status and most voted presented in chart format.
This page displays reported bugs with brief information about the user, date posted and number of votes.
This page displays users’ added bugs and features.
This page shows the latest news
- Registered users can create the account and view/post about features & bugs.
- Users can't delete another user’s bug/feature or edit.
- Prevention of voting on a user’s own posted bug.
- Views are counted only once when users enter the recipe view - - if the page is refreshed it isn't counted. This is done by session to prevent the collection of fake data.
- Users can vote for the feature by paying €50 for a vote; there is no limit to add multiple times.
- The profile page displays the user's posted bugs & features.
- Content on the website has been added by Python Faker.
- The project is using webpack for compiling scss files to css and ES6 scripts to ES5
- Add pagination for bugs/feature
- Search bug / feature
- HTML5
- Django
- for building app backend and render the frontend
- ES6 Support via babel (v7)
- The project uses babel for compiling ES7 to ES5
- Bootstrap 4
- Framework used for frontend development
- JQuery
- The project uses jquery for DOM manipulation and AJAX calls
- SCSS
- The project uses SCSS Preprocessors for compiling to CSS
- Webpack
- The project uses webpack for bundling the assets
- Stripe
- Used stripe gateway to proceed payments
- Python faker
- It used to populate the fake content users/bugs/features/comments to run go to project folder python populator.py
- Crispy forms
- Applying to Django forms bootstrap inputs textareas buttons classes
- Webpack loader
- The app was developed by using Test Driven Development paradigm
- The website has been tested on various screen sizes
The application is deployed to Heroku
Assets files are in assets folder
Compiled files are in the compiled-static/webpack-bundle folder
npm install
npm start
When you run npm run build we use the mini-css-extract-plugin to move the css to a separate file. The CSS file gets included in the head of the index.html.
npm run build
- Webpack boilerplate
- Images used from Unsplash