mikakallberg/Portfolio-Project-4

FullStack project

The Green Thumb

Navigation Through Content

• Deployed page
• Project Purpose
  • Learning Outcomes
  • Project Requirements
• Initial Planning
• User Experience
  • Demographics
  • User Goal
• Features
  • Existing features
  • Possible improvements
• Testing
  • Validator Testing
  • Manual testing
  • Automated Testing
• Bugs
• Deployment
• Credits
  • Mentoring
  • Content credits
  • Media -Blog Content credits
    • Why Soil Matters
    • How to grow tomatoes
    • How to grow carrots
    • The humble potatoe
    • The frail but worth it salad
    • The hearty onion
    • The plump Bell Pepper
  • Image Credits
    • About us picture
    • Favicons
    • Creation Credits

Project Purpose

(Taken from Assessment Handbook provided by Code Institute)

• Project purpose: In this project, you'll build a Full-Stack site based on business logic used to control a centrally-owned dataset. You will set up an authentication mechanism and provide role-based access to the site's data or other activities based on the dataset.

Learning Outcomes

• Use an Agile methodology to plan and design a Full-Stack Web application using an MVC framework and related contemporary technologies.
• • see User goals
• • Checklist in deployment
• Implement a data model, application features and business logic to manage, query and manipulate data to meet given needs in a particular real-world domain.
• • see Features
• Identify and apply authorisation, authentication and permission features in a Full-Stack web application solution.
• • see Features
• Create manual and/or automated tests for a Full-Stack Web application using an MVC framework and related contemporary technologies.
• • see Testing
• Use a distributed version control system and a repository hosting service to document, develop and maintain a Full-Stack Web application using an MVC framework and related contemporary technologies.
• • GitHub
• Deploy a Full-Stack Web application using an MVC framework and related contemporary technologies to a cloud-based platform.
• • Heroku
• Understand and use object-based software concepts
• • see Features

Technologies and Libraries used

Languages used

• Django

• HTML

• CSS

• JavaScript

Databases

• Postgresql
• • As database in Heroku
• SQLite
• • As database for Gitpod, the initial thought was to use this for unittest. The setting is left as part of future features, to have automatic testing instead of manual testing

Frameworks and tools

• Bootstrap
• Allauth
• Summernote
• Fontawesome
• Django-Crispyforms
• Django-Copyright
• Google fonts

Cloud storage and deployment services

• Cloudinary
• Heroku
• Gunicorn

Initial planning

Initial plan

• In the intial meeting there was three ideas. Recipe website, Garden blog and Car Dealship. Two rough wireframes where created.

Wireframe 1	Wireframe 2

Plan

• it was decided to build a Garden blog, so a rough sketch of a garden blog with inspiration from existing blogs where made. Please visit credits to see the inspiration used

Home Page	Blogpost page

User Experience (UX)

Demographics

• People who want to know more about gardening and adjancent subject.

User Goals

• As a Site User I can view a list of posts so that I can select one to read
• As a Site User I can click on a post so that I can read the full text
• As a Site User / Admin I can view the number of likes on each post so that I can see which is the most popular or viral
• As a Site User / Admin I can view comments on an individual post so that I can read the conversation
• As a Site User I can register an account so that I can comment and like
• As a Site User I can leave comments, edit and delete comments, on a post so that I can be involved in the conversation
• As a Site Admin I can create, read, update and delete posts so that I can manage my blog content
• As a Site Admin I can create draft posts so that I can finish writing the content later
• As a Site Admin I can approve or disapprove comments so that I can filter out objectionable comments
• As a Content Creator I can upload more then one image so that I can have multiple images in a carousel

Credits

Thank you

• Spencer Barriball for always being there and being a fantastic mentor.
• Daisy McGirr for helping me and giving me insights into backend cooperation with frontend, helping me with some debugs and lessons around django.
• Bim Williams for being a good person to talk to, and for supplying link to API to render content into a downloadable PDF.

Content credits

• This project is modelled and followed using the "I Think Therefore I Blog" walkthrough, produced by Matt Rudge at Code Institute. Using this allowed me to focus on understanding the concepts instead of inventing the wheel with every line of code I produce.
• Another source used in this project is Djanogcentral. Wherever code from this walkthrough is used, there is credit given in that file.
• To upload multiple images I took a lot of inspiration from a content creator on Youtube called The Pylot, my code is not a copy paste of his, but I used his video as a stepping stone to get functionality for my Carousels. I also used docs from Cloudinary.
• For the alt_tags a line of code from a question on StackOverflow was used.

Media

• For how to make the README nav-bar https://github.com/artkonekt/menu/blob/master/README.md was used.
• As template for README https://github.com/mikakallberg/readme-template/blob/master/README.md was used.

• Back to top