In this project, we will use Django as our software framework.

Do we want to allow users with no profiles? if the answer is nom then this issue is needed, otherwise for now we can update the Post model to be linked with the Django default User (will be conflicted with the PR related to issue #55)

• Adding the main content from the Readme to the about us page (using semi-automatic .md file to HTML converter with small fixes)
• Removing teammates that have been already left

writing 'setup', 'body' and 'tear up' for testing functionality of commenting using pytest, covering:

• model relation deletion
• populating database and assertion
• testing model functions

Make a static HTML file as the app demo page.

The file will contain the following details:

• App name
• Short Description
• Team members names

This issue is dependent on #3

The file path should be:
picATrip\msgboard\templates \board.html

• Allowing users to be able Log In and Log out
• Users needs to be logged in in order to access certain pages.

• add a class view for a list of posts
• create a template for the URL

• After register, the profile is created automatically (with defaults fields)

• adding migrations and a model for representing a comment.
• adding customized model registration to comment model and automating the process for models that will be added in the future

related issue: #44

Adding for now a page for posts and details without considering the presentation of the images, later it will be merged with another page that is going to be dealing with this issue of presenting pictures by the saved URLs in the post objects.
This entire issue considering the comments - view part focusing on the forms subject of Django

The script should run automatically on the VM using the Vagrant provisioning process.
Initially, the script should only install Pipenv and tell it to install software dependencies.

• Adding a new HTML file so we can add some data into the page in the future

• Also update the script to run pipenv sync.
  This depends on a Pipfile.lock file that is created when installing Django (#3).

This task is dependent on Django having been installed on the Vagrant box (issue #3),
and on having a script to update (issue #7).

Adding a link to the Google doc that includes the Application structure, features, feature story that describe the user experience etc.

This task is dependent on a Django app having been created and containing migration scripts (as part of #6),
and on having a script to update (issue #7).

Creating a base template as the frame for all pages in the application.
The file will help us to avoid repeated code, and make changes in a single place.

some examples - (https://docs.djangoproject.com/en/3.1/topics/auth/default/)

adding initial settings for using pytest and avoid conflicts with other PRs of the common basis of PRs related to tests using pytest

Install flake8 in order to verify that the code we add conforms to proper Python syntax and coding standards.

The scrolling bar doesn't work for some HTML pages- need to be fixed (low priority) - look for about.html in PR #67

useful and a better UX since nobody likes signing in and signing up -
Facebook - (https://learnbatta.com/blog/signup-sign-in-using-facebook-django-application-9/) - (optional for now the google sign-in is enough)
Google - (https://whizzoe.medium.com/in-5-mins-set-up-google-login-to-sign-up-users-on-django-e71d5c38f5d5) - Ma'ayan

Creating a user registration page that allows users to register to our app.

The commenting page will be a standalone page that the user will be redirected to when clicking on a "comment" button from the page that will be created for viewing a post.

for further details please check the google doc that elaborates the feature story in details (link appears on the bottom of the ReadMe file of the project)

Adding ERDs and DFDs to describe the relations between models and models in our project django apps to the google doc (link appears in the ReadMe.md file)

• Create a folder that contains our documents and how the application is organized.
• Adding a link to the Google doc that includes the Application structure, features, feature story that describe the user experience etc.

Adding code to support automation of the model registration process to the admin site, providing a simpler interaction with the tables that represents each model in the DB - each column representing a field in the model.

Adding a page where the users see the following mandatory fields (and can fill them ):

• Name of poster
• Name of location
• Main photo URL
• Description of the experience

writing a .yml file to implement an automatic file as we did with flake8 to run tests on the code we present in each PR.

fixing issue #4

• fixing the appearance of the ReadMe.md file
• adding a logo for the project
• adding technologies used for development
• using more of Markup language capabilities

related issue: #4

When testing PR #18, the flake8 tests failed with the following message:

This issue is for fixing the files so they pass the flake8 tests.

• Update the Team members list of the ReadMe.md file

Test

0. vagrant up --provision
1. go to localhost:8000/register
2. fill in details and continue
3. it throws an exception :
   

The way Vagrant works is that we create a file called Vagrantfile that contains the
instructions about how to create and bring up a virtual machine (VM) for working on our project.

We want to make sure that all the teammates can successfully use Git to clone the team project and Vagrant to bring up the development environment on their machines.

Use the built-in Django authentication system for the basic fields and an additional table for more info

• Adding pytest files and settings
• Adding a file to Github workflow in order to make it run when making a new PR

Depends on the #77 issue and waiting for PR #80 in order to be merged (although not really necessary but it's generated based on the use of the pytest-black automate file formatting so It would be wiser to wait until it will be merged to check whether the test passed or not).

• Adding postsList.html to the navigation bar in base.html

create a 'Post' application and add a 'post' model.

• When clicked on post it will redirect to the post detail page by the post id, blocked until PR #73 will be merged.
• In later versions will be replaced with clicking on the image of the post (after the feature of presenting a photo per post will be ready)
  closes PR #104

Updating the ReadMe file to describe more thoroughly the 'picATrip' project.

for each URL on our site, we need to check that it is referring to the correct view.

The folder that contains the views/models files named apphomepage.
I chose that name when I created the home page and now he seems wrong.
Please suggest a better name for this folder.

For now, the comments presented for each post in the post detail pages (look for issue #73) are showing the number of comments at most as 5 comments (even if there's more than 5) - it's currently medium prioprity

Update the navigation bar

• register and login page will be shown before the user logged in.
• logout and profile page will be shown after the user logged in.