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 the browser.
The page will reload if you make edits.
You will 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 project uses Imgur API and its documentation. However, I encountered many API limitations while creating this solution and some configurations weren't as described in the documentation...
To run the application you need to register your application here, then update your .env (remember, copy .env.example and rename to .env) file with your credentials, we are using only Anonymous usage without user authorization here.
After getting your Client-ID and updating the .env you can just use yarn start.
The CSS architecture is simple, for this specific case, mobile first wasn't required.
The user can filter options "section", "sort" and "window" on the top menu; back to the top with an arrow in the corner of the page and change pages at the end of the application.
Tests aren't finished, but a simple case was written to check if the app renders.