soniccyclone / requestbox

🦕 Hello! I’m Nathan Barlow! 🦖

I am a software developer, a gamer, a Christian, and many other things!

I have moved my personal development over to sr.ht, check it out!

requestbox's Issues

Design UI/UX

Prototype all of the screens on this website.

Design DB schema

We need a DB schema that can handle users, requests, and comments on those request.
Users need to have different roles (e.g. admin, developer, client) and have ownership over their requests and comments. They should need to contain other identifying information (e.g. name, company role).
Requests are basically just a title and description of the request. They have comments attached to them and they can also hold a special link in case someone wants to link the request directly back to a project board task or bug tracker issue. This link is just a simple hyperlink in an eye catching location. Requests can also be upvoted by users. This is not anonymous so a user can track the requests they have upvoted easily.
Comments are just comments attached to requests. We'll allow subcomments and collapsing comment threads so as to not limit conversations on requests.

Setup project environment

Project needs to build in vscode. There should be no additional setup beyond cloning the repo, opening with vscode, and hitting run. It needs to be as easy to run as visual studio makes things.
Don't forget to setup test environments that can be easily run in vscode as well.

Create entities

Should just be: User, Request, and Comment.

Create MongoDB

Design application architecture

Utilize ARF somehow.
Probably some simple MVC/MVP front end architecture with an ARF back end architecture.
Possibly use Vuex?

Design OAuth implementation

This will possibly affect the User entity. So plan ahead for what is required for us to support both local and OAuth users.