1. Introduction
2. Design
3. Data Structure
4. Wireframes
5. User Stories
6. Testing
7. Deployment
8. Validation
9. Tech
10. Credits

I choose to do this cause gaming has been a hobby of mine since I was just a little kid. So I wanted to make a place where gamers could gather round and chat/post about their favorite parts.

I choose to go with some darker colors but with alot of white around. And the colors I choose is choosen to contrast each other making sure there is high visibility. Then in some places around all theese dark brooding boring colors you will find some splashes of color. All designed to make certain functions pop out to the user. Aswell as when a user is looking at post if he sees one he has created it will say the author name in bold. This was thoughtfully made to make sure you don't have to search for your post.

When looking at these wireframes you can see it isn't made identical to what the plan was. This is partially because I did not have the time to fix the profile page and profile model like I would want to. So the profile page has not been created yet but, I reckoned I might aswell show you a little something of how I plan for it to look.

1. Landing Page
2. Profile Page
3. Current Post Page
4. All Posts Page

My sole purpose of this site was to build something to share ideas and knowledge about the games we love. And perhaps you can find your next gaming companion or promote your twitch channel. The choice is yours.

• Direct Message System (User to User)
• Comment chains (reply system)
• Verification either email or another social media account.
• Create Profilepage
• Add total likes to profile
• Add top posters of the week board

Automated testing has not been implemented in this project. So instead I have done all the testing manually.

• Implementation: Edit button and code to make it possible for a super user to edit any post.
• Test: To test this implementation, I wrote some test posts with different accounts. Then logged in to my super user and tried to edit a couple posts.
• Result: All posts was edited however I noticed it changed the original author.
• Verdict: Test passed it does edit the post however some fixes are needed to make sure author doesn't change.

• Implementation: Delete button and viewcode to make it possible for a super user to delete any post.
• Test: To test this implementation, I used some of all the test post I written and went on to delete it.
• Result: The posts were removed and everything was working as expected
• Verdict: Test passed without any troubles.

• Implementation: Auto selection of game on add post view
• Test: To test this implementation, I clicked my way in to add post page, and filled it out with some test data without choosing game.
• Result: It worked, after posting it jumped back to the right category again and the post were visible. However if trying to access this view from home page with url would cause an error
• Verdict: Test passed it did what it was supposed to however this error needs to be addressed and fixed.

• Implementation: Add edit possibilty for the author of an post
• Test: To test this implementation, I went in on an account created an post. Then tried to edit the content and the title.
• Result: It all worked good, when changing title and content then applying it sent me back to the postview with all changes applied.
• Verdict: Test passed as expected without any bugs present.

• Implementation: Add the function to like a post.
• Test: To test this implementation, I logged in to one of my accounts and tried liking different posts.
• Result: It liked like it was supposed to however if I logged out of the account and liked it threw and 500 error.
• Verdict: Test passed but bugs were present. Need to add authentication to like view, and send them to login page instead if clicking when logged out.

• Implementation: Making summernote more responsive
• Test: To test this implementation, I went in to add post and changed the device to some different phones and sizes.
• Result: After this implementation it does scale much better, however summernote does not seem to be preferable on phones. The toolbar at the top does not scale well so you get an horizontal scroll inside the notepad.
• Verdict: Test passed but does need some review in future development

• Problem: 500 Error on signup if email is filled out.
• Cause: Email verifications without any setup in django.
• Solution: Removed email verification by adding ACCOUNT_EMAIL_VERIFICATION = 'None' to settings.py. This to stop an email from trying to be sent.

• Problem: Form error when adding comment."No Author ID"
• Cause: Script was missing accidently been deleted, which filled out the hidden input
• Solution: Checked the old commmit and copied and pasted in the code again.

• Problem: By editing a post it changes the user. For instance if a superuser needs to fix some content.
• Cause: When editing it uses the same form as adding, so the script filled out the wrong author-id.
• Solution: Changed out variable for author from user to post.user and it all worked.

• Problem: Trying to access add-post page from the homepage throws an error.
• Cause: It couldn't find the HTTP_REFFERER since there is none when trying to access it this way.
• Solution: Added an if statement to check if HTTP_REFFERER exists in add-post and if it doesn't it hops over the code for prepoulating game field.

• Problem: When trying to like a page while not logged in, it sends you to login, but after you login it throws error.
• Cause: It is because it can not find the post without the id it gets from the request when clicking like.
• Solution: Disabled the like buttons for non logged in users instead.

The only known issue for me right now is summernote, it still does not look good but it is functional. At a later time I would like to see if there is, any other text editor more suited for phones. If there is one to be used it would make the phone use much easier and hopefully it would look neater aswell.

• Cloudinary account to store static files.
• Github
• Heroku

1. Get link to copy my repository. You can do this by clicking the green "code" button and then copy the HTTPS link.

2. Start up your own repository and enter bash command "git clone {link you copied}". Now you have copied everything and the settings can start.

3. Add an env.py file to root directory. If you are setting up for deployment with heroku check out step 4 in Deployment to heroku, if you need help finding your DATABASE_URL. In this file you will add:

import os

os.environ["SECRET_KEY"] = "[Your Secret Key]"
os.environ["DATABASE_URL"] = "[Your DB URL]"
os.environ["CLOUDINARY_URL"] = "[Your CLOUDINARY URL]"

4. Run this command to install everything in requirements.txt

pip3 install -r requirements.txt

1. To setup the database you must run the following command

python3 manage.py migrate

2. Then create your super user by typing this command

python3 manage.py createsuperuser

3. Start the server by running this command

python3 manage.py runserver

4. You should now have gotten a message if you want to browse your server. If you click this it should be working. Though since it is your own database it won't be populated with anything until you fill it up.

If you want to run this is an online environment I recommend trying heroku. Before trying this make sure you have followed the steps prior to this.

1. Either create an account or log in at Heroku

2. Set up a new app with a unique name in your region.

3. Locate resource tab and in addons field search for "postgres" and select free option

4. Locate your settings for app and reveal your config vars. Here you will find your DATABASE_URL this should be copied in to your env.py file so if you are running locally you will still be accessing the same database.

5. While you are at the config vars also add: ´´´bash CLOUDINARY_URL : {Your Cloudinary Url} SECRET_KEY : {Your Secret Key} ´´´

6. In heroku dasboard select deploy tab

7. Select deploy from github you can also enable auto deploy for future push

8. You can now follow the deployment in the window and when it is done you click "open app" at the top.

• To validate my python files I ran them all through PEP8 Online Check Below you can find the results of the tests. Only things left are some too long lines which can be seen in the document of "PEP8 settings.py"

• PEP8 admin.py
• PEP8 apps.py
• PEP8 contexts.py
• PEP8 forms.py
• PEP8 models.py
• PEP8 urls.py
• PEP8 views.py
• PEP8 settings.py

• To validate my HTML I ran them through HTML Validator And everything turned out all right except for summernotes widget which has alot of errors, which is an cause of how summernotes are built. This can be seen in picture number 3 all theese faults origins from summernote widget.

1. CSS Validation
2. Landing Page Validation
3. Summernote Errors
4. Login Validation
5. Logout Validation
6. Post Detail Validation
7. Post List Validation
8. Register Validation

• HTML
• CSS
• Javascript
• Python

• Django
• Bootstrap

• Jquery

• Cloudinary
• Heroku
• Postgres

Credit goes out to my mentor Richard Wells for all the awesome help during this project.

And also to Stackoverflow for having some quick answers Link to Stackoverflow