Skip to content

aditiakella/Per2Gaels

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Period 2: Gaels

Scrum Team Members and GitHub Profile Links

Links

Project Overview

Our website, tweeter.gq, is a website that features information about birds and their evolution. Our project showcases our team's learning throughout the year. Our project utilizes a Python Back End and an HTML Front End, as well as Jinja templates, SQLAlchemy databases, and CSS.

Project Components

Homepage (Grace):

Navbar (Grace):

  • On each page of our website there is a navigation bar
  • Clicking on those links takes you to different parts of our website
  • If you click on our logo, which is in the middle of the navbar, you will be redirected to our easter egg
  • Code Review:
    • On home.html, here is the code that sets up the style for the navbar
    • Here is the code that links the homepage of our website.
    • Here is the code that creates the dropdown menu for the About Us pages
    • Here is the code that links the Twitter API
    • Here is the code that turns our logo into the easter egg
    • Here is the code the links the contact page, phylogeny page, and our study journal
  • Scrum Board Card

About Pages (Aditi):

Audubon Society Twitter API (Luke):

  • To access the Twitter API, click on the API link on the homepage which will rediect you to the Twitter API
  • Code Review:
    • Views.py
      • The API keys and link are printed here in order to gain access to the API.
      • Under the keys, json.get is used to pull the data using the variables given when the API endpoint is tested on the Rapid API website.
      • Then it takes the respone [200] and prints it.
    • Tweet.html
      • The html code used in order to display the data the API pulls. It takes the variables from the app route and prints them onto the website.
  • Scrum Board Card

Easter Egg (Sophie):

  • In order to run this file, go to the homepage, click the logo in the middle of the screen, and it will redirect you to the Easter Egg
  • Code Review:
    • First, on easteregg.html, there is a section that sets up the style of the easter egg.
    • Then, there is code for our navbar
    • Next, we embedded the college board requirements.
    • Then we wrote the code for the "Who am I in Computer Science?", which highlights all of the things that we have learned throughout the course of working on this project.
    • We have also embedded our group journal, which has also been embedded to demonstrate our completion of the college board requirements
    • At the end, we used an HTML form to create a "feedback" page where you can say which aspects of the college board requirements you (the evaluator) think were not efficiently used
  • Scrum Board Card

Databases Front End (Grace):

  • On the navigation bar if you click on contact it will take you to an contact page
  • Code Review:
    • First, our contact page was created using index.html, which is based on a Jinja template using base.html. Base.html includes the style for index.htmal as well as a navbar.
    • On the contact page, there is a contact form on which the user can input there name, password, email, and phone number
    • Using the contact form, the user can add their information to a contact table.
    • Users can delete there information if they don't want it there anymore
  • Scrum Board Card

Database Back End (Aditi):

  • In order to access our database, go to our homepage and click on Contact in the NavBar. This will take you to the contact database page.
  • Code Review:
    • First, the User class, Email class and Phone Number class are defined in init.py.
    • The User ID is declared as the Primary Key, which means that each person in the database will have a unique user id.
    • Then, in create.py, the model_create function is defined, which allows users to be committed into the database.
    • Also in create.py, the model_delete function is defined, which allows users to be deleted from the database.
    • Then, create.py has a few functions that allow the names, passwords, emails, and phone numbers of users who are already in the database to be called.
    • Next, in views.py, all of the functions from create.py are imported.
    • In the create procedure on views.py, first, the contact form is used to gather the name, password, email and phone number of the user.
    • Then, the model_create procedure is called in order to commit the user's imformation to the table. The user's information is then shown in the database table.
    • In the delete function on views.py, a similar method is used.
    • First, the form is used to identify which user should be deleted from the database
    • Then the model_delete procedure is called and the user's information is no longer displayed in the table.
    • The functions emails and phones on views.py are used to display the users' emails and phone numbers. First the model_query_emails and model_query_phones procedures are used to call all of the emails and and phone numbers in the database. Then the emails and phone numbers are displyed on the table in index.html.
  • Scrum Board Card

Phylogeny Page (Sophie):

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published