Add/change/delete surrounding delimiter pairs with ease. Written with :heart: in Lua.

nvim-surround

LA CTF hosted by ACM Cyber & Psi Beta Rho! Website for the largest annual cybersecurity competition at UCLA! Whether you are tackling your first exploit or have professional experience, there will be challenges just right for you!

lactf-website

Platform for LA CTF. Forked from redpwn/rctf.

lactf-platform

The official (award-winning) website for ACM at UCLA, the largest tech community on campus!

website

An archive of past challenges from LA CTF hosted by ACM Cyber at UCLA and Psi Beta Rho.

lactf-archive

The home for ACM Cyber at UCLA! Website for the premier cybersecurity club at UCLA.

acmcyber.com

opensource

ACM Cyber's modular script for syncing unified event information across disparate platforms!

cyanea

icpc-website

📊 Website with UCLA grade distributions from 2021-2024

uclagrades.com

A proof verification of "Optimal Implementation of Quantum Gates with Two Controls".

2ControlVerification

Hardware/Firmware for LA Hacks 2022 2nd Place Overall, Best Hardware Hack, Life Hacks Track Winner: An IoT Communal Sharing System

lockr-hardware

A next.js, typescript, react starter repository with built-in linting and github actions for ACM project development!

next-ts-starter-template

XHacks 2021 Startup Track Winner: Be Heard. Educate, Enact, Empower. No voice left behind. (backend)

be-heard-backend

Added the apply button for the nav-bar

Included a boolean variable "IsApplyActive" and a string variable "ApplyButtonClassName" to make it easier to switch the state in the future

Apply Button

uclaacm/hoth.uclaacm.com

@jamesmwu I think maybe it's not showing because it depends on the existence of a `pull_request_template.md` in the branch you're trying to merge into (`main` in this case)? I just tried creating a PR in a test repo after merging a `pull_request_template.md` into `main` and it auto-filled correctly. I think it should work in theory, but not sure how else to test it in this repo...

## Overview
- Created a PR template
- Fixes #485 

## All Changes
- Created `pull_request_template.md` in the root repo directory which should populate all future PR descriptions

## New Bugs/Issues
- None

## Other information
- None

Nishant/pr-template

https://api.github.com/repos/uclaacm/hoth.uclaacm.com/contents/{+path}

MIT License

hoth.uclaacm.com

I don't think this is currently working, unless I'm testing it incorrectly. Do you think you could update it so it would auto-populate for future PRs? I branched off of this branch and created a PR here but didn't see it appear:
https://github.com/uclaacm/hoth.uclaacm.com/pull/490

### 👷 Deploy Preview for *acm-hoth* processing.


| Name | Link |
|:-:|------------------------|
|🔨 Latest commit | 67d12b09831fad994a5d36c4e30b604f829279c4 |
|🔍 Latest deploy log | https://app.netlify.com/sites/acm-hoth/deploys/679f0e7bc1c3f10008ef2408 |

Publish incredibly high performance websites and applications right from GitHub. The Netlify platform connects your repositories to an all-in-one workflow for global CDN deployment, continuous integration, and automatic (and free) HTTPS. Each time you commit changes, Netlify builds your site, prerenders markup, and optimizes assets on dedicated build infrastructure. Easily create an entirely automated workflow around any site generator such as Jekyll, Hugo, or Gatsby.

## Features

### Push your site live, directly from GitHub
Deploy your site to an ultra-redundant global CDN that’s purpose built for serving pages and assets quickly and consistently.

### Automate deployment
Netlify’s built-in Continuous Deployment automatically runs your build commands and deploys the result whenever you push to your Git repository.

### Add a custom domain
Purchase domains and manage DNS zones and records right inside of Netlify.

### HTTPS is automatic
Your site will automatically be secured with a free TLS certificate from Let’s Encrypt.

### Deploy Previews
Netlify’s Deploy Previews streamlined your workflow by giving you a unique, permanent URL to check what your changes will be like in production whenever you submit a pull request.

### And a lot more!
Netlify includes solutions for forms, identity, and even custom functions powered by AWS Lambda. And all this functionality can be configured directly in your repo.


Netlify

James/pr template review

Winner.jsx
- added an empty array for the HOTH-XI winning projects (line 7)
- modified const winners to include HOTH-XI (line 488)

Gallery.jsx
- Included menu item for HOTH XI (line 27)

Jaewook/add hoth xi winner

Discussed in person regarding changes, but please make sure the Gallery properly displays all the winners and their projects. Additionally, please ensure that all previous changes requested are addressed so we can avoid repeating the same feedback. I believe there are also conflicts with the main branch at the moment.

Reach out to @hannahkendall04 if you encounter any issues with the photo carousel failing to display!

This Looks great to me, but would like to hear @ariyin or @melissaqshi 's opinions on the Footer color-- looks somewhat out of place to me, but I don't know what replacement color would be better.

Suggestions would be great :0

### Overview
- Implemented a toggle button in the navbar to switch between light and dark mode across the entire site
- Fixes #470

### Changes
- Added package `react-switch` to get a customizable toggle switch
- Created `DarkModeToggle.jsx` accompanied with `DarkModeToggle.css`
 - Lets user dynamically change coloring theme by adding/removing CSS class `.dark` from `:root` document element
 - Uses `localStorage` to remember user's theme choice upon leaving the website
 - Created a custom toggle switch using new `react-switch` package
- Added the theme toggler to the navbar
 - To ensure that it fit properly with smaller screen sizes, had to change the "global" max mobile screen length from 950px to 1000px
- Added dark mode CSS variables in `src/styles/App.css` under `:root.dark`
 - Also added few more variables to have dynamic color changing based on selected theme
 - Modified CSS files of several pages to make theme changing compatible
 - To add light/dark mode coloring to the FAQ section chevron SVG, I had to add the SVG directly inline in `<AccordionItem>` and get rid of the `<img>` implementation in `src/components/FAQSection.jsx`
 - This was the cleanest solution that I could come up with (I couldn't find figure out how to cleanly add dynamic recoloring to the SVG using the `<img>` implementation after trying every possible method, like using a CSS mask, using different SVG files for light and dark mode, using CSS invert filter, and more)
 - If there's some other method that could work and is cleaner, let me know!

### New Bugs
- None

Nishant/toggle theme

(HOTH XII or whatever the name becomes, if it's HOTH 12)

Update graphics and HOTH XI references to HOTH XII

melissa/updatedGraphicsAndReferences (will work on in dev team meeting)

Changed references and graphics

I noticed that on the Workshops page, we still have "HOTH XI" in some of the descriptions. But I think that's OK since we plan to replace those with the new workshop videos later! But something for us to keep in mind.

LGTM!

Make sure to link the issue that this is related to!

Fixes #459 

### 👷 Deploy Preview for *acm-hoth* processing.


| Name | Link |
|:-:|------------------------|
|🔨 Latest commit | 7fbe2dec51f5e37767b5dc84839b8a025be8420a |
|🔍 Latest deploy log | https://app.netlify.com/sites/acm-hoth/deploys/679f0b29e4e69a0008b8ebed |

Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action

[Automated] Update announcement.json file

This issue follows #458 

The home page should have a popup with the latest announcement, and a button to navigate to the actual announcements page. There should be an internal flag / toggle such that we can choose whether or not we want to enable this popup.

Create announcements popup

Right now we've hardcoded the prize data into Prizes.jsx. Let's store the data instead in src/data using a new file named `PrizeData.js` or similar, and map it.

This is meant to make long term maintenance easier.

Put prize data in src/data

Fixes #475 

put prizeData in the format:

{
    id: 1,
    name: 'Best Overall',
    type: 'overall',
    label: 'PRIZE',
    amount: '$150 Amazon Gift Card'
},

Changed Prizes.jsx to display the exported prizeData array

Created helper function "getPrizeIcon" to fetch the correct prize icon based on the type 



Created data/PrizeData to map prizes to the Prizes.jsx page

For the last commit, I fixed the following errors
- set `isApplyActive` to false
- constant names on Navbar.jsx line 10 & 11 (changed to `applyButtonClassName` and `isApplyActive`)
- changed from `<Link>` tag to `<a>` tag on Navbar.jsx line 88
- removed bold style and changed color to `--hackAccent`on Navbar.css line 88 to 91

I'm not sure why but the 'Fixed previous errors' commit doesn't show the entire changes

Please change this to false. Before rerequesting, make sure that all previous feedback is still fixed.

Ah shoot I missed that, my bad. @dcho-jaewook Please change the button to be inactive.

Before you publish the PR and rerequest review, please make sure that all the feedback previously given is still fixed so we don't need to repeat the same things over again. Thanks!

> > > do we want it to be active rn?
> > 
> > 
> > Nah, Lillian and Max told me to keep it inactive for now since they haven't yet opened for apps
> 
> in the current commit it's active



> > do we want it to be active rn?
> 
> Nah, Lillian and Max told me to keep it inactive for now since they haven't yet opened for apps

in the current commit it's active

> do we want it to be active rn?

Nah, Lillian and Max told me to keep it inactive for now since they haven't yet opened for apps

open source at UCLA

Projects →

Learning →

Events →

Contribute →

featured project

lactf-archive

what we've been doing recently...