Skip to content

BarbaraShea/ProseAndShows

Repository files navigation

ProseAndShows

ProseAndShows

Prose and Shows is a web application that provides a space for bibliophiles and cinephiles to come together to recommend and discover books, shows, and films.

Link to Deployed Application

Prose & Shows

User Story

As a bibliophile or cinephile:

  • I want to connect with others online about books, tv shows, and movies.
  • I want to create posts so that I can recommend my favorite books, shows, and films.
  • I want to read recommendations about other users' favorite books, shows, and films.
  • I want to be able to search for recommendations based on keywords.
  • I want to see trending topics and genres.

Goal

As developers:

  • We wanted to build a site that showcased our knowledge of MVC structuring.
  • We wanted to build a site that utilized an API that we built, as well as Third-Party APIs.
  • We wanted to build a site with a sleek, clean design that would be eye-catching and easy to use.

Technologies Used

  • JavaScript
  • Express.js
  • Handlebars.js
  • Node
  • Materialize CSS
  • Sequelize
  • Google Fonts

Work Completed

  • Barbara worked on the Modules. She also handled MySQL and seeds, worked on JavaScript, and put together our presentation.
  • Taylor worked on the Controllers and setting up our routes.
  • Teisha worked on the Views, setting up our different Handlebars.js pages. She also created this READ.ME.
  • Joel worked on Heroku Deployment and JawsDB.

Learnings and Issues

Some of the learnings we're taking away from this project are:

  1. How to use Github in a team environment. Although we'd had experience working on a group project in the past, many of us found this project to be a little more difficult to use with Github. Having several folders and files meant that there was more room for file conflict. In particular, our .env file always got pushed up to the main branch, although it was listed in our gitignore. This means that group members' MySQL passwords were exposed, and it was also inconvenient to update that file after every pull from the main branch.
  2. In our first meeting, we didn't have a clear vision for our UI and never really flushed out the details of it. Creating Views without a real idea of what our pages should look like and what should go on them was difficult. Also, CSS was one of the last parts of the projects we completed, because it was difficult for us to all get on the same page about what the site should look like.
  • Thoughtful delegation of tasks would have made for a better start.

Future Application Updates

  • Making the results of the Recommendation search more relevant, or ordering by popularity.

Contributors

Barbara Kenny, Joel Benson, Taylor Lilley, Teisha McRae

Website Screenshot

Website Screenshot

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •