DEVSA is the central platform connecting San Antonio's tech community. We bridge the gap between passionate builders, local partners, and the growing tech ecosystem.
🌐 Live Site: devsa.community
DEVSA started with a simple question: "Where is the tech community in San Antonio?"
We found 20+ tech-focused organizations scattered across the city, not collaborating and living in their own bubbles. So we built DEVSA to bring them together—a platform where you can discover tech communities that match your interests and where these groups can collaborate, share resources, and grow stronger together.
- Framework: Next.js 16 with App Router
- Styling: Tailwind CSS v4
- Animation: Motion (Framer Motion)
- Database: Google Firestore - NoSQL cloud database
- Bot Protection: MAGEN - Human-first verification
- Deployment: Vercel
- Analytics: Vercel Analytics
- Node.js 18+
- pnpm (recommended) or npm
# Clone the repository
git clone https://github.com/your-org/next-devsa.git
cd next-devsa
# Install dependencies
pnpm install
# Set up environment variables
cp .env.example .env.local
# Edit .env.local with your keys (see Environment Variables section)
# Start development server
pnpm devThe app will be running at http://localhost:3000
Create a .env.local file with:
# Google Firestore - Service Account Key (as JSON string)
GOOGLE_SERVICE_ACCOUNT_KEY={"type":"service_account","project_id":"your-project",...}
# MAGEN (Bot Protection)
MAGEN_API_KEY=your_magen_api_key
MAGEN_SECRET_KEY=your_magen_secret_key
# Admin Setup (one-time use to create first admin)
ADMIN_SETUP_SECRET=your_random_secret_for_initial_setupAfter deploying, set up your first admin by making a POST request:
curl -X POST https://your-domain.com/api/admin/setup \
-H "Content-Type: application/json" \
-d '{"email": "[email protected]", "secret": "your_admin_setup_secret"}'This only works once when no admins exist in the system.
next-devsa/
├── app/ # Next.js App Router
│ ├── page.tsx # Homepage
│ ├── layout.tsx # Root layout with navbar/footer
│ ├── globals.css # Global styles & Tailwind
│ ├── api/ # API routes
│ │ ├── magen/ # MAGEN bot protection endpoints
│ │ ├── og/ # Open Graph image generation
│ │ ├── admin/ # Admin API endpoints
│ │ ├── newsletter/ # Newsletter subscription
│ │ ├── events/ # Events CRUD
│ │ └── access-request/ # Access request for organizers
│ ├── events/ # Events pages
│ │ ├── page.tsx # Community calendar
│ │ ├── community/[slug]/ # Dynamic community event pages
│ │ ├── morehumanthanhuman/ # AI Conference page
│ │ └── pysanantonio/ # PySA event page
│ ├── admin/ # Protected admin pages
│ │ ├── page.tsx # Admin dashboard
│ │ └── create-event/ # Create event page
│ ├── coworking-space/ # Geekdom coworking page
│ └── signin/ # Access request page
│
├── components/ # React components
│ ├── hero-bridge.tsx # Main hero section
│ ├── hero-communities.tsx # Community showcase grid
│ ├── partner-section.tsx # Partners carousel
│ ├── magen-newsletter-cta.tsx # Community spotlight section
│ ├── navbar.tsx # Navigation bar
│ ├── footer.tsx # Site footer
│ ├── access-request-form.tsx # Organizer access request form
│ ├── events/ # Event-specific components
│ ├── coworking-space/ # Coworking page components
│ ├── pysa/ # PySA event components
│ ├── aiconference/ # AI Conference components
│ └── icons/ # SVG icon components
│
├── data/ # Static data files
│ ├── communities.ts # Tech community listings
│ ├── events.ts # Community events
│ ├── partners.ts # Partner organizations
│ └── pysa/ # PySA event data
│ ├── sessions.ts # Conference sessions
│ ├── speakers.ts # Speaker information
│ └── sponsors.ts # Event sponsors
│
├── lib/ # Utility functions
│ ├── firebase-admin.ts # Firebase Admin SDK setup
│ ├── magen.ts # MAGEN bot protection
│ └── utils.ts # General utilities (cn, etc.)
│ └── magen.ts # MAGEN verification helpers
│
├── types/ # TypeScript type definitions
│ └── magen.d.ts # MAGEN types
│
└── public/ # Static assets
We welcome contributions from the San Antonio tech community! Here's how you can help:
- Edit
data/communities.ts - Add your community object following the existing format:
{
id: "your-community-id",
name: "Your Community Name",
description: "Brief description of your community",
logo: "https://your-logo-url.png",
color: "#yourBrandColor",
website: "https://your-website.com",
meetup: "https://meetup.com/your-group",
discord: "https://discord.gg/your-invite",
}- Edit
data/partners.ts - Add your partner organization:
{
id: "partner-id",
name: "Partner Name",
logo: "https://partner-logo-url.png",
description: "What the partner does",
website: "https://partner-website.com",
}- Fork the repository
- Create a feature branch:
git checkout -b feature/add-my-community - Make your changes
- Test locally with
pnpm dev - Commit with a clear message:
git commit -m "Add XYZ Community to listings" - Push to your fork:
git push origin feature/add-my-community - Open a Pull Request with a description of your changes
pnpm dev # Start development server with Turbopack
pnpm build # Build for production
pnpm start # Start production server
pnpm lint # Run ESLint