-
Select Topic AreaQuestion BodyMe and my team are preparing for a hackathon topic I provided on title we are new to this and knows I guess very little or nothing about it can u guys help us out to prepare well... |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
For a campus events platform, you might want to focus on these core areas: Backend/Data:
Frontend:
Key features to prioritize:
Tech stack suggestions:
Start with MVP features (create event, view events, basic auth) and build from there. Focus on clean UX since adoption depends on students actually wanting to use it. What's your team's experience level with web development? Also - a lot of this will depend on the length of the hackathon of course! |
Beta Was this translation helpful? Give feedback.
-
|
Based on my experience with full-stack development. Frontend For the frontend, stick with the basics: HTML, CSS, and vanilla JavaScript. It gives you direct control without the overhead of a framework, which is ideal for rapid development. You can focus on functionality instead of getting bogged down in setup. Backend For the backend, use FastAPI with Python. Fast to Learn: Python is easy for new developers to pick up, which helps your team move faster. Performant: It's asynchronous out of the box, so it handles concurrent requests well. This is good for features like notifications. Strong Libraries: Python's ecosystem has a library for almost anything you'll need. Database Use PostgreSQL for your database. It's a robust relational database that's well-suited for structured data. Mobile App If you're building a mobile app, use React Native. You can build for both iOS and Android from a single JavaScript codebase, which is far more efficient than writing two separate native applications. Cybersec Don't neglect basic security, even in a hackathon. You'll be handling user data. CORS (Cross-Origin Resource Sharing): You'll need to configure this on your backend to allow your frontend to make requests. FastAPI has middleware that makes this straightforward. Input Sanitisation: Use a library like bleach in Python to clean HTML submitted by users. This prevents cross-site scripting (XSS). SQL Injection: Remember to parameterise queries. Rate Limiting: Implement rate limiting on your API endpoints to prevent simple denial-of-service or spamming attacks. Deployment For deployment, use Railway. It simplifies the process by deploying directly from your Git repository. This will save you time on infra. Good luck. |
Beta Was this translation helpful? Give feedback.
For a campus events platform, you might want to focus on these core areas:
Backend/Data:
Frontend:
Key features to prioritize:
Tech stack suggestions: