π Visit the website to explore real-world projects, filter by tech stack, and discover new ideas!
This is a single-page web application built with Next.js, where all event logic is handled via API routes. The app reads from a CSV file, displays upcoming tech events, and lets users add new ones dynamically.
π¬ This project is proudly part of GSSoC '25! Thanks to the amazing open-source community, contributors, and mentors for your valuable support. Contributions are welcome from GSSoC contributors and open-source enthusiasts!
- π‘ API-Based Data Fetching: Fetch and update event data via custom API routes.
- π CSV Data Management: Read/write event info using
fs
andpapaparse
. - π Search Functionality: Filter events by event name.
- β‘ Real-Time Updates: Events update without a full-page refresh.
- π Fast UI: Built with Tailwind CSS and efficient state management.
- Next.js
- React
- Tailwind CSS
- Papaparse
- Node.js fs module
- Node.js (>= 16.x)
- npm or yarn
We welcome contributions as part of GirlScript Summer of Code 2025 (GSSoC'25) and beyond!
Follow these steps to contribute your changes to DevDisplay:
-
π Star & Fork the Repository
Click the βStarβ button to support the project, then βForkβ the repo to create your own copy:
π https://github.com/muskan-fatim/Tech_event.git -
π₯ Clone Your Fork
Use the following command to clone your forked repository to your local machine:git clone https://github.com/Your-Username/Tech_event.git
-
Create a Branch Navigate to the project directory and create a new branch for your changes:
cd Tech_event git checkout -b my-feature-branch
-
Make Changes Add your new ML projects, games, websites, or enhancements. Fix bugs or improve UI/UX as needed.
-
Commit Your Changes Use a meaningful commit message:
git add . git commit -m "π¦ [Feature Add] Add XYZ website project"
-
Push Your Changes Push your branch to your GitHub fork:
git push origin my-feature-branch
-
Submit a Pull Request
Go to your fork on GitHub.
Click "Compare & pull request".
Add a descriptive title using one of the prefixes: [UI], [UX], [Feature Add].
Link the related issue (if any) and clearly describe your changes.
π‘ Good first issues are labeled under
gssoc
# 1. Clone the repository
git clone https://github.com/muskan-fatim/Tech_event.git
cd Tech_event
# 2. Install dependencies
npm install # or yarn install
# 3. Start the development server
npm run dev # or yarn dev
Visit http://localhost:3000
in your browser to see the app live.
π Explore the Project Directory Structure
Tech_event/
βββ .gitignore
βββ CODE_OF_CONDUCT.md
βββ CONTRIBUTING.md
βββ README.md
βββ next.config.ts
βββ tailwind.config.ts
βββ tsconfig.json
βββ package.json #implied by npm/yarn references
βββ public/ #implied by Next.js standard structure
βββ app/
β βββ layout.tsx #implied by Next.js app router structur
β βββ page.tsx #main page component
β βββ ...other Next.js app router files
βββ components/ #custom React components
β βββ ...component files
βββ pages/
β βββ api/ #API routes
β β βββ ...API route handlers
β βββ ...other page files #if using pages router alongside app router
βββ styles/ #implied by Tailwind CSS usage
β βββ globals.css
βββ data/ #implied by CSV handling
β βββ events.csv #data file mentioned in README
βββ node_modules/ #ignored in .gitignore
βββ .next/ #ignored in .gitignore - Next.js build output
Thanks to these amazing people who have contributed to the Tech_event project:
Have ideas, feedback, or just want to say hi?
Reach out on Twitter @mushiiFatima or drop an issue to get involved.
Feel free to open issues or discussions if you have any feedback, feature suggestions, or want to collaborate!
To ensure a welcoming and inclusive environment, we have a Code of Conduct that all contributors are expected to follow. In short: Be respectful, be kind, and be collaborative. Please read the full Code of Conduct before participating.
This project is licensed under the MIT License.
Thank you again for your interest. We can't wait to see what you build with us! β€οΈβ€οΈ
#GSSoC25 #OpenSource #WomenInTech #NextJS #TechEvents