- Make sure Git and NodeJS is installed
- Clone this repository to your local computer.
- Create .env file in root folder.
- Contents of .env:
REACT_APP_SANITY_PROJECT_ID=XXXXXXXXXXXXXXXX
REACT_APP_SANITY_DATASET=XXXXXXXXXXXXXXXX
REACT_APP_SANITY_TOKEN=XXXXXXXXXXXXXXXX
- Open terminal in root directory. Run
npm installoryarn install. - Now,
cd backend-sanity. Runnpm installoryarn installagain. - Now all required packages are installed, let's setup sanity.
- Create an account in sanity.
- In terminal, type
sanity initto initialize our sanity project. - Type
sanity startto start sanity studio on localhost. URL will be shown in terminal. - After going to localhost, login in with your account. Now, your account is connected with this project.
- To get REACT_APP_SANITY_PROJECT_ID and REACT_APP_SANITY_TOKEN, go to sanity.
- Copy your project id as shown below:
- Under API Tab, go to tokens section and create a token. You can name it whatever you want. Just Don't forget to copy your project token. You will not be able to copy later.
- Now, you add your portfolio details to your project through sanity localhost.
- Now app is fully configured 👍 and you can start using this app using
npm startoryarn start.
NOTE: Make sure you don't share these keys publicaly.
You might encounter some bugs while using this app. You are more than welcome to contribute. Just submit changes via pull request and I will review them before merging. Make sure you follow community guidelines.
You can also give this repository a star to show more people and they can use this repository.
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
