-
-
Notifications
You must be signed in to change notification settings - Fork 91
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] Automatic title and meta description #863
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
import * as React from 'react'; | ||
|
||
export function getChildrenText(children?: React.ReactNode): string { | ||
if (hasChildren(children)) { | ||
return getChildrenText(children.props?.children); | ||
} | ||
|
||
if (Array.isArray(children)) { | ||
return children.map(getChildrenText).flat().filter(Boolean).join(''); | ||
} | ||
|
||
if (typeof children === 'string') { | ||
return children; | ||
} | ||
|
||
return ''; | ||
} | ||
|
||
function hasChildren( | ||
element?: React.ReactNode, | ||
): element is React.ReactElement<React.PropsWithChildren> { | ||
return ( | ||
React.isValidElement(element) && | ||
typeof element.props === 'object' && | ||
!!element.props && | ||
'children' in element.props && | ||
Boolean(element.props.children) | ||
); | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
AFAIR, we wanted to have a richer title than just the title for SEO purposes ("React Dialog component" instead of just "Dialog")
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.
Hmm I think short titles are a much better experience for the end user.
I see MUI docs do that, but I'm not a fan of how messy opening a bunch of tabs from mui.com feels
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 agree. It does look better in the browser's tabs.
@oliviertassinari, I remember you were suggesting richer titles in the past. Any opinions on this?
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.
We can put the SEO juice in the url
url:
/react-component-name
pageTitle:
Component name • Base UI
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.
We've agreed on the following for titles and URLs:
Dialog • Base UI
https://base-ui.com/react/dialog
Bonus, URLs are going to match import paths:
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.
@michaldudak Right, so why do the pages of MUI follow those patterns?
Source: https://analytics.moz.com/pro/analytics/analyze-keyword/15825137/2871441/9c418058312a1f68ac62edaa1217a2bc
Personally, I work with a small screen, my tabs are very quickly cut, I can't read them most of the time, I have learned to live without tab titles, so that's why I didn't bother so much. Or maybe it was because I always felt that onboarding is critical considering the duration developers stick to a specific stack. If someone helps win more new % users, and it's not annoying enough for them to leave, then it helps win in the long term?
We can wait to see how those pages rank. I will be curious to see. I'm creating an issue with this idea: mui/mui-public#251.