Skip to content

ABES-CodeChef/CC-websiteV2.0

Repository files navigation

CodeChef ABESEC Chapter Website

Welcome to the official CodeChef ABESEC repository..

🚀 Deployed Website

Coming Soon:

Table of Contents

About

This repository showcases the events, activities, and achievements of CodeChef ABESEC Chapter with a clean, responsive design. Built using React js, CSS, JavaScript, GSAP, React Router, and framer-motion, the project aims to provide an interactive, user-friendly experience for users. Explore our events, view achievements, and stay updated on the latest activities!

Features

  • Responsive Design: Optimized for all devices (mobile, tablet, desktop).
  • Event Listings: Displays upcoming events and activities.
  • Team Page: Introduces the members of the CodeChef ABESEC Chapter.
  • Dynamic Blog: Planned space for coding tutorials and technical articles.
  • Project Page: Highlights completed and upcoming projects, showcasing the Chapter's technical contributions.

Tech Stack

  • React js
  • JavaScript
  • GSAP
  • React Router
  • framer-motion
  • Tailwind CSS
  1. Clone the repository:
    git clone https://github.com/ABES-CodeChef/CC-Website-5.O.git
  2. Navigate to the project directory:
    cd CC-websiteV2.0
  3. Run the development server:
    npm run dev

Contributing

Contributions are welcome! Whether fixing bugs, adding features, or improving documentation, your support matters.

We welcome contributions from everyone! Whether you're fixing bugs, adding new features, or improving documentation, your help is appreciated.

How to Contribute

  1. Fork the Repository Start by forking the project repository to your GitHub account.

  2. Clone Your Fork Clone your forked repository to your local machine:

    git clone https://github.com/your-username/CC-websiteV2.0
  3. Create a New Branch Create a new branch for your feature or bugfix:

    git checkout -b feature/my-new-feature
  4. Make Your Changes Implement your changes in the codebase. Ensure you follow coding standards and add clear, concise code.

  5. Commit Your Changes Commit your changes with a descriptive commit message following the Conventional Commits format:

    git commit -m "feat: add new blog section"
  6. Push Your Branch Push your changes to your forked repository:

    git push origin feature/my-new-feature
  7. Open a Pull Request Submit a pull request (PR) to the main branch of the original repository. Clearly describe your changes in the PR description and reference any related issues.

Commit Message Guidelines

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation changes
  • refactor: Code refactoring without adding features or fixing bugs

Tips for Writing Good Pull Requests

  • Keep your PR focused on one change.
  • Describe the problem your PR solves.
  • Reference any related issues in your PR description.
  • Ensure your code works and passes any existing tests.

License

This project is licensed under the MIT License. See the LICENSE file for details.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 7