Current State:
Desired State:
Contributor Resources
Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Contributors' Welcome Guide and sure to join the community Slack.
@JubayerJoy thanks for this. Have a look at https://github.com/layer5io/meshery/pulls/1388
@leecalcote, I have reviewed the PR. Some great work by @PluckyPrecious 馃殌
That PR fixes image issue.
I think windows documentation, broken logo, and ToC is not yet covered 馃槙
@PluckyPrecious, what is your thought about this?
Hi @JubayerJoy it is great if you can cover those as i'm on transit and will be off my system for now. @leecalcote what you say?
@JubayerJoy Thanks for pointing these out. I'll take this one on if you haven't started working on it already.
@chandrashritii sure, I haven't started, go-ahead 馃憤
Is this issue still open? If so, I'll take this on.
@kishore007k I'm working on this one at the moment. Let's find you another issue :)
@chandrashritii 馃憤馃
Is this issue still open?
https://meshery.layer5.io/docs/architecture is missing the images.
Hi @sbs2001, good catch!
A common practice is to open a new issue if you can't find the same issue listed or mentioned anywhere.
If you want you can create a new issue or I can open one for you if you want.
Cheers!
@JubayerJoy
If you want you can create a new issue or I can open one for you if you want.
No thanks !
A common practice is to open a new issue if you can't find the same issue listed or mentioned anywhere.
FWIW this ticket is labeled duplicate for some reason, add to that my issue is a subset of what you are proposing(atleast the title). So IMHO opening a new issue is not necessary.
@sbs2001
FWIW this ticket is labeled
duplicatefor some reason, add to that my issue is a subset of what you are proposing(atleast the title).
True, your issue is a subset of the issues mentioned in the title. It's labeled duplicate cause some of them are already covered by other tickets (You can see some of them are already fixed).
So IMHO opening a new issue is not necessary.
My point is, I am not updating this list with similar issues, so the issue you mentioned might go unnoticed.
Each time an image breaks or document is missing, it falls under this title. Should people comment again and again here to get the issue noticed?
So, why not open a new issue?
@JubayerJoy Thank you for pointing out the documentation mistakes.
The issue with the missing links in the architecture page have been captured in #1675.
The windows page has been updated in PR #1657
The installation guides have been fixed in #1673
Other issues mentioned in the description have also been duly fixed through past PR's by other contributors. New issues should be opened to point out any future documentation errors.
//CC @leecalcote Closing this issue.