4 | JOIN US 5 |
6 | ); 7 | }; 8 | 9 | export default Header; 10 | -------------------------------------------------------------------------------- /src/app/programs/overview/page.tsx: -------------------------------------------------------------------------------- 1 | import WhatWeOffers from "@/components/programs/whatweoffers"; 2 | 3 | const Programs = () => { 4 | return ( 5 | <> 6 |4 | MEET THE BOARD 5 |
6 | ); 7 | }; 8 | 9 | export default Header; 10 | -------------------------------------------------------------------------------- /src/components/about/header.tsx: -------------------------------------------------------------------------------- 1 | const Header = () => { 2 | return ( 3 |4 | ABOUT US 5 |
6 | ); 7 | }; 8 | 9 | export default Header; 10 | -------------------------------------------------------------------------------- /src/utils/error.ts: -------------------------------------------------------------------------------- 1 | class Fault extends Error { 2 | name: string; 3 | code: number; 4 | 5 | constructor(code: number, name: string, message: string) { 6 | super(message); 7 | this.name = name; 8 | this.code = code; 9 | } 10 | } 11 | 12 | export default Fault; 13 | -------------------------------------------------------------------------------- /next.config.js: -------------------------------------------------------------------------------- 1 | /** @type {import('next').NextConfig} */ 2 | const nextConfig = { 3 | output: "export", 4 | reactStrictMode: true, 5 | images: { 6 | loader: "akamai", 7 | path: "", 8 | unoptimized: true, 9 | }, 10 | basePath: "", 11 | assetPrefix: "", 12 | }; 13 | 14 | module.exports = nextConfig; 15 | -------------------------------------------------------------------------------- /src/components/alumni/cards.tsx: -------------------------------------------------------------------------------- 1 | import alumni from "@/data/alumni"; 2 | import Dropdown from "./dropdown"; 3 | 4 | const Cards = () => { 5 | return ( 6 | <> 7 |8 | OUR ALUMNI 9 |
10 |{name}
12 |{description}
13 |{name}
16 |22 | PROJECT GALLERY 23 |
24 |21 | FREQUENTLY ASKED QUESTIONS 22 |
23 |15 | USED IN 16 |
17 |7 | HACKPACKS 8 |
9 |10 | WHAT ARE HACKPACKS? 11 |
12 |13 | Hackpacks are GitHub templates with pre-configured starter code, designed 14 | to get you up and running fast without the hassle of setup. Whether you're 15 | at a hackathon or starting a new project, hackpacks provide an 16 | out-of-the-box foundation so you can focus on building. 17 |
18 |25 | FOLLOW OUR INSTAGRAM{" "} 26 | 31 | @ACM_UCR 32 | 33 |
34 | 35 |14 | WHAT WE DO 15 |
16 |17 | DAS aims to analyze, experiment, and explore data across various of 18 | fronts and domains! Our goal is to expose you to skills working with 19 | big data ranging from statistical hypothesis testing to designing 20 | machine learning models! 21 |
22 |16 | {position} 17 |
18 |{name}
19 |{title}
31 |{date}
32 |33 | {location} - {startingTime} 34 |
35 |{description}
41 |9 | WANT TO GET INVOLVED? 10 |
11 | 17 | Join our Discord! 18 | 19 |22 | CHECK OUT OUR WORK! 23 |
24 | 30 | Github 31 | 32 |13 | CURRENT OPPORTUNITIES 14 |
15 |{title}
21 | 27 |{description}
31 |TECH STACK
33 |8 | PROGRAMS 9 |
10 |11 | ACM offers four project oriented programs, each with their own focus— 12 | such as web development and robotics--and one mentorship program. Our 13 | programs typically run quarterly. We strive to cover a wide variety of 14 | topics for our members to explore their interests! Take a look below! 15 |
16 |17 | WHAT WE OFFER 18 |
19 | {whatWeOffer.map( 20 | ( 21 | { header, program, acm, pText, textColor, linkColor, image, link }, 22 | index, 23 | ) => ( 24 |18 | PAGE NOT FOUND 19 |
20 | 24 | Go Back Home 25 | 26 |WHAT WE DO
14 |15 | Participants attend weekly stand-up meetings and work on assigned 16 | issues throughout the week. Issues will begin with developing the 17 | website's overall structure, responsiveness, and end with animations. 18 |
19 |21 | Weekly meetings are held covering all related tech-stack curriculum from 22 | TailwindCSS styling to motion.dev animations. By the end of the program, 23 | a fully functional website is developed by the team. 24 |
25 |8 | WANT TO GET INVOLVED? 9 |
10 | 15 | Join our Discord! 16 | 17 |20 | CHECK OUT OUR BLOGS! 21 |
22 | 27 | Medium 28 | 29 |32 | CHECK OUT OUR CODE! 33 |
34 | 39 | Github 40 | 41 |OUR VISION
34 |35 | Our Vision is simple: We want to improve our members professionally, 36 | technically, and personally. We want to help our members grow 37 | throughout their college career, whether they enter as a first-year 38 | university student or as a transfer student. 39 |
40 |29 | {position} 30 |
31 |{name}
39 |WHAT WE DO
17 |18 | Participants attend weekly design meetings and collaborate closely 19 | with leads and club ambassadors to create a wireframe — from color 20 | palette to all pages — complete with information and details. 21 |
22 |25 | We also host biweekly workshops on UI/UX principles and Figma 26 | proficiency, and we are open to anyone interested in learning more about 27 | design. By the end of the program, the website design will be finalized 28 | and ready for implementation by Spark in the following quarter. 29 |
30 |34 | WHY WE DO IT 35 |
36 |37 | We want UCR to become a premier institution for Computer Science and 38 | Engineering. University courses provide a good foundation, but we 39 | strive to build upon that. But more importantly, we want our members 40 | to make a positive difference in the world through software. 41 |
42 |35 | {title} 36 |
37 |53 | {header} 54 |
55 |{subtitle}
56 |25 | Join Now 26 |
27 |41 | {isLoading ? "Loading..." : status} 42 |
43 | )} 44 |48 | WHAT WE DO 49 |
50 |51 | We connect multiple students with a mentor to be advised throughout 52 | one school year. During this period there will be different social and 53 | activities hosted to help foster a deeper relationship between the 54 | mentor and mentees.{" "} 55 |
56 |23 | PHOTO GALLERY 24 |
25 |WHAT WE DO
16 |17 | Participants will work closely with their peers and leads, engaging 18 | with other sub-teams to improve teamwork and promote collaboration 19 | across engineering disciplines. 20 |
21 |23 | Each week, tasks will be assigned alongside lecture sessions that 24 | provide technical guidance and resources. A second weekly meeting 25 | focuses on integration, where sub-teams come together to test, refine, 26 | and combine their contributions into a cohesive system. 27 |
28 |33 | These sessions ensure that software, electronics, and mechanical 34 | components integrate seamlessly, offering insight into the workflow of 35 | real-world engineering projects. 36 |
37 |38 | By the end of the program, participants will have engineered a 39 | complete robotics product, gaining practical experience in 40 | interdisciplinary teamwork and problem-solving. 41 |
42 |23 | PHOTO GALLERY 24 |
25 |