Add link to our deployed Storybook instance in our docs
Categories
(Toolkit :: UI Widgets, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox112 | --- | fixed |
People
(Reporter: tgiles, Assigned: tiwari.abhishektiwari23, Mentored)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug, Whiteboard: [fidefe-reusable-components-ms3] [lang=js] [lang=md])
Attachments
(1 file, 1 obsolete file)
Now that Bug 1766701 has landed and our existing Storybook/reusable components documentation is more accessible, we should also link to our deployed storybook instance in these docs. Here is the deployed Storybook instance. We should probably add this link in the Storybook for Firefox doc under the title heading
Updated•2 years ago
|
Reporter | ||
Comment 1•2 years ago
|
||
To help Mozilla out with this bug, here's the steps:
- Comment here on the bug that you want to volunteer to help.
This will tell others that you're working on the next steps. - Download and build the Firefox source code
- If you have any problems, please ask on Element/Matrix in the
#introduction
channel. They're there to help you get started. - You can also read the Developer Guide, which has answers to most development questions.
- If you have any problems, please ask on Element/Matrix in the
- Start working on this bug.
- You will need to modify README.storybook.stories.md and add a link to https://firefoxux.github.io/firefox-desktop-components/?path=/story/docs-reusable-widgets--page after the first sentence in this doc.
- You can verify your changes using
./mach doc
and waiting for all the docs dependencies to be installed and ran.
- If you have any problems with this bug, please comment on this bug and set the needinfo flag for me. Also, you can find me and my teammates on the
#reusable-components
channel on Element/Matrix most hours of most days.
- Build your change with
mach doc
and verify your changes in the resulting doc. Also check your changes for adherence to our style guidelines by usingmach lint
. - Submit the patch (including an automated test, if applicable) for review. Mark me as a reviewer so I'll get an email to come look at your code.
- How to Submit a Patch
- This is when the bug will be assigned to you.
- After a series of reviews and changes to your patch, I'll push it to autoland.
- If there are changes requested, please read the "To update a submitted patch" section to ensure you don't accidentally create a duplicate revision!
- Your code will soon be shipping to Firefox users worldwide!
hi, I am outreachy applicant and would like to be assigned to this issue
Assignee | ||
Comment 3•2 years ago
|
||
Hello, I am also looking at this issue, as it is unassigned now. I have figured out the code where changes are required. But I have a doubt here. You mentioned adding the link at the end of the first sentence in the doc. This means after the end of this whole line, "Storybook is a component library to document our design system, reusable components, and any specific components you might want to test with dummy data." Or do we have to add the link for the word "storyBook" because when some clicks on storyBook will get retired to this new link? Please let me know. Thanks.
Assignee | ||
Comment 4•2 years ago
|
||
I have made the changes as mentioned. Should I make a commit for review ?
Assignee | ||
Comment 5•2 years ago
|
||
Updated•2 years ago
|
Assignee | ||
Comment 6•2 years ago
|
||
Sir, I have deleted the previous file I was working on, so I am making a new patch for it.
Assignee | ||
Comment 7•2 years ago
|
||
Comment 9•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Description
•