-
Notifications
You must be signed in to change notification settings - Fork 850
[EUI+] New IA #8547
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
[EUI+] New IA #8547
Conversation
0ad1148
to
11b76a0
Compare
@ryankeairns We should probably link this PR with: https://github.com/elastic/eui-private/issues/243 (and update its description, move to M1). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing job, @ryankeairns! I would say, let's just fix the conflicts and merge as is. All the comments I added are for us to fix in the future, not necessarily now. It's much better to merge imperfect than keep the PR open any longer.
Testing notes
Homepage links
There are broken links on the homepage now:
- Highlights > All components button
- Footer > Developers > Getting started
- Footer > Developers > Tokens
- Footer > Designers > Patterns
They don't use Docusaurus' Link
component and therefore it's hard to keep track of them breaking. We should probably update them to use it or useBrokenLinks
hook.
Utilities
I'd say the Utilities are much better suited in the "Components" section. They don't belong in "Getting Started" that should only scratch the surface. Currently, the developers are used to going to Components and seeing Utilities there. Additionally, although sometimes functions, the majority of the utilities are React components and hooks. I agree we could use some separation between UI components and utility components but we can do it on the same page. What do you think?
Sidebar font-size
There's some font-size inconsistency in the sidebar. I think they should be of equal font-size (probably 14px
). The bold text brings enough distinction between the pages vs folders.
Prop table
Maybe we could remove the last line in the prop table:
I think it'd look a bit cleaner.
Relative URL links
I used \[([^\]]+)\]\((?!https:\/\/)(?![^\)]*\.mdx)[^\)]*\)
regexp to find all Markdown links that are not https
links and do not contain the .mdx
file extension. These are:
packages/website/docs/components/overview.mdx
linkspackages/website/docs/components/display/beacon.mdx:13
packages/website/docs/getting_started/utilities/text_diff.mdx:70
packages/website/docs/getting_started/utilities/text_diff.mdx:298
packages/website/docs/data_visualization/types/metric_chart.mdx:20
packages/website/docs/components/forms/text/inline_edit.mdx
icon button links
I fixed these but I think we either lost the changes or have to rebase onto main:
packages/website/docs/patterns/error_messages/overview.mdx
linkspackages/website/docs/patterns/error_messages/error_warning.mdx:27
packages/website/docs/patterns/error_messages/error_validation.mdx:36
packages/website/docs/patterns/error_messages/error_pages.mdx:44
packages/website/docs/patterns/error_messages/error_help_users_avoid_errors.mdx:139
packages/website/docs/patterns/save_buttons.mdx:28
packages/website/docs/patterns/error_messages/error_banners.mdx:25
If we don't use relative file paths, we cannot leverage the preloading, prefetching and broken link detection Docusaurus capabilities.
@@ -182,19 +198,23 @@ export const PropTable = ({ | |||
> | |||
<header css={styles.header}> | |||
{showTitle && ( | |||
<EuiTitle size="m"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sidenote:
The original value m
is correct, it's just displayed incorrectly. I fixed this on #8557 using Docusaurus Heading
component which also adds an anchor and the copy anchor link icon.
<PropTable definition={docgen.EuiModalFooter} /> | ||
### Confirming an action | ||
|
||
Use a [Modal](#confirming-an-action) when you need to interrupt a user and ask them to confirm an action. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
non-blocking:
We're redirecting to itself here. Is that on purpose?
@@ -1,12 +1,42 @@ | |||
--- | |||
slug: /display/badge | |||
id: display_badge | |||
sidebar_position: 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
non-blocking:
Are we putting Badge first on purpose? Other components follow alphabetical order.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
non-blocking:
Not super crucial but the filename overview.mdx
doesn't fit here because it's a subpage of the Buttons category. I'd say we can just name it button.mdx
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
non-blocking:
The "Recommendations" page is the only subpage, so maybe we can merge it with introduction.mdx
content and move to a single testing.mdx
page?
|
||
**Keep these guidelines in mind:** | ||
|
||
* Minimize the number of callouts per page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
non-blocking:
We should either consistently used * Text
or - Text
. I used and updated the content with the latter.
@@ -184,7 +177,7 @@ If the total results are unknown, you can make a best guess based on the context | |||
|
|||
* * * |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
non-blocking:
We don't use dividers on any other pages, so we should remove it.
## Component | ||
|
||
:::tip | ||
It is strongly encouraged to use **EuiBeacon** in conjunction with [**EuiTour**](./tour). Standalone, the beacon is a visual cue that may lack context. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
non-blocking:
Sometimes, we seem to bold the component links. Do we want to do that? If so, we should think about whether we want to do it globally or locally like here. We can easily find all those links searching for [**
and should be easy to search and replace as well.
3da2298
to
aa3e4d5
Compare
Preview staging links for this PR:
|
💚 Build Succeeded
History
|
Closes https://github.com/elastic/eui-private/issues/243
Summary
Overhaul of the IA. Notable changes include:
QA
Remove or strikethrough items that do not apply to your PR.
General checklist
@default
if default values are missing) and playground toggles