🎉 Documentation Section Examples Redesign#4449
Conversation
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_4449/ |
|
I've added some more context to the summary of this PR. It's going to mainly be a side-project for me, so it will move slowly. That is unless someone else is keen to take the baton. Just raise your hand here so we know whose currently working on it. There's still a good amount of refactoring to do and some bug fixes, but overall the pieces are in place. |
|
✋🏽 I'm keen to help! |
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_4449/ |
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_4449/ |
# Conflicts: # src-docs/src/views/button/button_ghost.js # src-docs/src/views/button/button_group.js # src-docs/src/views/utility_classes/utility_classes.js
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_4449/ |
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_4449/ |
cchaos
left a comment
There was a problem hiding this comment.
I'd like to wrap up this PR since I think most dependencies have been merged now. There will still be a time period where we'll need to move all the playgrounds into the examples, but I think its ok to follow up.
There's also PLENTY more do to do cleanup the code, especially with more Typescripting, but another ok for follow up.
The only other thing to consider is if we want to just comment out the getting started section for now until we have better text formatting. @miukimiu ?
| onSort = (componentName) => { | ||
| const { sortedComponents } = this.state; | ||
| if ( | ||
| !sortedComponents[componentName] || |
There was a problem hiding this comment.
This table Props column sorting, I think, is the only thing that didn't get moved to the Playground table. It still may be nice to add back in.
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_4449/ |
Yes! I commented out the getting started section. 🙌🏽 |
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_4449/ |
Also fixed some mobile styles
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_4449/ |
snide
left a comment
There was a problem hiding this comment.
I did a manual functional test of all our example pages. Overall things work extremely well. These were the only small issues I noticed.
Long prop types no longer scroll within their container.
This one actually happens in all "display" and "form" playgrounds
This one happens in a lot of the charts examples
Grr... ok 👀
Yes, there are a lot of these. And I want to do them in follow ups because I want to evaluate the "right" places to move them to; especially ones that are more than one component. Basically, it require thought and want to get this initial change in first then my task is to fix up all the pages.
😆 You're constantly pushing for this and I honestly don't thing that's a very discoverable place to put such an important navigational element. And how would the button behave? Is it a toggle button? I like the explicit tabs of "Show me the examples vs Show me the Guidelines".
I thought I had this fixed, but likely I just need to adjust for if the tabs don't exist to remove any padding and/or the whole bottom panel. |
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_4449/ |
snide
left a comment
There was a problem hiding this comment.
Approved on functionality. I think figuring out the consistent pattern for playgrounds should be a follow up.
Yep, immediately! 😸 |
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_4449/ |





... and starting to move towards playgrounds within examples
I'll be moving these bits and pieces over to new PR's as some of these updates are already in other PR's and will cause conflicts.The Buttons page is the best example usage of the new pattern.
These are the basic ideas to implement in this PR:
We don't need to take this PR and update every playground usage right now, the separate pages still work. We'll just do a slow migration after this PR merges.
Checklist
[ ] Props have proper autodocs[ ] Added or updated jest tests[ ] Checked for breaking changes and labeled appropriately[ ] Checked for accessibility including keyboard-only and screenreader modesThis probably could be better. But I'll be sure to do a follow up[ ] A changelog entry exists and is marked appropriately