Development

πŸ‘©β€πŸ’» Development Guide

"Contributing to Confession Collective is like writing in a group diary, but with more TypeScript and fewer doodles."

Project Structure

confession-collective/
β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ components/     # Where the magic happens
β”‚   β”œβ”€β”€ hooks/         # Custom hooks (they're hooks, not boomerangs)
β”‚   β”œβ”€β”€ lib/           # Utilities (the Swiss Army knife drawer)
β”‚   └── types/         # TypeScript types (because we're fancy)

Development Flow

  1. Fork the repo (it's like adopting a digital pet)

  2. Create your feature branch:

git checkout -b feature/make-something-awesome
  1. Write amazing code

  2. Push to your fork

  3. Create a Pull Request (and cross your fingers)

Testing

# Run tests (and hope for the best)
npm test

# Run tests while watching files
npm run test:watch

# Run tests and generate coverage report
npm run test:coverage # Spoiler: We love high coverage!

Building

# Build for production
npm run build

# Preview the build
npm run preview # Moment of truth!

Remember: Code is like confessions – the cleaner, the better! 🧹

Last updated