├── .github
└── ISSUE_TEMPLATE
│ ├── bug_report.md
│ └── feature_request.md
├── .vscode
└── settings.json
├── CODE_OF_CONDUCT.md
├── Contribute.md
├── MAA-VIMALAlogo.png
├── README.md
├── index.html
├── script.js
└── style.css
/.github/ISSUE_TEMPLATE/bug_report.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Bug report
3 | about: Create a report to help us improve
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Describe the bug**
11 | A clear and concise description of what the bug is.
12 |
13 | **To Reproduce**
14 | Steps to reproduce the behavior:
15 | 1. Go to '...'
16 | 2. Click on '....'
17 | 3. Scroll down to '....'
18 | 4. See error
19 |
20 | **Expected behavior**
21 | A clear and concise description of what you expected to happen.
22 |
23 | **Screenshots**
24 | If applicable, add screenshots to help explain your problem.
25 |
26 | **Desktop (please complete the following information):**
27 | - OS: [e.g. iOS]
28 | - Browser [e.g. chrome, safari]
29 | - Version [e.g. 22]
30 |
31 | **Smartphone (please complete the following information):**
32 | - Device: [e.g. iPhone6]
33 | - OS: [e.g. iOS8.1]
34 | - Browser [e.g. stock browser, safari]
35 | - Version [e.g. 22]
36 |
37 | **Additional context**
38 | Add any other context about the problem here.
39 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature_request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Feature request
3 | about: Suggest an idea for this project
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Is your feature request related to a problem? Please describe.**
11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12 |
13 | **Describe the solution you'd like**
14 | A clear and concise description of what you want to happen.
15 |
16 | **Describe alternatives you've considered**
17 | A clear and concise description of any alternative solutions or features you've considered.
18 |
19 | **Additional context**
20 | Add any other context or screenshots about the feature request here.
21 |
--------------------------------------------------------------------------------
/.vscode/settings.json:
--------------------------------------------------------------------------------
1 | {
2 | "liveServer.settings.port": 5502
3 | }
4 |
--------------------------------------------------------------------------------
/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 | sonawaneomkar2306@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 |
--------------------------------------------------------------------------------
/Contribute.md:
--------------------------------------------------------------------------------
1 |
2 | # Contributing to Maa-Vimala
3 |
4 | First off, thanks for taking the time to contribute! ❤️
5 |
6 | All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
7 |
8 | > And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
9 | > - Star the project
10 | > - Tweet about it
11 | > - Refer this project in your project's readme
12 | > - Mention the project at local meetups and tell your friends/colleagues
13 |
14 |
15 | ## Table of Contents
16 |
17 | - [I Have a Question](#i-have-a-question)
18 | - [I Want To Contribute](#i-want-to-contribute)
19 | - [Reporting Bugs](#reporting-bugs)
20 | - [Suggesting Enhancements](#suggesting-enhancements)
21 | - [Your First Code Contribution](#your-first-code-contribution)
22 | - [Improving The Documentation](#improving-the-documentation)
23 | - [Styleguides](#styleguides)
24 | - [Commit Messages](#commit-messages)
25 | - [Join The Project Team](#join-the-project-team)
26 |
27 |
28 |
29 | ## I Have a Question
30 |
31 | > If you want to ask a question, we assume that you have read the available [Documentation]().
32 |
33 | Before you ask a question, it is best to search for existing [Issues](https://github.com/Web403/Maa-Vimala/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
34 |
35 | If you then still feel the need to ask a question and need clarification, we recommend the following:
36 |
37 | - Open an [Issue](https://github.com/Web403/Maa-Vimala/issues/new).
38 | - Provide as much context as you can about what you're running into.
39 | - Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
40 |
41 | We will then take care of the issue as soon as possible.
42 |
43 |
57 |
58 | ## I Want To Contribute
59 |
60 | > ### Legal Notice
61 | > When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
62 |
63 | ### Reporting Bugs
64 |
65 |
66 | #### Before Submitting a Bug Report
67 |
68 | A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
69 |
70 | - Make sure that you are using the latest version.
71 | - Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](). If you are looking for support, you might want to check [this section](#i-have-a-question)).
72 | - To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/Web403/Maa-Vimalaissues?q=label%3Abug).
73 | - Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
74 | - Collect information about the bug:
75 | - Stack trace (Traceback)
76 | - OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
77 | - Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
78 | - Possibly your input and the output
79 | - Can you reliably reproduce the issue? And can you also reproduce it with older versions?
80 |
81 |
82 | We use GitHub issues to track bugs and errors. If you run into an issue with the project:
83 |
84 | - Open an [Issue](https://github.com/Web403/Maa-Vimala/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
85 | - Explain the behavior you would expect and the actual behavior.
86 | - Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
87 | - Provide the information you collected in the previous section.
88 |
89 | Once it's filed:
90 |
91 | - The project team will label the issue accordingly.
92 | - A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
93 | - If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
94 |
95 |
96 |
97 |
98 | ### Suggesting Enhancements
99 |
100 | This section guides you through submitting an enhancement suggestion for Maa-Vimala, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
101 |
102 |
103 | #### Before Submitting an Enhancement
104 |
105 | - Make sure that you are using the latest version.
106 | - Read the [documentation]() carefully and find out if the functionality is already covered, maybe by an individual configuration.
107 | - Perform a [search](https://github.com/Web403/Maa-Vimala/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
108 | - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
109 |
110 |
111 | #### How Do I Submit a Good Enhancement Suggestion?
112 |
113 | Enhancement suggestions are tracked as [GitHub issues](https://github.com/Web403/Maa-Vimala/issues).
114 |
115 | - Use a **clear and descriptive title** for the issue to identify the suggestion.
116 | - Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
117 | - **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
118 | - **Explain why this enhancement would be useful** to most Maa-Vimala users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
119 |
120 |
121 |
--------------------------------------------------------------------------------
/MAA-VIMALAlogo.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Omkar-Sonawane-23/Maa-Vimala/806c8d330802f6346a736224d77cc4a7eba921f7/MAA-VIMALAlogo.png
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
Maa-Vimala
2 |
3 | ### Calling all keyboard enthusiasts! 🚀 Ever wish you could conquer the digital realm without lifting a finger off your beloved keys? Well, say hello to our latest creation—a game-changing tool for developers who live for the thrill of a keyboard shortcut.
4 |
5 | ## Features
6 |
7 | 1. ### Perform Search using Keyword like
8 | - ### 📺 Youtube
9 | - ### 🔍 Google
10 | - ### 📚 Wikipedia
11 |
12 | 2. ### Use only one word to perform Word Search (Without Space)
13 | 3. ### Perform Calculations 🧮
14 | 5. ### Weather Information ☁️
15 | 4. ### Set ToDo's (Coming Soon ❗)
16 |
17 | ## How To Add This on a New Tab
18 |
19 | git clone https://github.com/Web403/Maa-Vimala
20 |
21 | path/to/Maa-Vimala/index.html
22 | Go To Browser -> Setting search for Home page
23 | set to Custom Url
24 | Paste your Path To Index File.
25 |
26 | ## Contributing
27 |
28 | Pull requests are welcome.
29 | Read Contribute.md File First
30 | For major changes, please open an issue first to discuss what you would like to change.
31 |
32 |
33 | ## How To Use It?
34 |
35 | 1. Just Start Typing
36 | 2. Press Enter After Complete.
37 | 3. Watch the video for more 📽️.
38 |
39 | [![Watch the video]](https://github.com/Web403/Maa-Vimala/assets/130058150/06f7bc4e-fbb0-418c-b080-1b4b05c97d1b)
40 |
41 | ## Contributing
42 |
43 | Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
44 |
45 | Please make sure to update tests as appropriate.
46 |
47 |
48 | # Join the Discord
49 | https://discord.gg/uD7x8Mah
50 |
--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 | Maa-Vimala
13 |
14 |
15 |
16 |
17 |
27 |
28 |
39 |
40 |