Information regarding the pages:
Artworks page: The Artworks page displays a curated collection from the Museum of Fine Arts Houston. Users can search or browse through the artworks, each presented in a card with a "Show Details" option. Clicking this button reveals additional information, such as the artist's name, medium, dimensions, and style. The page features a search function for filtering by title, and the design ensures that expanded details remain visible while interacting with other artworks, providing a seamless exploration experience.
Exhibition page: The Exhibitions page presents a selection of exhibitions at the Museum of Fine Arts Houston. Users can explore ongoing exhibits and filter them by start date, allowing them to plan visits based on their preferred timeframe. The page features a date selector for filtering exhibitions and a "Reset" button to clear filters. Each exhibition is showcased in a card format, displaying its name, start date, and end date. The design provides a straightforward and user-friendly interface for discovering and attending museum exhibitions based on individual preferences and schedules.
Front Page: The front page warmly welcomes users to MFAH, where they can explore the latest artworks and exhibitions recently added to the museum.
Admission Page: The admissions page allows users to purchase tickets for specific exhibitions or general admission. Users can select the desired number of tickets, and to complete the checkout process, they need to log in to receive their receipt. Once logged in, they can choose a payment method, proceed to checkout, and finalize their purchase.
Gift Shop Page: Similar to the admissions page, users can choose their preferred items from the gift shop. They are required to log in before checking out, and after confirming their payment method, the transaction is complete.
Customer Landing Page: On the customer landing page, users can conveniently view their recent orders.
Not Authorized Page: If users attempt to access pages without the necessary authorization, such as customers trying to access admin pages, they are redirected to the not authorized page. This informs them that they do not have the credentials to view the requested page.
Not Found Page: In the event that a user enters a route that doesn't exist, they are redirected to the not found page. This notifies them that there might be an error in their route.
Employee Pages (Landing Page): Pages that give employees and admins access to database CRUD operations. Allows employees to carry out their functions in relation to the database. Admins gain access to deletion requests to the database. while employees do not have this privilege.
Sample employee pages locked behind login -
(Employee Info):
(View and edit artworks):
(View and edit gift shop items):
(Manage employees as an Admin):
(Generate reports):
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can't go back!
If you aren't satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you're on your own.
You don't have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn't feel obligated to use this feature. However we understand that this tool wouldn't be useful if you couldn't customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify