on strengths and weaknesses • Work cohesively to enhance each other’s pages • Communicate consistently to ensure jobs got done well and team members were up to date on current issues • Flip card effect for book summary was very creative • Creative theme and pictures • Easy to follow on what page you’re on, and what column you clicked to sort
Displaying information by extracting from other pages (github and issues/commits) • Usage of GitHub to collaborate with other coders • Implementation of BootStrap • Proper project documentation using github issues and the github technical report
creative link design for “Go to author” and “Go to publisher” • If we added multiple cases of each instance, we would have to set up the model pages different • Add more cases
be linked to our website to load in massive amounts of books? • When a user clicks on the issue tracker icon they can go on our github and create/close issues. How can we prevent that?
page is very well organized and split up, making it easy to read. • Embedding of music video on song pages is great. • Inclusion of social media accounts for artists and labels is a nice touch. • Linkage between songs, artists, and labels is very well implemented and smooth. • Included plenty of artists, songs, and companies which gives viewing that tables pages a better feel.
• We could’ve made the links like them, where the artist name or song is the link rather than just use “Go to author” and “Go to publisher” • We learned how to embed videos using the iframe tag
out a way to automatically update commits/issues, the numbers didn’t match between the individual contributions, the overall number, and the tracker • Make individual song pages more aesthetically pleasing, white background is dull • Could leave “Image” column heading off about page. Kind of self explanatory. • Use logos of tools used instead of naming the tools • Make homepage fit to page so you don’t have to scroll to see the bottom of the picture