Giter VIP home page Giter VIP logo

membership-portal-ui's Introduction

ACM at UCSD: Membership Portal UI

This is the frontend repository for the ACM at UCSD membership portal. The live portal is viewable at: https://members.acmucsd.com.

See https://github.com/acmucsd/membership-portal for the portal backend.

Setup

Install Node and npm: https://nodejs.org/en/. Builds are currently run on version 14.18.2, but the LTS and Current versions should also work.

Install yarn: npm install -g yarn. Builds are currently run on 1.22.11, but any version should also work.

Running

Clone the repo: Run git clone https://github.com/acmucsd/membership-portal-ui.git in a terminal.

Install packages: Run yarn or yarn install to install the node modules.

Run the portal: Run yarn start to run the portal with the development environment variables. The page will be available at localhost:8080.

Currently the portal is deployed as-is using yarn build on Netlify.

Issues

  • Add on Github, including a title, description, screenshots if applicable

  • Label the applicable issue type.

  • If you’d like to work on that specific issue, assign yourself.

  • If not, it will get assigned during development meetings.

PRs

  • Every PR should have a corresponding issue it’s tied to. You can link by using the phrase “Resolves #XX.” in the PR description, or in the GitHub sidebar. Assign yourself to the PR.

  • Tag the PR as “PR: Needs Review” and request a review from the portal PM.

  • If the PR is approved, go ahead and merge the PR into the repo.

  • If the PR isn’t approved, check the comments for feedback / suggested changes. When you merge, the branch will be deleted automatically.

Coding

  • When working on the portal, start by creating a new branch based on master. Add all commits to this branch, and then you can create a PR from there.

  • There should be one feature/bugfix per branch.

  • If you’re working on the portal in parallel with someone else and end up with PR conflicts / merge issues, contact the portal PM via the Discord server.

  • If you are working on an overarching feature/refactor, make a separate branch from master and try your best to rebase to master whenever applicable.

membership-portal-ui's People

Contributors

alexzhang1618 avatar annsudhart avatar cgcha avatar coraxyc avatar dependabot[bot] avatar duanwilliam avatar eminguyen avatar falafel72 avatar farisashai avatar imgbot[bot] avatar jvil26 avatar leestanley avatar ohharsen avatar paulpan05 avatar raymosun avatar ryan-truong avatar shravanhariharan2 avatar steets250 avatar stonet2000 avatar stormfirefox1 avatar sumeet-bansal avatar trevorkw7 avatar trulyronak avatar wishingwell13 avatar yesean avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

membership-portal-ui's Issues

Create registration form

Should be similar to #5. Also, don't worry about giving it functionality. That'll be done in the registration page issue. This issue should mainly cover laying out the component, anywhere where you would usually put a function call (such as submitting the form) should just be replaced with a prop

Update README

Our coverage badge literally says 100% coverage because it's for a branch that no longer exists woops. Also should probably include a guide on how this is deployed.

Handle users who forget their password

Low priority, I'll probably add labels to issues for priority later. Just handle this however you want, it can be through sending them an email or a text message for verification. You can also have them meet with a Board member to be able to change their password? The choice is yours but don't worry about this unless you have absolutely nothing else to do

Add ESLinting

Why

We can solve coding bugs that can lead to problems not easily checked by us, and we can combine it with prettier to ensure proper code styling

How

Use Airbnb's ESLint config and make sure it works with prettier.

Note

We should NOT enforce eslint for now since we're in crunch time, but after the portal ships we should prohibit code from being pushed without passing eslint (as a commit config / or push hook or something)

Populate upcoming events list

This will include connecting to the backend to find upcoming events. I'm adding Casey to this PR also because she wants to join in on the project and she has a bit experience doing something similar to this with the URL shortener

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.