-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Update keywords on docs pages #223
Comments
Hi @BekahHW, how are you doing? Can I work on this issue if you could assign it to me? Also, may I ask for help if I get stuck? |
@Suraj-kumar00 sure. Just read our Contributing docs to learn how to assign yourself |
Yeah sure, thanks @BekahHW |
|
Thanks for taking this on! If you have not already, join the conversation in our Discord |
Thanks for being interested in this issue. It looks like this ticket is already assigned to a contributor. Please communicate with the assigned contributor to confirm the status of the issue. |
Hi @BekahHW, actually I'm getting the error after running the command npm test
npm info using npm@10.2.3
npm info using node@v18.19.0
npm ERR! Missing script: "test" // this is the error I'm encountering
npm ERR!
npm ERR! To see a list of scripts, run:
npm ERR! npm run
npm ERR! A complete log of this run can be found in: C:\Users\offic\AppData\Local\npm-cache\_logs\2024-01-15T15_47_34_579Z-debug-0.log there is no test file in package.json . |
@Suraj-kumar00 did you follow the instructions for running in the readme?
|
Yes sure I did @BekahHW |
After cloning in the terminal, you should start with |
Yeah actually I did all things again and than it's working in local host, tomorrow I'll create pull request. |
🎉 This issue has been resolved in version 1.61.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Current
Right now, there's not been consistency on keywords. Keywords are a way to improve the SEO of the pages. We should do a review of each page to determine if we could be doing a better job.
ref: #213 (comment)
Solution
Go through the pages most likely to be viewed by someone looking for answers about open source. Update the keywords to showcase the resource.
For example, the maintainers guide might look like this:
The text was updated successfully, but these errors were encountered: