updated the repo

ankita841 · Jun 25, 2020 · 8eda61f · 8eda61f
1 parent aa93e1d
commit 8eda61f
Show file tree

Hide file tree

Showing 34 changed files with 187 additions and 14 deletions.
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -0,0 +1,54 @@
+# Contributing to Profext
+We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
+
+- Reporting a bug
+- Discussing the current state of the code
+- Submitting a fix
+- Proposing new features
+- Becoming a maintainer
+
+## We Develop with Github
+We use github to host code, to track issues and feature requests, as well as accept pull requests.
+
+## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
+Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
+
+1. Fork the repo and create your branch from `master`.
+2. If you've added code that should be tested, add tests.
+3. If you've changed APIs, update the documentation.
+4. Ensure the test suite passes.
+5. Make sure your code lints.
+6. Issue that pull request!
+
+## Any contributions you make will be under the MIT Software License
+In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
+
+## Report bugs using Github's [issues](https://github.com/briandk/transcriptase-atom/issues)
+We use GitHub issues to track public bugs. Report a bug by [opening a new issue](); it's that easy!
+
+## Write bug reports with detail, background, and sample code
+
+
+**Great Bug Reports** tend to have:
+
+- A quick summary and/or background
+- Steps to reproduce
+  - Be specific!
+  - Give sample code if you can.
+- What you expected would happen
+- What actually happens
+- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
+
+People *love* thorough bug reports. I'm not even kidding.
+
+## Use a Consistent Coding Style
+I'm again borrowing these from [Facebook's Guidelines](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
+
+* 2 spaces for indentation rather than tabs
+* You can try running `npm run lint` for style unification
+
+## License
+By contributing, you agree that your contributions will be licensed under its MIT License.
+
+## References
+This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
diff --git a/LICENSE b/LICENSE
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2020 Profext
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/README.md b/README.md
@@ -6,7 +6,7 @@
 # This project is a part of Student Code In 2020 👣
   OPEN SOURCE CONTEST - STUDENT CODE IN
   ### About Student Code In 💻
-  Student Code-in is a global program that helps students grow with “OPEN SOURCE”. It is a 2 months long Open-Source initiative which provides you the best platform to improve your skills and abilities by contributing to vast variety of OPEN SOURCE Projects. In this,all the registered participants would get an exquisite opportunity to interact with the mentors and the Organizing Team. 
+  Student Code-in is a global program that helps students grow with “OPEN SOURCE”. It is a 2 months long Open-Source initiative that provides you the best platform to improve your skills and abilities by contributing to a vast variety of OPEN SOURCE Projects. In this, all the registered participants would get an exquisite opportunity to interact with the mentors and the Organizing Team. 
 
 <div align="center">
 
@@ -33,7 +33,7 @@
 ![GitHub forks](https://img.shields.io/github/forks/garimasingh128/profext.svg?logo=github&color=teal)
 ![GitHub top language](https://img.shields.io/github/languages/top/garimasingh128/profext?color=yellow&logo=javascript)
 
-A profile 🔎 search engine for accessing my all social media profile in one tap.👨‍💻👩‍. This chrome extension let's you track your profiles on any account in a single click.
+A profile 🔎 search engine for accessing my all social media profile in one tap.👨‍💻👩‍. This chrome extension lets you track your profiles on any account in a single click.
 
 ## 📋 Table of Contents
  ➡️   [Vision](#-vision)
@@ -63,7 +63,7 @@ A profile 🔎 search engine for accessing my all social media profile in one ta
 
 
 ## 👩‍ Vision
-Getting all your social media profiles under one button click so that you don't have to manually search and do the hassle of searching your profile handles while making your resume, filling job opportunities forms, registering for events etc.
+Getting all your social media profiles under one button click so that you don't have to manually search and do the hassle of searching your profile handles while making your resume, filling job opportunities forms, registering for events, etc.
 
 ## ❤️ Inspiration
 This is motivated by [Traversy Media tutorial on Google Chrome Extention](https://www.youtube.com/watch?v=wHZCYi1K664).
@@ -90,16 +90,16 @@ This is motivated by [Traversy Media tutorial on Google Chrome Extention](https:
  ```bash
  git clone github.com/your_username/profext.git
  ```
- 2. Open the folder in your favourite code editor and start adding modifications.
+ 2. Open the folder in your favorite code editor and start adding modifications.
  3.  Load the folder in `chrome://extensions/` on chrome (Load unpacked)
 
  ## 💻 Development guidelines
 
-1.  Put all the code in one of the existing files in  `/src`  . If you add a new file, make a relavent modification to  `build.js`  .
+1.  Put all the code in one of the existing files in  `/src`. If you add a new file, make a relevant modification to  `build.js`.
 
-3.  Push all the code to your own branch. Once you are sure its working, merge it with  `dev`  branch. Let's maintain only the stable and released versions on the  `master`  branch.
+3.  Push all the code to your own branch. Once you are sure it is working, merge it with the `dev`  branch. Let's maintain only the stable and released versions on the  `master`  branch.
 
-4.  Write kick-ass, readable and clean code.
+4.  Write a kick-ass, readable, and clean code.
 
 5.  Load the  `/build`  folder in  `chrome://extensions/`  on chrome (Load unpacked)
 
@@ -113,23 +113,23 @@ Resources to learn Git:
 -  https://try.github.io/
 
 ## 🧐 Simple things to keep in mind 
-- The first step is to create a manifest file named `manifest.json`. This is a metadata file in JSON format that contains properties like your extension’s name, description, version number and so on. In this file we tell Chrome what the extension is going to do, and what permissions it requires.
+- The first step is to create a manifest file named `manifest.json`. This is a metadata file in JSON format that contains properties like your extension’s name, description, version number, and so on. In this file, we tell Chrome what the extension is going to do, and what permissions it requires.
 - To test if the extension works, visit `chrome://extensions` in your browser and ensure that the **Developer mode** checkbox in the top right-hand corner is checked.
 - Click **Load unpacked extension** and select the directory in which your extension files live. If the extension is valid, it will be active straight away so you can open a new tab to see your extension.
-- When your first Chrome extension looks nice and works like it should, it’s time to publish it to the Chrome Store. Simply follow [this link](https://chrome.google.com/webstore/developer/dashboard) to go to your Chrome Web Store dashboard (you’ll be asked to sign in to your Google account if you’re not). Then click the `**Add new item**` button, accept the terms and you will go to the page where you can upload your extension. Now compress the folder that contains your project and upload that ZIP file.
-- As a web developer, it’s very easy to create a Chrome extension in a short amount of time. All you need is some HTML, CSS, JavaScript and a basic knowledge of how to add functionality through some of the JavaScript APIs that Chrome exposes. Your initial setup can be published inside the Chrome Web Store within just 20 minutes. Building an extension that’s new, worthwhile or looks nice will take some more time. But it’s all up to you!
+- When your first Chrome extension looks nice and works as it should, it’s time to publish it to the Chrome Store. Simply follow [this link](https://chrome.google.com/webstore/developer/dashboard) to go to your Chrome Web Store dashboard (you’ll be asked to sign in to your Google account if you’re not). Then click the `**Add new item**` button, accept the terms and you will go to the page where you can upload your extension. Now compress the folder that contains your project and upload that ZIP file.
+- As a web developer, it’s very easy to create a Chrome extension in a short amount of time. All you need is some HTML, CSS, JavaScript, and basic knowledge of how to add functionality through some of the JavaScript APIs that Chrome exposes. Your initial setup can be published inside the Chrome Web Store within just 20 minutes. Building an extension that’s new, worthwhile or looks nice will take some more time. But it’s all up to you!
 
 ## 💻 System Requirements
 -  Google Chrome
 -  Git
--  Code Editor (Visual Studio Code,Sublime Text)
+-  Code Editor (Visual Studio Code, Sublime Text)
 
 ## 🏆 Contributing
 
-Please read  CONTRIBUTING.md  for information on how to contribute to profext-extension.
+Please read  [CONTRIBUTING.md](CONTRIBUTING.md)  for information on how to contribute to profext-extension.
 ## 👬 Owner
 
-[Garima Singh](https://github.com/garimasingh128)
+<a href="https://github.com/garimasingh128"><img src="https://avatars3.githubusercontent.com/u/44302373?s=460&u=efaafa72f4d83d40b66fc68258d14cebbf1d7de0&v=4" width="100px;" alt=""/><br /><sub><b>Garima Singh</b></sub></a><br />
 
 [![Codacy Badge](https://api.codacy.com/project/badge/Grade/69a18fa3a0574431b6f9463f02a8e7a8)](https://app.codacy.com/manual/garimasingh128/profext?utm_source=github.com&utm_medium=referral&utm_content=garimasingh128/profext&utm_campaign=Badge_Grade_Dashboard)
 [![Relative date](https://img.shields.io/date/1577392258?color=important&label=started&logo=github)](https://github.com/garimasingh128/) [![Maintenance](https://img.shields.io/maintenance/yes/2020?color=green&logo=github)](https://github.com/garimasingh128/)

diff --git a/design/font/._BukhariScript-Regular.otf b/design/font/._BukhariScript-Regular.otf
diff --git a/design/font/Anaktoria.otf b/design/font/Anaktoria.otf
diff --git a/design/font/Anton-Regular.ttf b/design/font/Anton-Regular.ttf
diff --git a/design/font/BukhariScript-Regular.otf b/design/font/BukhariScript-Regular.otf
diff --git a/design/font/BukhariScript-Regular.ttf b/design/font/BukhariScript-Regular.ttf
diff --git a/design/font/CooperHewitt-Book.otf b/design/font/CooperHewitt-Book.otf
diff --git a/design/font/CooperHewitt-Medium.otf b/design/font/CooperHewitt-Medium.otf
diff --git a/design/font/Prata-Regular.ttf b/design/font/Prata-Regular.ttf
diff --git a/design/font/alegreya-bold_[allfont.net].ttf b/design/font/alegreya-bold_[allfont.net].ttf
diff --git a/design/form.png b/design/form.png
diff --git a/design/images/back.png b/design/images/back.png
diff --git a/design/images/background.jpg b/design/images/background.jpg
diff --git a/design/images/background_splash.png b/design/images/background_splash.png
diff --git a/design/images/bitbucket.png b/design/images/bitbucket.png
diff --git a/design/images/github.png b/design/images/github.png
diff --git a/design/images/gitlab.png b/design/images/gitlab.png
diff --git a/design/images/globe.png b/design/images/globe.png
diff --git a/design/images/gmail.png b/design/images/gmail.png
diff --git a/design/images/image1.png b/design/images/image1.png
diff --git a/design/images/insta.png b/design/images/insta.png
diff --git a/design/images/linkedin.png b/design/images/linkedin.png
diff --git a/design/images/medium.png b/design/images/medium.png
diff --git a/design/images/stackoverflow-512.png b/design/images/stackoverflow-512.png
diff --git a/design/images/twitter.png b/design/images/twitter.png
diff --git a/design/images/wordpress.png b/design/images/wordpress.png
diff --git a/design/popup.png b/design/popup.png
diff --git a/design/splash screen.png b/design/splash screen.png
diff --git a/pull_request_template.md b/pull_request_template.md
@@ -0,0 +1,38 @@
+# Description
+
+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.
+
+Fixes # (issue)
+
+## Type of change
+
+Please delete options that are not relevant.
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] This change requires a documentation update
+
+# How Has This Been Tested?
+
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
+
+- [ ] Test A
+- [ ] Test B
+
+**Test Configuration**:
+* Firmware version:
+* Hardware:
+* Toolchain:
+* SDK:
+
+# Checklist:
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published in downstream modules
diff --git a/splash_screen.html b/splash_screen.html
@@ -162,7 +162,9 @@
       <main class="valign-wrapper">
          <span class="container grey-text text-lighten-1 ">
             <h1 style="font-size: 100px;font-family: CommercialScript BT;
-               font-weight: 900;margin-top: 175px;margin-left: 125px;"><img src="images/icons8-100.png" height="85" width="85">Profext</h1>
+               font-weight: 900;margin-top: 175px;margin-left: 125px;">
+               <img src="images/icons8-100.png" height="85" width="85">Profext
+            </h1>
             <a class="btn" href="edit.html" style="margin-left: 200px;text-decoration:none;">Get Started</a>
          </span>
       </main>