Research standard NodeJS project structures for backend
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
What is the goal or the problem, and why is it important?
The goal is to determine what NodeJS project structures would best to use for the service based on industry standards. This is important because it will determine how the code is structured and organized.
/epic &3 (closed)
How are you going to achieve the goal or solve the problem?
This will be achieved through online research into common project structures, and will probably involve looking through the documentation on NodeJS's website.
What will be produced as a result of this effort and where will it live on GitLab?
Details about the agreed upon structure will be stored in the 'docs' folder in FillOrder in a file called "projectStructure.md"
Give a justification of weight or due date.
This issue should take 1-3 days because members will need to agree upon a file structure and this make take some discussion about what struck is best for the project.
Who will do it, and what will they do?
@gcolon021 will take this issue and will research common backend file structures to decide what would be best to use. This will further lead to the creation of the actual structure for the backend.
What was the outcome?
The outcome of this issue is project structure documentation found here and includes the links used to understand the common project structures for NodeJS. While there has been discussion about which structure to use there has not been a final selection.
Template Version 1.0.0
/label type::spike