1. Node JS LTS | current version - 20.9.0
2. Node Package Manager (NPM) | current version - 10.3.0
3. Node Version Manager (NVM) | current version - 0.39.5
4. React LTS | current version - 18.2.0
5. Github account with no deployed websites (?)

1. Clone files locally by copying http link and in terminal running git clone HTTP_LINK_COPIED
2. The root folder of the cloned repository should have the following:
   • CNAME
   • package.json
   • index.html
   • readme file
   • sitemap.xml
   • wisreactapp folder

In the Root Folder of your Locally Cloned Repository:

1. Download the LTS version of Node JS
2. To check if NodeJS installed, open terminal and use command node -v
3. Install nvm using command curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
4. To check if nvm is installed, open terminal and use command nvm --version
5. NPM comes when you install Node JS. To ensure it is installed, run the command npm -v
6. cd into the wisreactapp folder, then run the npm i command. This will install all node modules being used in the React app.
   • NOTE: Ensure you have node_modules in your .gitignore within your React App file. This will ensure you DO NOT push tens of thousands of modules to the GitHub Repository.
7. While still in the wisreactapp folder, install bootstrap (css) using command npm install react-bootstrap@next [email protected]

1. In terminal, make sure you cd into the wisreactapp folder
2. To run locally, type npm start
3. The website should open on your local host, and you are now ready to make changes and see these changes dynamically!

1. Make sure you are on the main branch, and that all the changes you want are pushed and merged with main
2. Make sure site runs correctly locally by cd into the wisreactapp folder and running npm start
   • Fix any issues if they exist and push these changes
3. To begin the deployment process, make sure you are cd into the wisreactapp folder
4. Make sure github pages package installed: npm install gh-pages --save-dev
5. In both package.json files (root folder and the wisreactapp folder), update the first line "homepage": "https://USER_NAME.github.io/REPOSITORY_NAME"
   • You should be able to find the exact link after deploying on github pages
6. Make sure the "scripts" line looks like this: "scripts": { "predeploy": "npm run build", "deploy": "gh-pages -d build", }
7. In terminal type npm run build. Let that compile, then enter npm run deploy
8. Go to GitHub in your browser. Navigate to the repository, then the Actions page
9. Wait for the "pages build and deployment" workflow run to finish
10. Click on the workflow run when it is completed successfully, and the link to your website will be there. Click on it to view your website live!
11. As mentioned in Step 5, this link is going to be what you will insert into the "homepage" line of your package.json files.

1. After making a change to local files, cd into general file
2. Type git add . to add all changes, you can replace . with specific file
3. Type git commit -m
4. Type git push origin main or just git push

1. Purchase from a domain manager site
2. Verify domain name on github (this may take up to 24 hours)
3. On domain managers site, find the Manage DNS page
4. Add 4 A records: Under each ipv4 title add:
   • 185.199.108.153
   • 185.199.109.153
   • 185.199.110.153
   • 185.199.111.153 These point to the location of the github deployment
5. Under CNAME record:
   • Hostname should contain www
   • Name should contain name of root repository - eg. USER_NAME.github.io
6. Add TXT record
   • Hostname should contain _github-pages-challlenge-YOUR_ACCOUNT_NAME
   • Name should contain the numbers given from verified domain name You should end up with 7 records total - 4 A, 2 TXT, 1 CName
7. In your locally cloned repository, navigate back to the "homepage" line of both package.json files and replace the github.io link: "homepage": "https://YOUR_DOMAIN/"
8. Open GitHub on your browser and navigate to your repository Settings -> Pages
9. Scroll down and enter your custom domain. Click "Save". A DNS check will begin which may (unlikely) take up to 24 hours.
10. Navigate to the Actions page of your repository. You should see the new workflow run for the deployment
11. Once the workflow run is complete, click on it and you should see the link to your live website. If the DNS check succeeded, your website should load correctly!

1. In the locally cloned repository, ensure you are currently on the main branch and that it is updated as you wish
2. cd into the wisreactapp folder
3. In terminal enter npm run build. Let that compile, then enter npm run deploy
4. Wait for the "pages build and deployment" workflow run to finish
5. Click on the workflow run when it is completed successfully, and the link to your website will be there. Your website should load with the updated changes (Note it may take a few minutes for the updates to be visible after redeploying)! IF YOU HAVE A CUSTOM DOMAIN:
6. The link generated by the workflow run will not work. It will be a github.io link. You must navigate to your repository Settings -> Pages
7. Scroll down and enter your custom domain. Click "Save". A DNS check will begin which may (unlikely) take up to 24 hours.
8. Navigate to the Actions page of your repository. You should see the new workflow run for the deployment
9. Once the workflow run is complete, click on it and you should see the link to your live website. Your website should load with the updated changes (Note it may take a few minutes for the updates to be visible after redeploying)!

Once the website is up and running, you need to make sure it is findable on google search.

1. Go to google search console and type in domain name for verification
2. It will redirect to domain name provider and add a text file
3. Wait for a few hours then you should be able to verify the domain
4. Once domain is verified, check if it is indexed or not. Indexed means you can find it through google search and unindexed you can't
5. If unindexed, check reason and meaning of reason at google's faq page
6. You may need to create a site map depending on issue -> Creating a sitemap needs to be using xml file
7. Put the xml file into the root of the repository and push changes

1. Create a new .jsx file in the wisreactapp/src/components folder
2. Add the code for your new section. Follow the format of the other components for consistency
3. Add the new page to the App.jsx file in the wisreactapp/src folder
4. Add the new page to the navigation.jsx file in the wisreactapp/src/components folder
5. If you are confused on how to format, just follow what was done for other landing page components (eg. Team.jsx)

1. Create a new .jsx file in the wisreactapp/src/components folder
2. Add the code for your separate page. Follow the format of the other components for consistency
   • Ensure the new section uses the navigation2.jsx nav bar rather than the normal navigation.jsx nav bar
3. Add the new page to the App.jsx file in the wisreactapp/src folder, as a route under the App function
4. If you are confused on how to format, just follow what was done for other separate pages (eg. calendar.jsx)

1. To adjust or remove the loading screen, navigate to the App.jsx file in the wisreactapp/src folder. The logic can be found here
2. To adjust the styling of the loading screen, navigate to the style.css file in the wisreactapp/public/css folder, and do ctrl-f "loading". This will bring you to the location of the styles
3. To add a loading symbol to a specific element on the website that takes a while to load, follow the logic found in the Calendar.jsx file in the wisreactapp/src/components folder

1. Use navigation.jsx for any components that should be accessed via the landing page
2. Use navigation2.jsx for any separate pages. This nav bar contains only the WOMEN IN SCIENCE link that will take you back to the landing page

1. To update the events section, first obtain the square png or jpeg image of the event you would like to display on the website
2. Add this to the wisreactapp/public/img/Portfolio folder
3. Navigate to the data.json file in the wisreactapp/src/data folder
4. Scroll down to the "Gallery" object. Currently, we keep 6 Current events and 6 Past events. You can change this however you like. To add the most recent event, add a section of code like this to the very top/beginning of the "Gallery" object: { "title": "Name of Event", "largeImage": "img/portfolio/ImageName.png", "smallImage": "img/portfolio/ImageName.png", "eventType": "current" },
5. If you want to keep only 6 Current events and 6 Past events, remove the very last section of the "Gallery" object. Set the "eventType" of the last "current" event with "past".
6. Check your locally running copy to ensure the new event has been added, then push your changes!