the world of musical theater in an organized and interactive way. Visitors can browse a collection of plays, songs, and cast members, with each page connected so you can easily discover more information.
Tong Wu Backend Backend Frontend Frontend Backend/Frontend ★ Created the scraper and filled the database. ★ Made pagination for site. ★ In charge of website deployment on GCP. ★ Made models and attributes for database creation. ★ Created model relationships. ★ Produced unit tests for database. ★ Made initial HTML pages. ★ Created the navigation bar along with filter buttons. ★ Refined and made details to website UI design. ★ Created about page and linked GitLab. ★ Overall site UI designer. ★ Made searching, sorting, and filtering logic/options. ★ Created our API with Postman along with tests. ★ Made initial instances for our models. ★ Added global search feature.
we could do better: What puzzled us: ★ The UI is very smooth and makes it easy to navigate. ★ We have a large selection of plays, songs, and people. ★ Search, sort, and filter logic makes for easy model pinpointing. ★ Thoughtful UI design and implementation. ★ Dynamic website hosting. ★ How to use Flask, SQLAlchemy, and PostgreSQL to create a database. ★ Image quality for models. ★ Implement a larger database. ◦ Ex. some actors don’t have songs for their instance pages. ★ Further refinement of UI and search, sort, filter functions. ★ Website hosting on GCP. ★ Database scraping, populating, and connecting. ★ Dynamic website hosting by using render templates for Flask. (page routes)
they could do better: What puzzels us: • UI and navigation bar: easy to locate and browse models. • Sort/Search/Filter s: user friendly. • Small interaction details (hovering action highlights and expands instances) • Models: Artists, Albums, Songs. • Used API to embed music clips. • Web page doesn’t fit entire screen. • Not all songs have an embedded music clip. • Refreshing any page that wasn’t the homepage would lead to a “Error: Not Found” page.