Need meshmate to assist in start contributing to meshery Doc

Hi everyone,

I need a meshmate to assist in kickstarting my contribution to meshery docs. It has been very difficult as a newcomer to get started in contributing . I have attended the newcomers meeting, search the contributing documentation as well as github/issue . In the github issue, it has been very difficult getting unassigned issues and as a newcomer am not very good in identify a flaw in the documentation and open an issue against it. It is very good to start at opened “good first issues” before graduating to the level of identifying and opening issue against it.

Hi Saka, welcome back, and well done on the groundwork you have already done. Attending the newcomers meeting and reading the contributing docs first is exactly the right start.

For docs contributions, the best place to begin is the open good first issues list, and to filter for ones with no assignee yet. Two lists to watch:

Meshery docs and site issues: Issues · meshery/meshery.io · GitHub
Meshery docs issues: Issues · meshery/meshery · GitHub

I checked both lists just now and the open docs good first issues I could see are already assigned, so please pick from the list rather than from this reply, and comment on the issue asking to be assigned before you start work. New unassigned ones do open up regularly.

On spotting doc flaws to open issues against: the easiest way in is to follow a guide yourself and note anywhere the steps, commands, or screenshots do not match what you actually see. Outdated terminology, broken links, and steps that no longer work are all good first issues to file. Describe what you tried, what you expected, and what happened instead, and a maintainer can confirm it.

The newcomers guide at A dedicated page for the newcomers | Meshery and the Friday newcomers meeting are good places to keep asking questions, and the newcomers channel in Slack is there for quick help too. Happy to point you at a specific issue once an unassigned docs one opens up, just ask here.

thanks @Kate_Suttons for your prompt response. All the advice is taken.