Closed prjctimg closed 8 months ago
Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for a maintainer to decide if it is ready to be worked on.
To claim an issue, please leave a comment that says ".take". If you have any questions, feel free to ping a maintainer.
This issue was mentioned by @takanome-dev here
Is your feature request related to a problem? Please describe. Switching between repositories just to update the documentation is slowing down productivity.
Describe the solution you'd like Is it possible to include the documentation site inside of this repository and maybe switch to a simpler template but mantain our customizations ?
Describe alternatives you've considered Using a workflow that builds the documentation for every release and update the markdown files. This will in turn trigger a redeployment of the entire site. Similar to what the
gh-pages
npm package 📦 does.Additional context Can we make a component inventory so that we build our UI with consistency in mind. These components will also be used in the demo app which will showcase the library in action.