Skip to content

maxkrv/uevent-fe

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

37 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Uevent

Uevent: Your Ultimate Event Management Platform

license last-commit repo-top-language repo-language-count

Developed with the software and tools below.

ESLint TypeScript Docker Zod Prettier Axios Tailwind-CSS Vite React Zustand Day.js PostCSS React Query React Hook Form


πŸ”— Quick Links


πŸ“‹ Overview

Uevent is a comprehensive event management platform that connects users with events and companies. The platform allows users to discover, follow, and purchase tickets for events, follow companies, and manage their event attendance. With a modern, intuitive interface, Uevent provides a seamless experience for event discovery, ticket purchasing, and social engagement around events.

Key Features

  • User Authentication: Secure login, registration, and account management
  • Event Discovery: Browse and search for events with filtering options
  • Company Profiles: Follow companies and stay updated with their events
  • Ticket Management: Purchase and manage event tickets
  • Interactive Maps: Location-based event discovery with Google Maps integration
  • User Profiles: Personalized profiles with upcoming and past events
  • Notifications: Real-time updates for followed events and companies
  • Responsive Design: Seamless experience across all devices

πŸš€ Tech Stack


πŸ’» Getting Started

βš™οΈ Installation

  1. Clone the uevent-fe repository:
git clone https://github.com/maxkrv/uevent-fe
  1. Change to the project directory:
cd uevent-fe
  1. Install the dependencies:
npm install

πŸ•œ Running Uevent

Use the following command to run Uevent in development mode:

npm run dev

The application will be available at http://localhost:3000 (or the port specified in your Vite configuration).

πŸ“¦ Building for Production

To build the application for production:

npm run build

To preview the production build locally:

npm run preview

πŸ“‚ Project Structure

src/
β”œβ”€β”€ assets/           # Static assets like logos
β”œβ”€β”€ config/           # Application configuration
β”œβ”€β”€ modules/          # Feature-based modules
β”‚   β”œβ”€β”€ auth/         # Authentication related components
β”‚   β”œβ”€β”€ company/      # Company related components
β”‚   β”œβ”€β”€ event/        # Event related components
β”‚   β”œβ”€β”€ ticket/       # Ticket related components
β”‚   β”œβ”€β”€ user/         # User profile related components
β”‚   └── ...
β”œβ”€β”€ shared/           # Shared utilities, components, and hooks
β”‚   β”œβ”€β”€ api/          # API client setup
β”‚   β”œβ”€β”€ components/   # Reusable UI components
β”‚   β”œβ”€β”€ guards/       # Route guards
β”‚   β”œβ”€β”€ hooks/        # Custom React hooks
β”‚   β”œβ”€β”€ lib/          # Library configurations
β”‚   β”œβ”€β”€ store/        # Global state management
β”‚   β”œβ”€β”€ types/        # TypeScript type definitions
β”‚   β”œβ”€β”€ utils/        # Utility functions
β”‚   └── validators/   # Form validation schemas
└── styles/           # Global styles

πŸ”§ Environment Variables

The application requires the following environment variables:

VITE_API_URL=your_api_url
VITE_GOOGLE_MAPS_API_KEY=your_google_maps_api_key
VITE_GOOGLE_CLIENT_ID=your_google_client_id

Create a .env file in the root directory and add these variables with your specific values.

🀝 Contributing

Contributions are welcome! Here are several ways you can contribute:

``Contributing Guidelines``
  1. Fork the Repository: Start by forking the project repository to your GitHub account.
  2. Clone Locally: Clone the forked repository to your local machine using a Git client.
git clone https://github.com/maxkrv/uevent-fe
  1. Create a New Branch: Always work on a new branch, giving it a descriptive name.
git checkout -b new-feature-x
  1. Make Your Changes: Develop and test your changes locally.
  2. Commit Your Changes: Commit with a clear message describing your updates.
git commit -m 'Implemented new feature x.'
  1. Push to GitHub: Push the changes to your forked repository.
git push origin new-feature-x
  1. Submit a Pull Request: Create a PR against the original project repository. Clearly describe the changes and their motivations.

Once your PR is reviewed and approved, it will be merged into the main branch.

πŸ“„ License

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


About

No description, website, or topics provided.

Resources

License

Stars

2 stars

Watchers

1 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages