"
4 | labels: [":bug: bug"]
5 | body:
6 | - type: textarea
7 | id: current_behaviour
8 | attributes:
9 | label: Current Behaviour
10 | description: A concise description of what you are currently experiencing
11 | validations:
12 | required: true
13 | - type: textarea
14 | id: expected_behaviour
15 | attributes:
16 | label: Expected Behaviour
17 | description: A concise description of what is expected to happen
18 | validations:
19 | required: true
20 | - type: textarea
21 | id: steps_reproduce
22 | attributes:
23 | label: Steps To Reproduce
24 | description: Steps to reproduce the behavior.
25 | placeholder: |
26 | 1. Go to...
27 | 2. Click on...
28 | 3. See error...
29 | validations:
30 | required: false
31 | - type: textarea
32 | id: anything_else
33 | attributes:
34 | label: Anything else?
35 | description: |
36 | Links? References? Anything that will give us more context about the issue you are encountering!
37 |
38 | Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
39 | validations:
40 | required: false
41 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/config.yml:
--------------------------------------------------------------------------------
1 | blank_issues_enabled: true
2 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/docs.yml:
--------------------------------------------------------------------------------
1 | name: "📝 Docs"
2 | description: "Found a security issue report it here"
3 | title: "[DOCS] :memo: "
4 | labels: [":memo: documentation"]
5 | body:
6 | - type: textarea
7 | id: description
8 | attributes:
9 | label: Description
10 | description: A concise description if you want us to update or create new documentation
11 | validations:
12 | required: false
13 | - type: textarea
14 | id: anything_else
15 | attributes:
16 | label: Anything else?
17 | description: |
18 | Links? References? Anything that will give us more context about the issue you are encountering!
19 |
20 | Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
21 | validations:
22 | required: false
23 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature_request.yml:
--------------------------------------------------------------------------------
1 | name: "✨ Feature Request"
2 | description: "Suggest and idea for this project"
3 | title: "[FEAT] :sparkles: "
4 | labels: [":sparkles: enhancement"]
5 | body:
6 | - type: textarea
7 | id: description
8 | attributes:
9 | label: Description
10 | description: A concise description of what you want in this project
11 | validations:
12 | required: false
13 | - type: textarea
14 | id: anything_else
15 | attributes:
16 | label: Anything else?
17 | description: |
18 | Links? References? Anything that will give us more context about the issue you are encountering!
19 |
20 | Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
21 | validations:
22 | required: false
23 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/refactor.yml:
--------------------------------------------------------------------------------
1 | name: "♻ Refactor Code"
2 | description: "Refactor your code"
3 | title: "[REFACTOR] :recycle: "
4 | labels: [":recycle: refactor"]
5 | body:
6 | - type: textarea
7 | id: description
8 | attributes:
9 | label: Description
10 | description: A concise description of how we can refactor our code
11 | validations:
12 | required: false
13 | - type: textarea
14 | id: anything_else
15 | attributes:
16 | label: Anything else?
17 | description: |
18 | Links? References? Anything that will give us more context about the issue you are encountering!
19 |
20 | Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
21 | validations:
22 | required: false
23 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/security_issue.yml:
--------------------------------------------------------------------------------
1 | name: "🔒 Security Issue"
2 | description: "Found a security issue report it here"
3 | title: "[SECURITY] :lock: "
4 | labels: [":lock: security"]
5 | body:
6 | - type: textarea
7 | id: description
8 | attributes:
9 | label: Description
10 | description: A concise description of the security issue
11 | validations:
12 | required: true
13 | - type: textarea
14 | id: how_to_solve
15 | attributes:
16 | label: How can we solve this
17 | description: Please tell us how can we solve this issue
18 | validations:
19 | required: false
20 | - type: textarea
21 | id: anything_else
22 | attributes:
23 | label: Anything else?
24 | description: |
25 | Links? References? Anything that will give us more context about the issue you are encountering!
26 |
27 | Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
28 | validations:
29 | required: false
30 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/test.yml:
--------------------------------------------------------------------------------
1 | name: "🧪 Test"
2 | description: "Issue related to tests"
3 | title: "[TEST] :test_tube: "
4 | labels: [":test_tube: tests"]
5 | body:
6 | - type: textarea
7 | id: description
8 | attributes:
9 | label: Description
10 | description: A concise description if you want us to write new tests or check on failing tests
11 | validations:
12 | required: false
13 | - type: textarea
14 | id: anything_else
15 | attributes:
16 | label: Anything else?
17 | description: |
18 | Links? References? Anything that will give us more context about the issue you are encountering!
19 |
20 | Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
21 | validations:
22 | required: false
23 |
--------------------------------------------------------------------------------
/.github/PULL_REQUEST_TEMPLATE.md:
--------------------------------------------------------------------------------
1 |
2 |
3 | ### Description
4 |
5 | Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
6 |
7 | ### Checklist:
8 |
9 |
10 |
11 | - [ ] This pull request follow our contribution guidelines
12 | - [ ] I have performed a self-review of my own code
13 | - [ ] I have commented my code, particularly in hard-to-understand areas
14 | - [ ] I have made corresponding changes to the documentation (postman and swagger)
15 | - [ ] I have written tests for the code
16 | - [ ] I have updated .env.example file for new .env variables
17 |
18 |
19 |
20 | ### What is current behavior?
21 |
22 |
23 |
24 | Closes #(issue_number)
25 |
26 | ### What is new behavior?
27 |
28 |
29 |
30 | ### Breaking Changes?
31 |
32 |
33 |
34 | ### Additional information
35 |
36 |
37 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
2 |
3 | # documentation
4 | /docs
5 |
6 | # dependencies
7 | /node_modules
8 | /.pnp
9 | .pnp.js
10 |
11 | # testing
12 | /coverage
13 |
14 | # production
15 | /build
16 |
17 | # misc
18 | .DS_Store
19 | .env
20 | .env.local
21 | .env.development.local
22 | .env.test.local
23 | .env.production.local
24 |
25 | npm-debug.log*
26 | yarn-debug.log*
27 | yarn-error.log*
28 |
29 |
30 |
--------------------------------------------------------------------------------
/.husky/commit-msg:
--------------------------------------------------------------------------------
1 | #!/usr/bin/env sh
2 | . "$(dirname -- "$0")/_/husky.sh"
3 |
4 | npx commitlint --edit $1
5 |
--------------------------------------------------------------------------------
/.vscode/settings.json:
--------------------------------------------------------------------------------
1 | {
2 | "cSpell.words": ["IAPI"],
3 | "docwriter.style": "Auto-detect",
4 | "editor.tabSize": 4,
5 | "editor.comments.insertSpace": true,
6 | "editor.autoIndent": "full",
7 | "prettier.tabWidth": 4,
8 | "prettier.arrowParens": "always",
9 | "prettier.bracketSpacing": true,
10 | "editor.insertSpaces": false,
11 | "prettier.useTabs": true,
12 | "dotenv.enableAutocloaking": false
13 | }
14 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | We as members, contributors, and leaders pledge to make participation in our
6 | community a harassment-free experience for everyone, regardless of age, body
7 | size, visible or invisible disability, ethnicity, sex characteristics, gender
8 | identity and expression, level of experience, education, socio-economic status,
9 | nationality, personal appearance, race, religion, or sexual identity
10 | and orientation.
11 |
12 | We pledge to act and interact in ways that contribute to an open, welcoming,
13 | diverse, inclusive, and healthy community.
14 |
15 | ## Our Standards
16 |
17 | Examples of behavior that contributes to a positive environment for our
18 | community include:
19 |
20 | - Demonstrating empathy and kindness toward other people
21 | - Being respectful of differing opinions, viewpoints, and experiences
22 | - Giving and gracefully accepting constructive feedback
23 | - Accepting responsibility and apologizing to those affected by our mistakes,
24 | and learning from the experience
25 | - Focusing on what is best not just for us as individuals, but for the
26 | overall community
27 |
28 | Examples of unacceptable behavior include:
29 |
30 | - The use of sexualized language or imagery, and sexual attention or
31 | advances of any kind
32 | - Trolling, insulting or derogatory comments, and personal or political attacks
33 | - Public or private harassment
34 | - Publishing others' private information, such as a physical or email
35 | address, without their explicit permission
36 | - Other conduct which could reasonably be considered inappropriate in a
37 | professional setting
38 |
39 | ## Enforcement Responsibilities
40 |
41 | Community leaders are responsible for clarifying and enforcing our standards of
42 | acceptable behavior and will take appropriate and fair corrective action in
43 | response to any behavior that they deem inappropriate, threatening, offensive,
44 | or harmful.
45 |
46 | Community leaders have the right and responsibility to remove, edit, or reject
47 | comments, commits, code, wiki edits, issues, and other contributions that are
48 | not aligned to this Code of Conduct, and will communicate reasons for moderation
49 | decisions when appropriate.
50 |
51 | ## Scope
52 |
53 | This Code of Conduct applies within all community spaces, and also applies when
54 | an individual is officially representing the community in public spaces.
55 | Examples of representing our community include using an official e-mail address,
56 | posting via an official social media account, or acting as an appointed
57 | representative at an online or offline event.
58 |
59 | ## Enforcement
60 |
61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
62 | reported to the community leaders responsible for enforcement at
63 | mutiiemail@gmail.com.
64 | All complaints will be reviewed and investigated promptly and fairly.
65 |
66 | All community leaders are obligated to respect the privacy and security of the
67 | reporter of any incident.
68 |
69 | ## Enforcement Guidelines
70 |
71 | Community leaders will follow these Community Impact Guidelines in determining
72 | the consequences for any action they deem in violation of this Code of Conduct:
73 |
74 | ### 1. Correction
75 |
76 | **Community Impact**: Use of inappropriate language or other behavior deemed
77 | unprofessional or unwelcome in the community.
78 |
79 | **Consequence**: A private, written warning from community leaders, providing
80 | clarity around the nature of the violation and an explanation of why the
81 | behavior was inappropriate. A public apology may be requested.
82 |
83 | ### 2. Warning
84 |
85 | **Community Impact**: A violation through a single incident or series
86 | of actions.
87 |
88 | **Consequence**: A warning with consequences for continued behavior. No
89 | interaction with the people involved, including unsolicited interaction with
90 | those enforcing the Code of Conduct, for a specified period of time. This
91 | includes avoiding interactions in community spaces as well as external channels
92 | like social media. Violating these terms may lead to a temporary or
93 | permanent ban.
94 |
95 | ### 3. Temporary Ban
96 |
97 | **Community Impact**: A serious violation of community standards, including
98 | sustained inappropriate behavior.
99 |
100 | **Consequence**: A temporary ban from any sort of interaction or public
101 | communication with the community for a specified period of time. No public or
102 | private interaction with the people involved, including unsolicited interaction
103 | with those enforcing the Code of Conduct, is allowed during this period.
104 | Violating these terms may lead to a permanent ban.
105 |
106 | ### 4. Permanent Ban
107 |
108 | **Community Impact**: Demonstrating a pattern of violation of community
109 | standards, including sustained inappropriate behavior, harassment of an
110 | individual, or aggression toward or disparagement of classes of individuals.
111 |
112 | **Consequence**: A permanent ban from any sort of public interaction within
113 | the community.
114 |
115 | ## Attribution
116 |
117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118 | version 2.0, available at
119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120 |
121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
122 | enforcement ladder](https://github.com/mozilla/diversity).
123 |
124 | [homepage]: https://www.contributor-covenant.org
125 |
126 | For answers to common questions about this code of conduct, see the FAQ at
127 | https://www.contributor-covenant.org/faq. Translations are available at
128 | https://www.contributor-covenant.org/translations.
129 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | ## Contributing
2 |
3 | [fork]: /fork
4 | [pr]: /compare
5 | [code-of-conduct]: CODE_OF_CONDUCT.md
6 |
7 | Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
8 |
9 | Please note that this project is released with a [Contributor Code of Conduct][code-of-conduct]. By participating in this project you agree to abide by its terms.
10 |
11 | ## Issues and PRs
12 |
13 | If you have suggestions for how this project could be improved, or want to report a bug, open an issue! We'd love all and any contributions. If you have questions, too, we'd love to hear them.
14 |
15 | We'd also love PRs. If you're thinking of a large PR, we advise opening up an issue first to talk about it, though! Look at the links below if you're not sure how to open a PR.
16 |
17 | 1. [Fork][fork] and clone the repository.
18 | 2. Configure and install the dependencies: `yarn install`.
19 | 3. Create a new branch: `git checkout -b my-branch-name`.
20 | 4. Work on your issue/feature
21 | 5. Before committing the changes run tests using `yarn test`
22 | 6. Follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) for writing commit messages
23 | 7. Push to your fork and [submit a pull request][pr] in `main` branch
24 | 8. Pat your self on the back and wait for your pull request to be approved and merged.
25 |
26 | Here are a few things you can do that will increase the likelihood of your pull request being accepted:
27 |
28 | - Keep your changes as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
29 | - Follow [Conventional commits](https://www.conventionalcommits.org/en/v1.0.0/).
30 |
31 | Work in Progress pull requests are also welcome to get feedback early on, or if there is something blocked you. (just mark them as draft)
32 |
33 | ## Resources
34 |
35 | - [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
36 | - [About Pull Requests](https://help.github.com/articles/about-pull-requests/)
37 | - [GitHub Help](https://help.github.com)
38 | - [Conventional commits](https://www.conventionalcommits.org/en/v1.0.0/)
39 | - [Conventional commits vscode extension](https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits)
40 | - [Github issues and pull requests vscode extension](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github)
41 |
--------------------------------------------------------------------------------
/Dockerfile:
--------------------------------------------------------------------------------
1 | FROM node:alpine
2 |
3 | WORKDIR /usr/src/app
4 |
5 | COPY package.json .
6 | COPY yarn.lock .
7 |
8 | RUN yarn install
9 |
10 | COPY . .
11 |
12 | CMD ["yarn", "run", "start"]
13 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2022 Multi Email
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 |
2 | [](#contributors-)
3 |
4 |
5 | # Technologies Used
6 |
7 | - React
8 | - Redux
9 | - Tailwind CSS
10 |
11 | # Features
12 |
13 | - Admin dashboard
14 | - User settings and or user dashboard
15 | - send emails
16 | - recive emails
17 | - Connections through other parties ie discord, twitter, facebook etc..
18 |
19 | # Setup
20 |
21 | ## Windows
22 |
23 | ```
24 | git clone https://github.com/MultiEmail/MultiEmail-frontend.git
25 | cd MultiEmail-frontend
26 | yarn install
27 | yarn dev
28 | ```
29 |
30 | # Linux
31 |
32 | ```
33 | git clone https://github.com/MultiEmail/MultiEmail-frontend.git && cd MultiEmail-frontend && yarn install && yarn dev
34 | ```
35 |
36 | # Docker
37 |
38 | For development server (http://localhost:3000)
39 | ```bash
40 | git clone https://github.com/MultiEmail/MultiEmail-frontend.git
41 | cd MultiEmail-frontend
42 | docker compose --env-file ./.env
43 | ```
44 |
45 |
46 | # Wanna join the team?
47 |
48 | - [Discord server](https://discord.gg/8kTdfWmuQa)
49 | - [Postman team](https://www.postman.com/multiemail/workspace/muti-email-rest-api/overview)
50 |
51 |
52 | ## Contributing
53 |
54 | - Contributions make the open source community such an amazing place to learn, inspire, and create.
55 | - Any contributions you make are **truly appreciated**.
56 | - Check out our [contribution guidelines](/CONTRIBUTING.md) for more information.
57 |
58 |
59 | License
60 |
61 |
62 |
63 |
64 | This project is Licensed under the MIT License. Please go through the License atleast once before making your contribution.
65 |
66 |
67 | ## Contributors ✨
68 |
69 | Thanks goes to these wonderful people ❤:
70 |
71 |
72 |
73 |
74 |
In our live's, we often have different mail account's on different services such as our personal email, our work, our school etc.
42 |
43 |
44 |
45 |
46 | {
47 | mail.map((x, i) => (
48 |
49 |
{x}
50 |
51 |
52 | ))
53 | }
54 |
55 |
56 |
{
57 | // Check the current position of the page and scroll to the next section if not at the bottom
58 | if (window.scrollY < window.innerHeight) {
59 | window.scrollTo({
60 | top: window.innerHeight,
61 | behavior: 'smooth',
62 | });
63 | }
64 | else {
65 | window.scrollTo({
66 | top: 0,
67 | behavior: 'smooth',
68 | });
69 | }
70 | }}>
71 |
72 |
73 |
74 |
75 |
76 |
77 |
78 |
79 |
Organized
80 |
81 |
82 |
83 |
Save's Time
84 |
85 |
86 |
87 |
88 |
89 |
Customize
90 |
91 |
92 |
93 |
Open Source
94 |
95 |
96 |
97 |
98 |
So, Multi Email?
99 |
Multi Email is a web app that allows you to manage all your email accounts in one place. It organizes your emails and offers ton of customization's.
100 |
101 |
102 |
103 | //
104 | //
105 | //
106 | //
107 | //
114 | //
115 | //
116 | //
117 | // Multi Email development team is carried out by
118 | // passionate developers
119 | //
120 | //
121 | // Project to manage multiple emails at once with lots
122 | // of customization. You can send and receive emails.
123 | // Desktop notifications can be modified. I also want
124 | // to eventually make a mobile version of this app so
125 | // that the desktop and mobile versions can
126 | // communicate.
127 | //
128 | //
129 | // {' '}
130 | // Later on we will also make it a vscode extention, so
131 | // if you spent a lot of time in vscode that's the
132 | // extention you want.
133 | //
134 | //
135 | //
136 | //
137 | //
138 | );
139 | };
140 |
141 | export default About;
--------------------------------------------------------------------------------
/src/pages/home/Home.tsx:
--------------------------------------------------------------------------------
1 | import { FC } from "react";
2 | import sample from "../../assets/photos/product-sample.png";
3 | import logo from "../../assets/logos/icon-transparent.svg";
4 | import { motion } from "framer-motion";
5 | import { Link } from "react-router-dom";
6 |
7 | const Home: FC = () => {
8 | return (
9 |
10 |