Skip to content

AntonKL/sitoo-web-admin

Repository files navigation

Sitoo web admin

This is a demo project, build as part of a job application.

The Developer has the floor

For this project I took the opportunity to try out React Hooks and two unfamiliar libraries that I wanted to test out, Final forms React and Antd. While it provided great fun, I many times scratched my head trying to figure how to pass the correct data to the libraries' functions.

It also raised a question on how to structure the project, the good ol' container/component pattern that always helpt us separating concerns seems obsolete in a Hooks world. Even Dan Abramov states that this is probably the case. How is the future going to look like in terms of reusability? While I do not hold all the answers, I decided to go with a more scene-based approach for this project. In the end, I found myself spending less time jumping around in folders, and it felt pretty straight forward, considering it was my first dedicated Hooks project.

How to run the project

  1. Clone project
  2. !IMPORTANT! Setup your Sitoo API-key according to instructions in this readme.
  3. Follow this instructions for setting up a CORS-proxy. Proxy needs to be running in the background all the time to make requests work.
  4. cd into your project
  5. npm i
  6. npm start

Setup API key

The project uses dotenv to provide file with enviromental variables during build time. Here's how you set it up:

  1. Rename .env.example => .env
  2. Enter your API-key in .env REACT_APP_SITOO_API_KEY=${enter your sitoo api key here}

Please note that you need to restart React Create App server after each change to .env-file.

Deps

  • Node.js (project built with v10.15.1, but might run with other versions as well. No guaranties. Stuff can break

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published