Open nfiniteset opened 6 years ago
This is feasible
Looks like have a couple of options as a starting point
autodesk.github.io
. We could build a bare version of the repository into that branch where there's a directory hig
and a directory storybook
in that that corresponds to /packages/storybook/storybook-static
on master. I'm assuming this could be done using the ci master build script. Then our storybook would appear at autodesk.github.io/hig/storybook
.
We could have the master build script copy /packages/storybook/storybook-static
to some place like /docs/hig/storybook
. Which would correspond to autodesk.github.io/hig/storybook
We'd have to be mindful of what we put in /docs
in this case
Thoughts?
As a developer outside the VPN I can read the docs so I can use the library
Acceptance:
Add a step in our build process to publish the storybook to our repo's GitHub pages.
Continue publishing it to
storybook.hig.autodesk.com
as well.