Skip to content

Latest commit

 

History

History
86 lines (51 loc) · 6.08 KB

README.md

File metadata and controls

86 lines (51 loc) · 6.08 KB

Introduction

This is an independent portfolio project built using React.js and leverages TanStack Query and Router, TailwindCSS and Mock Service Worker. The focus of this project is to demonstrate my React proficiency and ability to learn and implement new libraries and APIs effectively.

Motivation

From the outset, Musee was designed as a front end only demo app, embracing an iterative and spontaneous development process. Even without a backend API, the project is structured in a way that allows for potential smooth integration with an app server in the future.

This project has allowed me to focus on core frontend development skills, particularly in working with APIs, and creating user-friendly UIs. By adopting an iterative approach, I've navigated challenges as they arise, thereby strengthening my problem-solving skills and my proficiency in modern front end technologies.

Key Features

Landing Page

Inspired by the beautiful world of fine art, Musee is a web app that allows users to explore paintings from the Art Institute of Chicago.

The key features of Musee include:

  • A gallery showcasing 200 of the Art Institute of Chicago's public domain paintings:

Gallery Page

  • A detailed view for each painting that provides more information about the artwork including a link to the AIC page for the painting:

Painting Page

  • The ability to favorite paintings so that users can create their own personalized collections:
Favorites page on mobile
Mobile View

Learning Journey & Technical Challenges

  1. Getting Back into React Development and Embracing New Libraries
    After a gap in web development, I chose this project as part of getting reacquainted with React and modern front end tools. I intentionally selected TanStack's Query and Router, and Tailwind CSS, despite my previous experience with React Router, Redux, and Bootstrap. This challenge provided an opportunity to get hands-on with different libraries and enhance my adaptability as a developer.

  2. Styling with TailwindCSS and daisyUI
    Given my self-proclaimed weakness in styling, adopting Tailwind CSS was a deliberate decision to push myself and improve my styling skills. I supplemented Tailwind with daisyUI to accelerate the process. This venture improved my CSS understanding and utility-first design approach, even though styling remains an area of further growth.

  3. REST API Development with Mock Service Worker
    In the absence of a backend API server, I simulated one using Mock Service Worker. This created a mock REST API for the application, allowing me to design and fine-tune front end behavior and user interface based on simulated server responses. This experience not only added to the project's complexity but also prepared me for potential future integration with an actual backend server.

  4. State Persistence
    One of the crucial aspects of Musee is state persistence. This was achieved by leveraging local storage and URLs, a strategy which not only enhances the user experience but also introduced me to advanced state management techniques. This allows users to bookmark or refresh their pages without losing their place in the application, thereby providing a smoother browsing experience. This state persistence was also crucial in implementing the favorites feature.

  5. DevOps and CI/CD
    One of Musee's development goals was to introduce robust DevOps practices through setting up continuous integration and deployment (CI/CD). Building a CI/CD pipeline was a challenging and rewarding process. It involved learning to configure GitHub workflows, understanding how to automate testing and code style checks with tools like ESLint, and setting up automatic builds and deployments to GitHub Pages. These practices were crucial in maintaining high code quality and ensuring smooth, automated deployments.

  6. Embracing Testing Practices
    Given Musee's iterative development and my initial focus on new libraries, I prioritized feature implementation. However, understanding the importance of testing, I back-filled tests after core functionalities were built. This approach allowed me to validate Musee's stability, improve code quality, and further familiarize myself with testing tools like Vitest and React Testing Library.

Technical Details

This is a TypeScript React app that is built with Vite. Supporting libraries include:

Mock Server

The frontend is designed to interface with a backend API server, simulated via Mock Service Worker.

Data

To better align with my goal of maintaining proficiency in Python - my secondary web development language - Python scripts were employed to fetch and process data from the Art Institute of Chicago's API. In a future enhancement of the project where a server is to be added, it would likely be written in Python. However, for now, the processed data is served as static Github pages files.

Testing and DevOps

Testing is conducted using Vitest and React Testing Library.

Separate Docker containers are used for the TypeScript frontend and the Python scripts. A Makefile is used to provide convenience Docker commands.

To support a robust development process, a CI/CD GitHub workflow is implemented. This workflow is configured to run tests, check the code style with Prettier and ESLint, and automatically build and deploy the application to GitHub Pages whenever changes are merged into the main project branch.

Contact

Email: monocle.github@gmail.com