Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
64 changes: 64 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
# MegaEngage - Employee Engagement Platform

## Overview

MegaEngage is a modern employee engagement platform designed to help organizations measure, track, and improve employee satisfaction and engagement levels.

## Features

- **Dashboard**: Real-time analytics and insights
- **Surveys**: Create and manage employee engagement surveys
- **Feedback**: Continuous feedback collection and management
- **Recognition**: Peer-to-peer recognition and rewards
- **Reports**: Comprehensive reporting and data visualization

## Tech Stack

- Frontend: React, TypeScript, Tailwind CSS
- Backend: Node.js, Express
- Database: PostgreSQL
- Authentication: JWT

## Getting Started

### Prerequisites

- Node.js (v16 or higher)
- npm or yarn
- PostgreSQL

### Installation

1. Clone the repository:
```bash
git clone https://github.com/PetrAnto/megaengage.git
cd megaengage
```

2. Install dependencies:
```bash
npm install
```
Comment on lines +40 to +41

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove npm install/run instructions that cannot execute

The onboarding steps tell users to run npm install and npm run dev, but this commit adds those commands without adding a package.json, so a fresh clone fails immediately with ENOENT instead of starting the project. This makes the primary setup path in the new README unusable unless the missing Node project files are added or the commands are replaced with the real run instructions.

Useful? React with 👍 / 👎.


3. Set up environment variables:
```bash
cp .env.example .env

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Drop .env.example copy step or add the missing template

The setup guide now includes cp .env.example .env, but the repository does not contain .env.example, so this step always fails for new users following the README verbatim. Either commit the referenced template file or remove this instruction to avoid a broken setup flow.

Useful? React with 👍 / 👎.

```
Edit `.env` with your configuration.

4. Start the development server:
```bash
npm run dev
```

## Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.

## Contact

For questions or feedback, please open an issue in this repository.