https://github.com/triple-ade/analytics_dashboard
Craft a responsive and visually appealing analytics dashboard
https://github.com/triple-ade/analytics_dashboard
Last synced: 15 days ago
JSON representation
Craft a responsive and visually appealing analytics dashboard
- Host: GitHub
- URL: https://github.com/triple-ade/analytics_dashboard
- Owner: TRIPLE-ADE
- Created: 2024-01-24T11:10:00.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-01-27T16:42:03.000Z (over 2 years ago)
- Last Synced: 2025-03-01T07:27:48.528Z (over 1 year ago)
- Language: JavaScript
- Homepage: https://analytics-dashboard-mu.vercel.app
- Size: 98.6 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## Getting Started
The analytics dahsboard with responsive and visually appealing interface. Emphasize a sleek and user-friendly design to guarantee a smooth experience across different devices.
### Prerequisites
To run this project you need the following installed:
- [Node 20.9](https://nodejs.org/) or later
## Technologies Used
- React JS
- Next JS
- Tailwind CSS
### Setup
Clone this repository to your desired folder:
```bash
git clone https://github.com/Superfly101/medlink.git
```
Install project dependencies:
```bash
cd medlink
npm install
```
Run development server:
```bash
npm run dev
```
Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
## 🤝 Contributing
Contributions, issues, and feature requests are welcome!
### Contribution Guidelines
1. Clone the repo `git clone https://github.com/TRIPLE-ADE/analytics_dashboard`.
2. Create a new branch from the `dev` branch `git checkout -b Feat/{feature you're working on}`
3. Make sure your branch is up to date with the `dev` branch: `git pull origin main`
4. After making changes, do `git add .`
5. Commit your changes with a descriptive commit message: `git commit -m "your commit message"`.
6. To make sure there are no conflicts, run `git pull origin main`.
7. Push changes to your new branch, run `git push -u origin Feat/{feature you're working on}`.
9. Ensure to describe your pull request.
### _Commit CheatSheet_
| Type | | Description |
| -------- | ------------------------ | ----------------------------------------------------------------------------------------------------------- |
| feat | Features | A new feature you're adding |
| fix | Bug Fixes | A bug fix |
| docs | Documentation | Documentation only changes |
| style | Styles | Features and updates relating to styling |
| refactor | Code Refactoring | A code change that neither fixes a bug nor adds a feature |
| perf | Performance Improvements | A code change that improves performance |
| test | Tests | Adding missing tests or correcting existing tests |
| build | Builds | Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) |
| ci | Continuous Integrations | Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) |
| chore | Chores | Other changes that don't modify, frontend or test files |
| revert | Reverts | Reverts a previous commit |
> _Sample Commit Messages_
- `feat: Added plugin info endpoints` := `feat` is used here because the feature was non-existent before the commit.