sanju-0/chrome-extension

Best way to get started in a web project by making a cool Chrome Extension that generates random jokes. Beginner friendly code so that you can understand things easily.

chrome-extension's Issues

Close button for popup.

There is no option to close the popup when it is opened in the tab.

Add the button to activate 'close' event.

Add Issues

As the maintainer of a Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.

Recommendations:

• Add issues of varying difficulty to the repo often.
• Generate issues even if you plan on solving them, so the repository appears as active.
• Contribute/commit often to the repo so it does not go stale.

In order to submit your project into CX you will need at least one issue, but we recommend more so other students have an idea on where to start.

Add Topics

In Community Exchange, GitHub Topics will help the discoverability of your project. You should create topics pertaining to:

• the tech stack you used on the project
• the subject matter of your repo

There is a limit of 20 topics you can add to your repo. There is no need to go overboard with topics. We recommend under 10 topics. You can add topics by following these instructions.

Add Code of Conduct

We recommend that every repo has a code of conduct. If you don’t feel comfortable creating your own Code of Conduct from scratch, we highly recommend using one of the templates provided by GitHub. If you do use a template, please read through the template and ensure that you can and will abide by the Code of Conduct.

Please follow these instructions on how to add a Code of Conduct.

Update README.md

Your README is already looking really good! 🎉 Because a README is often the first item a visitor will see, here are some additional things I recommend adding:

• How users can get started with the project
  * How to setup the project on their computer
  * How to contribute to your project
• Mention or link to your code of conduct
• Describe who can contribute to the project

You might also be interested in creating a CONTRIBUTING.md file, but we recommend starting simple with the bullet points above, and once you start to see an increase in users interested in contributing, you should consider a CONTRIBUTING.md file so you don’t find yourself overwhelmed with questions from other users.

You can add animations

You can add animation when jokes pop up we can add lit bit animation in that or we can also add animation on joke text to make it more attractive and it make more fun to read jokes.

Add a repo description

Other than GitHub Topics, your description will be the primary way of catching the users eyes. Your repo description should be clear and concise. Ask yourself:

• In one sentence, how do I convey what my repo does?
• What type of users am I interested in attracting to my repo?
• If I was a user, what words or phrases might spark my interest?

Community Exchange Introduction/Tracking

👋 Hi @Sanju-github002,

I am your GitHub mentor for the GitHub Education, Community Exchange (CX) project. I'll be collaborating with you on preparing your repo for CX.

You mentioned in your submission that you wanted to submit a Collaborate repo. This means that you want to invite other students to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for a Collaborate CX submission on June 1, 2022.

This issue will serve as a tracking issue to track all issues related to CX. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.

If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.

I look forward to working with you!

CX Issues:

• #2
• #3
• #4
• #5
• #6
• #7

Add templates for issues

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

We recommend creating a “Report Bug” and “Feature Request” issue template. In case it's helpful, there are some instructions for adding templates here. 😄

Some suggested prompts/questions you can add to a “Report Bug” template are:

• Briefly describe the bug
• What is the expected behavior?
• Please provide step by step instructions on how to reproduce the bug

Some suggested prompts/questions you can add to a “Feature Request” issue template are:

• Briefly describe your feature request
• What problem is this feature trying to solve?
• How do we know when the feature is complete?

Change API

I want to change API with another API through which we get more funny jokes for API changing you should change the mainfest.json file. You should have knowledge of APIs for that.

Change in styling

It looks very simple I want to add the latest effects that make it more good-looking.
In this,

you can change the CSS file and add more effects and make it a more attractive extension ✨

You can add animations

Now it have a simple animation you can add background and more text animation.
Try to add some attractive animation or something that make extension more attractive :)