• Runs on the same infrastructure that Google uses internally for its end-user products, such as Google Search and YouTube. • Used domain provided by NameCheap Hosting
• Postgres What did we do well? • Search and sort functionality • Immaculate and beautiful layout • Relevant links easily available on all pages • Our backend code is very well documented and clean Our Website
affect our website in the end, it would have been better to implement three separate data tables instead of our one large one to show mastery of the course. If our dataset had been larger we would have wasted too much memory by using one data table. What puzzled us? • We had trouble figuring out how to implement our unit tests on the website, and our initial confusion regarding an instance vs. a database on GCP proved to be a hindrance for quite some time • Putting calls for distinct authors in our flask page as opposed to our publishers html page. Our Website
- easy to navigate • Parallax effect looked great • Consistent theme • Creative name What could they have done better? • Search bar on the splash page doesn’t link properly • Formatting inconsistencies - text alignment • Odd formatting for the specific pages - exchange length for width • Cover photo doesn’t have anything to do with books • Could rename to “CAJAN” for dual recipe-book website potential Group 2 - CANJA Books