├── .github
└── auto_assign.yml
├── .gitignore
├── .idea
├── .gitignore
├── Social-Scheduler.iml
├── inspectionProfiles
│ └── Project_Default.xml
├── misc.xml
├── modules.xml
├── vcs.xml
└── workspace.xml
├── CODE_OF_CONDUCT.md
├── LICENSE
├── README.md
├── Temporary-Backend
├── .env
├── .gitignore
├── controllers
│ └── whatsAppControllers.js
├── helper-function
│ └── whatsapp-send-message.js
├── package-lock.json
├── package.json
├── routes
│ └── whatsapp-routes.js
└── src
│ └── App.js
├── contribute.md
├── features.json
├── linkedin-automation
├── config.txt
└── index.py
├── logo.jpg
├── package-lock.json
├── package.json
├── public
├── _redirects
├── favicon.ico
├── index.html
└── robots.txt
└── src
├── App.css
├── App.js
├── Detail.css
├── components
├── About.jsx
├── Contact.jsx
├── Default.jsx
├── LandingPage.jsx
├── Signin.jsx
├── UserRegistration.js
├── assets
│ ├── css
│ │ ├── components
│ │ │ └── about_us.css
│ │ └── materialize.min.css
│ ├── images
│ │ ├── HakinCodes.png
│ │ ├── about-background.jpg
│ │ ├── boyimage.png
│ │ ├── facebook.svg
│ │ ├── girlimage.png
│ │ ├── github.svg
│ │ ├── google-icon.svg
│ │ ├── instagram.svg
│ │ ├── linkedin.svg
│ │ ├── temp-logo.jpg
│ │ ├── twitter.svg
│ │ ├── undraw_Login.svg
│ │ └── undraw_team_spirit_hrr4.svg
│ └── js
│ │ ├── materialize.js
│ │ └── materialize.min.js
├── layout
│ ├── Footer.jsx
│ └── Navbar.jsx
└── pages
│ ├── 404-Page
│ ├── Page_404.css
│ └── Page_404.jsx
│ └── Contributor
│ ├── CardItem.jsx
│ └── Cards.jsx
├── contact_illustration.svg
├── data
├── adminList.js
└── mentorList.js
├── index.js
├── lib
├── contributers.js
└── email.js
└── utils
└── screenSizes.js
/.github/auto_assign.yml:
--------------------------------------------------------------------------------
1 | # Set to true to add reviewers to pull requests
2 | addReviewers: true
3 |
4 | # Set to true to add assignees to pull requests
5 | addAssignees: false
6 |
7 | # A number of reviewers added to the pull request
8 | # Set 0 to add all the reviewers (default: 0)
9 | numberOfReviewers: 1
10 |
11 | # A number of assignees to add to the pull request
12 | # Set to 0 to add all of the assignees.
13 | # Uses numberOfReviewers if unset.
14 | # numberOfAssignees: 2
15 |
16 | # Set to true to add reviewers from different groups to pull requests
17 | useReviewGroups: true
18 |
19 | # A list of reviewers, split into different groups, to be added to pull requests (GitHub user name)
20 | reviewGroups:
21 | projectAdmin:
22 | - anushbhatia
23 | - smaranjitghose
24 | mentors:
25 | - ashishnagpal2498
26 | - abhu-A-J
27 | # Set to true to add assignees from different groups to pull requests
28 | useAssigneeGroups: false
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
2 |
3 | # dependencies
4 | /node_modules
5 | /.pnp
6 | .pnp.js
7 |
8 | # testing
9 | /coverage
10 |
11 | # production
12 | /build
13 |
14 | # misc
15 | .DS_Store
16 | .env.local
17 | .env.development.local
18 | .env.test.local
19 | .env.production.local
20 |
21 | npm-debug.log*
22 | yarn-debug.log*
23 | yarn-error.log*
24 |
25 | .idea/
26 |
27 | .vscode/
28 |
--------------------------------------------------------------------------------
/.idea/.gitignore:
--------------------------------------------------------------------------------
1 | # Default ignored files
2 | /shelf/
3 | /workspace.xml
4 | # Editor-based HTTP Client requests
5 | /httpRequests/
6 |
--------------------------------------------------------------------------------
/.idea/Social-Scheduler.iml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
--------------------------------------------------------------------------------
/.idea/inspectionProfiles/Project_Default.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
--------------------------------------------------------------------------------
/.idea/misc.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
--------------------------------------------------------------------------------
/.idea/modules.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
--------------------------------------------------------------------------------
/.idea/vcs.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
--------------------------------------------------------------------------------
/.idea/workspace.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 | 1597567038883
40 |
41 |
42 | 1597567038883
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 |
64 |
65 |
66 |
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 |
75 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | In the interest of fostering an open and welcoming environment, we as
6 | contributors and maintainers pledge to making participation in our project and
7 | our community a harassment-free experience for everyone, regardless of age, body
8 | size, disability, ethnicity, sex characteristics, gender identity and expression,
9 | level of experience, education, socio-economic status, nationality, personal
10 | appearance, race, religion, or sexual identity and orientation.
11 |
12 | ## Our Standards
13 |
14 | Examples of behavior that contributes to creating a positive environment
15 | include:
16 |
17 | * Using welcoming and inclusive language
18 | * Being respectful of differing viewpoints and experiences
19 | * Gracefully accepting constructive criticism
20 | * Focusing on what is best for the community
21 | * Showing empathy towards other community members
22 |
23 | Examples of unacceptable behavior by participants include:
24 |
25 | * The use of sexualized language or imagery and unwelcome sexual attention or
26 | advances
27 | * Trolling, insulting/derogatory comments, and personal or political attacks
28 | * Public or private harassment
29 | * Publishing others' private information, such as a physical or electronic
30 | address, without explicit permission
31 | * Other conduct which could reasonably be considered inappropriate in a
32 | professional setting
33 |
34 | ## Our Responsibilities
35 |
36 | Project maintainers are responsible for clarifying the standards of acceptable
37 | behavior and are expected to take appropriate and fair corrective action in
38 | response to any instances of unacceptable behavior.
39 |
40 | Project maintainers have the right and responsibility to remove, edit, or
41 | reject comments, commits, code, wiki edits, issues, and other contributions
42 | that are not aligned to this Code of Conduct, or to ban temporarily or
43 | permanently any contributor for other behaviors that they deem inappropriate,
44 | threatening, offensive, or harmful.
45 |
46 | ## Scope
47 |
48 | This Code of Conduct applies both within project spaces and in public spaces
49 | when an individual is representing the project or its community. Examples of
50 | representing a project or community include using an official project e-mail
51 | address, posting via an official social media account, or acting as an appointed
52 | representative at an online or offline event. Representation of a project may be
53 | further defined and clarified by project maintainers.
54 |
55 | ## Enforcement
56 |
57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
58 | reported by contacting the project team at smaranjitghose@protonmail.com. All
59 | complaints will be reviewed and investigated and will result in a response that
60 | is deemed necessary and appropriate to the circumstances. The project team is
61 | obligated to maintain confidentiality with regard to the reporter of an incident.
62 | Further details of specific enforcement policies may be posted separately.
63 |
64 | Project maintainers who do not follow or enforce the Code of Conduct in good
65 | faith may face temporary or permanent repercussions as determined by other
66 | members of the project's leadership.
67 |
68 | ## Attribution
69 |
70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71 | available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72 |
73 | [homepage]: https://www.contributor-covenant.org
74 |
75 | For answers to common questions about this code of conduct, see
76 | https://www.contributor-covenant.org/faq
77 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2020 Anush Bhatia
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
Social Scheduler
2 | Social Media is everywhere. Who doesn't use it?. Twitter, Instagram, Facebook, Snapchat have evolved to be the means of modern communication.
3 |
4 |
5 |
6 | A project to automatically send invite to all of your social media like LinkedIn, Facebook, email, WhatsApp, Instagram as soon as he finishes filling the form.
7 |
8 |
9 | We can also send deadlines, important meeting announcement. Now no more delays and late candidates on interviews.
10 |
11 |
12 |
13 |
Skills Required
14 |
15 | - ReactJS
16 | - Nodejs
17 | - Python
18 | - Selenium
19 | - API for Various Social Media
20 |
21 |
Contributing Guidelines
4 |
5 |
6 | We value all the people who are interested in contributing to Social scheduler . This is required to create a unified development environment. These are mostly guidelines, not rules. Use your best judgement, and feel free to propose changes to this document in a pull request.
7 |
8 | We want your contributions to this project to be as easy and transparent as possible, whether it's:
9 | * Reporting a bug
10 | * Submitting a fix
11 | * Proposing new features
12 |
13 |
Steps
14 |
15 | **1.** Fork [this](https://github.com/anushbhatia/Social-Scheduler.git) repository.
16 |
17 | **2.** Clone the forked repository.
18 |
19 | ```
20 | git clone --depth 1 https://github.com//Social-Scheduler.git
21 | ```
22 |
23 |
24 |
25 | **3.** Navigate to the project directory.
26 |
27 | ```
28 | cd Social-Scheduler
29 | ```
30 |
31 | **4.** Add a reference to the original repository.
32 |
33 | ```
34 | git remote add upstream https://github.com/anushbhatia/Social-Scheduler.git
35 | ```
36 |
37 | **5.** See changes using
38 |
39 | ```
40 | git remote -v
41 | ```
42 |
43 | **6.** Create a new branch.
44 |
45 | ```
46 | git checkout -b
47 | ```
48 |
49 | **7.** Always take a pull from the upstream repository to your master branch to keep it at par with the main project.
50 |
51 | ```
52 | git pull upstream master
53 | ```
54 |
55 | **8.** Make changes in the source code after getting yourself assigned by the mentors.
56 |
57 |
58 |
59 | **9.** Add and then commit your changes.
60 |
61 | ```
62 | git add .
63 | git commit -m ""
64 | ```
65 |
66 | **10.** Push your local branch to the remote repository.
67 |
68 | ```
69 | git push -u origin
70 | ```
71 |
72 | **11.** Create a Pull Request!
73 |
74 | **12.** Finally, go to your repository in browser and click on `compare and pull requests`.
75 |
76 | **13.** Then add a title and description to your pull request that explains your precious effort.
77 |
78 |
79 |
80 | **14.** Click on `Create Pull Request`.
81 |
82 |
83 |
84 |
85 | **Congratulations!** Sit and relax, you've made your contribution to [Social Scheduler](https://github.com/anushbhatia/Social-Scheduler/) project.
86 |
87 |
88 |
34 | Lorem Ipsum is simply dummy text of the printing and
35 | typesetting industry. Lorem Ipsum has been the
36 | industry's standard dummy text ever since the 1500s,
37 | when an unknown printer took a galley of type and
38 | scrambled it to make a type specimen book. It has
39 | survived not only five centuries, but also the leap
40 | into electronic typesetting, remaining essentially
41 | unchanged. It was popularised in the 1960s with the
42 | release of Letraset sheets containing Lorem Ipsum
43 | passages, and more recently with desktop publishing
44 | software like Aldus PageMaker including versions of
45 | Lorem Ipsum.
46 |
51 | Lorem Ipsum is simply dummy text of the printing and
52 | typesetting industry. Lorem Ipsum has been the
53 | industry's standard dummy text ever since the 1500s,
54 | when an unknown printer took a galley of type and
55 | scrambled it to make a type specimen book. It has
56 | survived not only five centuries, but also the leap
57 | into electronic typesetting, remaining essentially
58 | unchanged. It was popularised in the 1960s with the
59 | release of Letraset sheets containing Lorem Ipsum
60 | passages, and more recently with desktop publishing
61 | software like Aldus PageMaker including versions of
62 | Lorem Ipsum.
63 |
64 |
65 |
66 |
67 | {/*-------All Social Icons------------------ */}
68 |