Personal Website of Adam Mihajlovic

Personal Website made to show my work resume in a more beautiful format. It uses the framework Gatsby for the front-end which is based on react but with styled-components. For the back-end, it's using strapi to manage the content of this website in relation with cloudinary to manage media and postgres to host the data itself.

The front-end of the website is currently hosted on vercel and the back-end is hosted on a home-server via http. To view it, go to adammihajlovic.ca.

The Strapi back-end is hosted from home on home.adammihajlovic.ca/admin in order to make changes wherever I am.
(Needs a password for access by the way 😉)

For more information please feel free to contact me with my information provided on the website: adammihajlovic.ca

🚀 Quick start (To run this locally)

1. Prerequisites

   Install both Gatsby's and Strapi's CLI to run the servers.

   # installation
   npm install -g gatsby-cli
   npm install -g strapi
   
   # verify installation
   gatsby-cli -v
   strapi -v

2. Environment variables

   Navigate to the /server folder and make sure you have a .env file containing the following:

   APP_KEYS=""
   HOST=127.0.0.1
   PORT=1338
   JWT_SECRET=""
   ADMIN_JWT_SECRET=""
   API_TOKEN_SALT=""
   
   CLOUDINARY_NAME=""
   CLOUDINARY_KEY=""
   CLOUDINARY_SECRET=""
   
   DATABASE_HOST=""
   DATABASE_PORT=
   DATABASE_NAME=""
   DATABASE_USERNAME=""
   DATABASE_PASSWORD=""

   When this is done, navigate back to the source folder and go to /client and make sure you .env file contains the following:

   STRAPI_TOKEN=""

3. Installing dependencies and building project

   Start by making sure everything is up-to-date. Both in the /server and the /client folder, run

   # install dependencies
   npm install
   
   # build application
   npm run build

4. Running the back-end

   Start by running the back-end (Strapi) by running the following command in the /server folder:

   # start in production mode 
   npm run start
   
   # OR
   # start in development mode (with schema modifications enabled)
   npm run develop

   Your Strapi content-manager should now be running at http://localhost:1338!

5. Running the front-end

   Then to run the front-end (Gatsby), run the following command in the /client folder:

   # start in production mode 
   npm run start
   
   # OR
   # start in development mode (with auto-reload)
   npm run develop

   Your site is now running at http://localhost:8000!

   Note: You'll also see a second link: http://localhost:8000/___graphql. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the Gatsby Tutorial.

🧐 What's inside?

A quick look at the top-level files and directories you'll see in a Gatsby project (Front-end).

.
├── node_modules
├── src
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-ssr.js
├── LICENSE
├── package-lock.json
├── package.json
└── README.md

1. /node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.

2. /src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template. src is a convention for “source code”.

3. .gitignore: This file tells git which files it should not track / not maintain a version history for.

4. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.

5. gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.

6. gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the config docs for more detail).

7. gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.

8. LICENSE: This Gatsby starter is licensed under the 0BSD license. This means that you can see this file as a placeholder and replace it with your own license.

9. package-lock.json (See package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won’t change this file directly).

10. package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.

11. README.md: A text file containing useful reference information about your project.

🎓 Useful information

Looking for more guidance?

• Documentation for Gatsby.
• Documentation for Strapi.