-
Notifications
You must be signed in to change notification settings - Fork 718
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
docs: reorganize query docs #735
Conversation
- give queries a top-level nav entry instead of nesting under DOM Testing Library - give each query its own page - reorganize pages like "Which Query" under the new heading - update internal links and redirects
7043cbb
to
dcf41db
Compare
@@ -0,0 +1,418 @@ | |||
--- |
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 and the other pages in the queries folder are the main changes in this PR
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.
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.
Really appreciated that!
give queries a top-level nav entry instead of
nesting under DOM Testing Library
I expected it to appear in the left sidebar and it took me some time to find the new link. What does everyone think about moving it to the left sidebar?
Frameworks > DOM Testing Library > Queries
now just lists a single link to /docs/queries/about/
. Would it be simpler to redirect from /docs/dom-testing-library/api-queries
to /docs/queries/about/
and remove internal usage of /docs/dom-testing-library/api-queries
?
I really like this change. |
Co-authored-by: Sebastian Silbermann <[email protected]>
Co-authored-by: Adrià Fontcuberta <[email protected]>
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 looks great 🎉
const { getByText } = within(document.getElementById('messages')) | ||
const helloMessage = getByText('hello') | ||
const messages = document.getElementById('messages') | ||
const helloMessage = within(messages).getByText('hello') |
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.
way more clear 👌
Co-authored-by: Adrià Fontcuberta <[email protected]>
I think I got rid of these, but left the page in the DOM TL tree so that it would at least contain the full API if you are browsing library docs directly. It might make sense to add some more text later that explains the relationship between the core APIs, DOM Testlng Lib, and framework wrappers.
One thing I like about giving it its own section is that we can keep the nav list expanded on page load. I could see "Core API" or just "API" being the title, in order to make room for an "interactions" (events) section, but I think the top nav having both "Docs" and "API" would be confusing
I have been thinking we basically need all the concepts from my talk here https://www.youtube.com/watch?v=b8SOFNc_X_A pulled into a docs page. On top of that, we should give all of the top-level APIs the same treatment as the Queries, so you can browse most of them at a glance from the left nav rather than clicking into pages. |
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.
Looks great 👍
I'm pretty happy with how this brings up some more sections into the top-level and makes it apparent where there are gaps. As @afontcu pointed out, events could use a cleanup. If anyone wants to jump on that soon, feel free. Merging this iteration now. |
Looks great, I think that's a really good separation :) |
@alexkrolick I think that this PR accidentally pushed a |
@MatanBobi you're right, feel free to clean up |
nesting under DOM Testing Library
Closes #485