New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate Lookbook for admin components #624
Comments
|
@joemasilotti i never integrated lookbook into a project, would you like that I take this one? |
|
If you're up for it then go for it! Please post updates when you can as I'm really excited about this and want to see it live. If I don't hear back in 7 days I'll reach out and see how you're doing. |
|
@joemasilotti cool, thanks! I'll keep updated here and probably start some thread in twitter to document the process 🙌🏼 |
|
That would be amazing – please do! |
|
@joemasilotti Small update here. I already installed the gem and documented the easiest component. Everything have been going well so far, but I needed to do a small trick with the base components of the previews that we can discuss later. Current result: BTW, the default route for this is |
|
Nice – awesome progress!
Feel free to post a WIP PR with a comment or GitHub review comment and I can take a look. Happy to get it started earlier if the code will trickle throughout the changes. |
More and more View Components have been added to the
Admin::namespace the past few weeks. I'd love to be able to preview them on their own and together as a page. This could be especially helpful for new folks to the project as they can see examples without diving into code.A PR addressing this issue should:
Admin::ListComponent,Admin::Tables::TableComponent, andAdmin::Forms::ContainerComponentPlease don't add all the component previews in this PR. This will be a pressure test of how Lookbook works, is integrated, and what we can customize. Then we can go back and add the rest when we are sure it's the right path!
Also, I'm not interested in the experimental pages feature (yet). For now the 3 "component" previews could be under a "Pages" folder.
The text was updated successfully, but these errors were encountered: