Philamuseum.org
My main responsibility in this project was to create the website's front-end. However, I was also heavily involved in the back-end processes, including the architecture of the entire site, the development approach, user-experience, and design reviews. I transformed the previous monolithic architecture into a micro-service architecture by decoupling the front-end and back-end and selecting appropriate web solutions for each challenge. I used React to develop the front-end, with Server-Side Rendering features, and managed the back-end through Sanity. Additionally, I created APIs to provide collection data and search functionality. This project was one of the most significant accomplishments in my career as a developer.
ElasticSearch
ElasticSearch has played a crucial role in driving the dynamic content and search functionality of the philamuseum.org website. While it was primarily utilized as a search tool, it was also carefully calibrated to deliver content based on managed scoring and relevance. In addition, a combination of front-end and back-end API calls were developed to establish a predictive search feature.
Calendar
ElasticSearch was leveraged to support the calendar feature on the website. This involved utilizing its content aggregation, filter, and date range capabilities.
Object Page
From a technical standpoint, the object pages required a complete overhaul. The goal was to enable visitors to zoom in on the artwork and encourage them to learn more about it by presenting similar objects and additional information. I sourced the data from various outlets, with primary object data being obtained from Google FireStore through a Cloud Function. The images were served via a Micr.io IIIF image server, while ElasticSearch and Sanity.io CMS were utilized to manage additional content enhancements.
