tucsonjs website #1
Description
Overview
Project Name
website
Brief Description
To kick off the practice of building stuff together, let's make a hub for all our links. We can integrate with the lu.ma api so the upcoming and previous meetup events can be available (and so we don't have to update the website every time an event is posted.)
Problem Statement
Get people contributing and learning about whatever stack we go with, a place to try to build in a group, have people get code reviews etc
Project Details
Key Features & Scope
- Set up the repo workflow so only pull requests with a codeowner approval can be merged to main
- Get people added to the tucsonjs github org
- Build Github-pages hosted website that links to github, discord, lu.ma
- Integrate lu.ma api to show upcoming and previous events
- Could do things like build a d3.js chart to track meetup attendance/growth
- Someone could make a docker container with database if they want to learn that!
- Someone could add jest/react testing library/cypress tests if they want to learn that
- Easter eggs!
Success Criteria
We should consider this a moving target with a minimum set of standards. Try to treat the project as you would a company's application, and apply your code reviews through that lens. We can iterate on this over time, but minimum success criteria would be a functional website with links to various platforms.
Target Audience
Members, local community, prospective members
Technical Information
Proposed Tech Stack
- Frontend: T3 Stack (Typescript, React, Next.js, Tailwind?, tRPC?)
- Backend: monorepo with nextjs handling backend
- Database: idk postgres?
- Other tools/services: lu.ma ai
Complexity Assessment
- [] Beginner Friendly - Great entry point for new developers
- Intermediate - Requires some experience with web development
- Advanced - Needs experienced developers in specific areas
Estimated Timeline
- Sprint Project (1-2 weeks)
- Short Term (1-2 months)
- Medium Term (3-4 months)
- Long Term (6+ months)
Team & Collaboration
Ideal Team Size
- Small team (2-3 people)
- Medium team (4-6 people)
- Large team (7+ people)
- Open to any number of contributors
Project Leadership
- Yes, I want to be the project lead
- Yes, but I'd like a co-lead
- I'd prefer someone else leads, but I'll be a core contributor
- I'm just proposing the idea for others to take on
- No opinion but happy to lead if helpful
Community Impact
Local Tucson Connection
Learning Opportunities
Industry standard techstack, api integration, styling and theming, devops, whatever we want
Additional Information
Inspiration/References
Potential Challenges
time allocation, collaboration across levels of experience etc
Resources Available
Community Project Agreement
By submitting this project idea, I understand and agree that:
- Community Ownership: This project will be owned by the TucsonJS community and hosted in the TucsonJS GitHub organization
- Collaborative Decision Making: Major project decisions will be made collaboratively with input from active contributors and TucsonJS organizers
- Open Source: The project will be open source and available for the broader community to use and contribute to
- Continuity: The project should be able to continue even if I (the original proposer) step away or become unavailable
- Community Standards: The project will follow TucsonJS community guidelines and code of conduct
I acknowledge that I'm proposing this as a community project, not a personal project that I own.
Your Information
GitHub Username: @beardage
Discord Username: beardage
Your Experience Level: 15ish years building websites/apps
Availability: random evenings
Next Steps
- General interest/feasibility feedback
- Technical approach discussion
- Help refining the scope
- Finding collaborators
- Other: