Saikai
Manage Your Way To Work!
Explore the docs Âģ
View Website
¡
Report Bug
¡
Contact Us
Table of Contents
About The Project
400 job applications
Pretty simple, right? Until you need to keep track of your job search! And that's where Saikai comes in.
Saikai is a web platform, where job seekers can keep track of their job applications and organize their job search.
In Saikai, you can log any detail regarding the job applications and quickly get a clear vision of how your job search is going.
Saikai helps you to manage all the information you need in order to be right on ready once you get a call back from your dream company. Here you can organize all the position details including position description, status, applied date and many more!
Built With
Getting Started
Prerequisites
Install Node.
- npm
npm install npm@latest -g
Installation
- Get a free API Key at Firebase console.
- Clone the repo
git clone https://github.com/Saikai-oyo/Saikai.git
- Install NPM packages
npm install
- Create
.env.local
file and enter your API in (you will get 7 keys)REACT_APP_FIREBASE_API_KEY= THE_API_RELEVANT_KEY REACT_APP_FIREBASE_AUTH_DOMAIN= THE_API_RELEVANT_KEY REACT_APP_FIREBASE_PROJECT_ID= THE_API_RELEVANT_KEY REACT_APP_FIREBASE_STORAGE_BUCKET= THE_API_RELEVANT_KEY REACT_APP_FIREBASE_MESSAGING_SENDER_ID= THE_API_RELEVANT_KEY REACT_APP_FIREBASE_APP_ID= THE_API_RELEVANT_KEY REACT_APP_FIREBASE_MEASUREMENT_ID= THE_API_RELEVANT_KEY
- Start the application
npm started
Usage
- Your time should be focused on creating something amazing. A project that solves a problem and helps others
- You shouldn't be doing the same tasks over and over like creating a README from scratch
- You should element DRY principles to the rest of your life.
Roadmap
See the Next Milestones for a list of proposed features (and known issues) for the next milestones.
Contributing
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.
- Speak with Idan at LinkedIn to be formal contributing
- Fork the Project.
- Create your Feature Branch.
- Commit your Changes.
- Push to the Branch.
- Open a Pull Request.
Convention
Branch
Branch naming convention is as following:
TYPE-ISSUE_ID-DESCRIPTION
examples:
feat-45-add-new-button
fix-741-change-localstorage-get-function
Pull Request (PR)
Pull Request (PR) title convention is as following:
[TYPE-ISSUE_ID]-DESCRIPTION
example:
[Feat-45] Add button to login component
[Fix-114] Change localstorage get function
Commits
Commit information convention is as following:
[TYPE-ISSUE_ID]-DESCRIPTION
example:
[Feat-45] Add button to login component
[Fix-114] Change localstorage get function
Type
When type can be:
* feat - is a new feature
* doc - documentation only changes
* fix - a bug fix
* refactor - code change that neither fixes a bug nor adds a feature
All PRs must include commit message with the changes description!
License
Distributed under the MIT License. See LICENSE
for more information.
Contact
đ¨đžâđģ Open-source Manager (Idan) - LinkedIn