-
Notifications
You must be signed in to change notification settings - Fork 849
chore(website): restructure docs folder (2 of 2) #8594
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
Conversation
8a675d1
to
5e27a7a
Compare
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.
This PR is of high prio and it's amazing you've done it in such a short amount of time! For the future, it'd be great to break it down into smaller PRs or more granular commits because I have to admit, it's hard reviewing and testing everything at once. Once you see the number of files growing, it's best to cut it short.
Great job! 🎉
Testing notes
Designers > Icons redirection is broken:
Redirects to https://eui.elastic.co/pr_8594/new-docs/docs/display/icons
, should be https://eui.elastic.co/pr_8594/new-docs/docs/components/display/icons/
instead.
All the highlights links are broken:
They redirect to e.g. https://eui.elastic.co/pr_8594/new-docs/docs/layout/flex
, should be https://eui.elastic.co/pr_8594/new-docs/docs/components/layout/flex/
.
I didn't notice this change before but Code used to be in Editors and Syntax, and now there's only one element there, "Markdown". Do you think we should move it back, leave it as is?
@@ -1,10 +1,7 @@ | |||
--- | |||
slug: /containers/accordion |
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 suggestion:
Personally, I'd prefer to remove the front matter altogether and keep using the h1 Markdown heading. We'd leverage plain Markdown syntax over MDX syntax which is more approachable. Is there a reason why we're moving it to the front matter?
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.
thinking about it more I also prefer the plain markdown syntax
Is there a reason why we're moving it to the front matter?
we were using both and I thought we could make it consistent, then chose the front matter one because it renders with theme/DocItem/Content
and also thought it looked better 🤷
I say we follow your suggestion and change this back to plain Markdown
@@ -1,12 +1,10 @@ | |||
--- | |||
slug: /display/icons | |||
id: display_icons_overview | |||
title: Icon |
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 suggestion:
Maybe we could keep it simple and always name it "Icon" or "Icons"? Whichever is fine.
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.
I think Icons 🤔
EUI offers a wide variety of components. This section is organized topically with individual pages containing live example, usage recommendations, guidelines, and props. | ||
|
||
The adjacent [patterns](../patterns/) section provies additional guidance for handling use cases that cross multiple components. | ||
The adjacent [patterns](../patterns/index.mdx) section provies additional guidance for handling use cases that cross multiple components. |
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.
The adjacent [patterns](../patterns/index.mdx) section provies additional guidance for handling use cases that cross multiple components. | |
The adjacent [patterns](../patterns/index.mdx) section provides additional guidance for handling use cases that cross multiple components. |
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.
thank you!
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.
doubt:
Should this be index.mdx
instead?
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.
yes, it should! good catch 🙏
- **EuiPageTemplate.BottomBar** extends [EuiBottomBar](../../containers/bottom_bar.mdx) | ||
- **EuiPageTemplate.EmptyPrompt** extends [EuiEmptyPrompt](../../display/empty_prompt/index.mdx) | ||
- **EuiPageTemplate.BottomBar** extends [EuiBottomBar](../../containers/bottom-bar.mdx) | ||
- **EuiPageTemplate.EmptyPrompt** extends [EuiEmptyPrompt](../../display/empty-prompt/index.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.
outside the scope:
Could we fix the formatting in the Demo underneath? Also, there seems to be something breaking syntax highlighting right after this demo. Feel free to skip.
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.
will fix 💅
thanks a lot @weronikaolejniczak for the great (and super fast as well!) review broken links are fixed (7e3d878)
@ryankeairns changed this in #8547 (I'd leave it as is) I'll fix the |
|
💚 Build SucceededHistorycc @acstll |
Preview staging links for this PR:
|
💚 Build Succeeded
History
cc @acstll |
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.
LGTM! Thanks for tackling this, @acstll 💪🏻
Summary
Resolves #8583
Resolves #8576
Resolves #8573
(how do you make this "resolves" one line?)
Following up on #8547 and https://github.com/elastic/eui-private/discussions/282
Scope
Part 2 of #8588, second and last batch of changes to make it easier/faster to review.
The affected folders inside
website/docs
are:components
utilities
(moved out ofgetting-started
)Changes
gettings_started/
→getting-started/
,color_mode.mdx
→color-mode.mdx
overview.mdx
files toindex.mdx
to avoid needed to set theslug
explicitly e.g.content/overview.mdx
withslug: /content
→content/index.md
slug
andid
fields from front matter, leaving that task to Docusaurus' defaultslink.id
field in_category_.yml
with default id, e.g.id: content_writing
→id: content/writing/guidelines
sidebar_position
andtitle
fields where neededQA
Visit the affected parts of the site and check:
Important
Pay special attention to Forms, there are no more "Category pages", toggles are plain toggles
Staging links: