-
Notifications
You must be signed in to change notification settings - Fork 943
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
Roadmap - Shutdown Docs AE Glossary #6111
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
website/docs/docs/test-terms.md
Outdated
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.
delete before merge
@@ -246,6 +242,9 @@ var siteSettings = { | |||
//showLastUpdateAuthor: false, | |||
|
|||
sidebarCollapsible: true, | |||
exclude: [ | |||
'hover-terms.md' |
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.
Prevents hover-terms
page from being built on the site. This file is only used for storing hover snippets which are used in the custom Term
component.
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. Confirmed snippet appears to be working correctly and redirects are also working as expected.
Just curious, I'm assuming the ones on the sheet that are marked Need to consolidate
will be merged into a single WWW blog post?
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.
Hey @JKarlavige This looks great! I just had a few questions. Thanks for getting this PR up 🙇🏻♀️
hoverSnippet: Data lineage provides a holistic view of how data moves through an organization, where it’s transformed and consumed. | ||
|
||
data-warehouse: | ||
displayText: data warehouse |
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.
@JKarlavige It looks like we lost the links to https://docs.getdbt.com/docs/environments-in-dbt and https://docs.getdbt.com/terms/view on the about environments page. Will links and terms no longer be compatible?
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.
Does this refer to the links when clicking the terms themselves on a page? If so - yes, these hover snippets will no longer be linkable, only the hover snippet functionality remains in place.
If term URLs are hit directly, they will either redirect to the migrated WWW blog page if that term was migrated, or redirected to the WWW blog index if that term wasn't migrated.
I did update two files where we were linking to term pages as Docusaurus was flagging them as broken links. But even if any links are still out there, they will redirect rather than 404ing when hit
website/docs/docs/test-terms.md
Outdated
|
||
This has displayText set but no hoverSnippet set: <Term id="noHoverSnippet" /> | ||
|
||
This should NOT show a hover snippet (but should still show children): <Term id="demo">Demo</Term> |
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.
Hey @JKarlavige This looks correct, but not sure what you mean by it should still show children?
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.
Good question! If the Term
component is used but the id
isn't found in hover-terms.md
, it would still show the children of the component, in this case the text Demo
. These are just some test cases i added for us to test when reviewing the PR. But i will remove all of these before merge.
website/docs/terms/hover-terms.md
Outdated
hoverSnippet: This is a demo term hover snippet | ||
displayText: Yay demo term | ||
|
||
noDisplayText: |
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.
Not sure of the use case here. Also it seems to not be working on the test page, but likely it's that I'm not understanding what it should be doing 😆
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.
Yeah feel free to disregard these ones 😅 i just wanted to add some test cases for us to review to ensure the pages won't break in certain scenarios. The noDisplayText
example falls back to displaying the id
text itself ("noDisplayText") on the page, if both the displayText
property and children
are missing.
Here's an actual use case on this functionality, say we had a term snowflake
in the hover-terms.md
file:
snowflake:
hoverSnippet: This is the hover snippet text when hovering over the Snowflake term
Then the Term
component is used like this on a page: <Term id="snowflake" />
Since it doesn't have a displayText
property set in hover-terms.md
, and child text isn't passed into the component (for example: <Term id="snowflake">this is child text</Term>
), it will fallback to showing the id
on the page instead, which is snowflake
.
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.
Ah! Thanks for the explanation!
website/docs/terms/hover-terms.md
Outdated
noDisplayText: | ||
hoverSnippet: No Display Text hover snip | ||
|
||
noHoverSnippet: |
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.
What's the use case for noHoverSnippet?
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 example shows how a term will appear on a page if a term is set in hover-terms.md
, but the hoverSnippet
property isn't set for that term. So if the Term
component is used on a page: <Term id="noHoverSnippet" />
, and this term doesn't have a hoverSnippet
set, it will just display plain text on the page with no hover snippet functionality
@runleonarun One other update - we have 3 terms that the SEO agency is helping consolidate into one to migrate to the WWW blog, they are: Rather than pausing the project while waiting on those pages to be consolidated into one blog post, we will leave those 3 term pages live for now on docs. Then once a new blog post is together and published, we will go back and shutdown these final 3 term 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.
Thanks for the explanations JK! Approving.
What are you changing in this pull request and why?
We are moving 10 key terms from the Docs glossary over to the WWW blog. The goal is to maintain the hover snippet functionality where the
Term
component is used throughout the site, while shutting down the individual term pages.The terms we are migrating vs. what we are redirecting to the blog index can be found here. This defines what redirects point to specific WWW blog pages vs. what falls under the wildcard redirect pointing to the blog index.
This PR:
docs/terms.md
file to maintainhoverSnippet
functionality using Term componentDocumentation
Our documentation on terms/hover snippets have been updated: https://www.notion.so/dbtlabs/How-to-use-Docusaurus-glossary-terms-hover-snippets-dc5cc7bfc05848fd8ea3906239da97da?pvs=4
Previews
Verify hover snippets show correctly on test page:
https://docs-getdbt-com-git-roadmap-ae-glossary-dbt-labs.vercel.app/docs/test-terms
Verify hover snippet works on prod pages where
Term
component is used:ELT & ETL term pages should remain live as part of this initial update. They will be migrated to the WWW blog at a later date:
TODO Before Merge
test-terms.md
pagehover-terms.md