[Sistent] Add Switch component to the sistent components page
Current Behavior
Layer5 and it's projects use Sistent library to enable easy component reusability among our various projects. One such component is Switch.
Ideally, all sistent components are represented on https://layer5.io/projects/sistent/components, so a centralized usage and example documentation can be maintained. This will aid new developers to more quickly jump into contributing to the various projects. The Switch component, currently needs this representation.
Desired Behavior
Proper documentation for Switch component, similar to Button component on https://layer5.io/projects/sistent/components The documentation should include:
- Explanation of the the function that the component serves in context of it's usage.
- Code examples.
- Stylistic guidelines to be followed while using the component in code (if any).
Contributor Resources and Handbook
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.
- π¨ See Sistent Repository.
- π See contributing instructions.
- π¨ Wireframes and designs for Layer5 site in Figma (open invite)
- ππΎππΌ Questions: Discussion Forum and Community Slack.
Join the Layer5 Community by submitting your community member form.
Hey @dragon-slayer875 , I want to work on this issue. Please assign
hey, @vishalvivekm , Can You assign to me??
@sudhanshutech It seems I have been removed from the organizations. Can you assign this issue to @Sumitsh28 going by that he asked first?
Hey @dragon-slayer875 , I want to work on this issue. Please assign
Assigned.
Thank you @Vidit-Kushwaha for chiming in, please let me know if you want to work on similar opened issues, will be happy to assign.
Hello @Vidit-Kushwaha @vishalvivekm, if there hasn't been progress on this issue, I would love to work on it.
@Anand-Theertha Go ahead π
Hey , @Vidit-Kushwaha , Can you assign this issue to me>
Ohh no, I missed the assignment on this issue, really sorry. I will open up a PR by the end of this week. @Vidit-Kushwaha
@Anand-Theertha, looks we need to reassign the issue.
@vishalvivekm can I take up this issue?
Sure go ahead @M-DEV-1
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@vr-varad Iβm interested in continuing work on this issue from where @M-DEV-1 paused. Can I proceed?
Sure @Rajesh-Nagarajan-11