-
Notifications
You must be signed in to change notification settings - Fork 3
2. Technical Overview
- Feature Branches: Create a new branch for each feature or bug fix.
- Pull Requests: Submit pull requests for code review and merging.
- Code Reviews: Peer review is crucial; to ensure code quality and standards.
Production Deployment: Once changes are verified and a successful local build is done, then they are deployed to Vercel.
In our project, we follow the Next.js 13 app router structure for directory organization. We have a "components" directory at the same level as the "app" directory. This is a common pattern where reusable components are kept separate from the pages. It helps in better organization and code reusability.
Our website is powered by several key technologies. We use Next.js, a popular React framework that allows for server-side rendering and efficient client-side navigation. Additionally, we utilize TypeScript for static typing and enhanced developer productivity. Tailwind CSS is another technology we use for fast and responsive UI development. It provides utility classes that help in rapidly building custom designs. Lastly, we integrate Sanity CMS for content management and easy collaboration across the team.
To enhance the functionality of our website, we integrate third-party services and APIs. One such service is Nodemailer, which we use to send emails to responsible parties for contact form submissions via our club Gmail account. This ensures that the relevant individuals receive timely notifications and can respond efficiently.
Follow our coding standards for consistency.
- Adding/Editing Pages: https://nextjs.org/docs/app/building-your-application/routing/pages-and-layouts
- Modifying Styles: https://tailwindcss.com/docs/