React based website for the Hispanic Association of Computer Scientists. Allowing our members to be able to contribute to the website and gain experience with industry tools.
You will need:
- node.js
- yarn
- git
- a text editor of your choice or IDE. Brackets, VSCode, and Webstorm are all great.
You can get node.js from https://nodejs.org/en/. MacOS can also get it using homebrew.
That should also have installed npm for you.
You can install yarn at https://yarnpkg.com/en/.
You can find git if you don't have it already at https://git-scm.com/downloads .
We will post a tutorial on git shortly, but you can also check this one here.
Clone the repo. Put it somewhere more permanent than the Downloads folder. Navigate in terminal/powershell to the project and use
yarn install
This installs all packages/libraries you currently needed for this project locally. You can start the development server with
yarn start
This is a script in the package.json file. It's function is to start up webpack and a developer server where your changes will be watched and automatically recompiled so you can see them live. If a tab isn't opened automatically, you can go to
http://localhost:8080/
Feel free to mess around with the code and see what happens.
Check out our todo list:
This is our tentative sitemap
In order to have a consistent flow with developer branches we need to implement a naming convention on new branches, as well as a step by step approach to merging and pull requests.
developerName-feature
# Example
robert-announcement-queries- Push your branch's code to GitHub.
- Create a new Pull Request.
- Set the base branch to 'master' and the compare branch to your personal branch.
- Request others to review your code.
- After review, your code will be merged by designated Git Master.
- Finish fleshing out the how to contribute section
#People:
- Jesus Palos
- Andrew Marquez
- Jesus Luna
- Earl Potts
- Manuel Ponce
- Alberto Aviles-Correa
- Pamela Vazquez
- Santiago Cortes
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.
Starts up both local backend server and the app in development mode. Compatible with macOS and linux machines.
Starts up both local backend server and the app in development mode. Compatible with Windows machines.
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.