This repository is designed to provide easy access to Developer MultiGroup's events. You can explore past or upcoming events here, and if you'd like to contribute, you can check out the issues section to support us.
Also check out our Data Science Awesome Repo for more resources!
- Dynamic Structure: Create and publish new events without requiring any database or storage service
- Add to Calendar: Easily add event sessions to your calendar and stay in the loop
- Access Locations: Reach event venues easily with your platform's preferred map application
- Responsive Design: A fully dynamic design to follow our events from any platform
- Next.js: User interface development
- Shadcn/ui: Pre-built components
- Tailwind CSS: Styling and responsive designs
- Vercel: Code deployment
- Framer: Component and page animations
- Node.js (version 16.x or later)
- npm or yarn
$ git clone https://github.com/Developer-MultiGroup/multigroup-event-page.git
$ cd multigroup-event-page
$ git branch genai-fund
$ npm install
$ npm run devVisit http://localhost:3000 in your browser to see the development version.
classDiagram
direction LR
class Event {
+Speaker[] speakers
+Session[] sessions
+Sponsor[] sponsors
}
class Speaker {
+string fullName
+string title
+string phrase
+string company
}
class Session {
+string topic
+string date
+string dateTime
+string startTime
+string endTime
+string speakerName
}
class Sponsor {
+string tier
+string sponsorSlug
}
Event *-- Speaker : contains
Event *-- Session : contains
Event *-- Sponsor : contains
/public/images
├── speakers
└── sponsorsThe project's photo storage structure is as shown above.
All speaker photos are stored in this directory with slugified names. When adding a speaker to any event, photos are automatically retrieved from this directory when added with that name.
The logic for sponsor photos is the same as speakers. Sponsor logos are kept in this directory with a slugified name, and this name is added to the array structure in the event object when needed.
After setting up the project in your local environment by following the installation instructions, you can make any changes you want and fix any bugs by sending a Pull Request. Follow these steps to send a PR:
-
Create a
Forkof the project -
Create a new
Branchgit checkout -b feature/your-feature # or git checkout -b fix/your-fix -
Make your changes
-
Commit your changes
git add . git commit -m "feat: Add a descriptive commit message" # or git commit -m "fix: Add a descriptive commit message"
-
Push your changes to the
Repositorygit push origin feature/your-feature
-
Open a
Pull RequestCreate a PR from your ownForkof this project to the mainRepositoryin your profile
Check out the project's license.
If you have any questions, feel free to reach out to me at me@furkanunsalan.dev.
