-
Notifications
You must be signed in to change notification settings - Fork 63
Conversation
Storybook and Tailwind configuration previews: Ready Storybook: https://wordpress.github.io/openverse-frontend/_preview/1868 Please note that GitHub pages takes a little time to deploy newly pushed code, if the links above don't work or you see old versions, wait 5 minutes and try again. You can check the GitHub pages deployment action list to see the current status of the deployments. |
Size Change: -7.64 kB (-1%) Total Size: 810 kB
ℹ️ View Unchanged
|
src/locales/en.json
Outdated
"new": "For users of the legacy CC Meta Search site, the Meta Search feature on {openverse} will look familiar. The goal was to ensure that the functionality is not lost, but is updated and embedded within our new search engine for openly licensed content. In addition, the Meta Search feature builds on this functionality, allowing us to quickly add new sources to Meta Search as we discover them, and support new content types in the future, as we expand.", | ||
"content": "For many years, Creative Commons has offered its users a dedicated search portal for searching platforms that have CC licensing filters built in. In fact, this is still maintained at {old}.", | ||
"old": "oldsearch.creativecommons.org", | ||
"new": "For users of the legacy CC Meta Search site, the External Sources feature on {openverse} will look familiar. The goal was to ensure that the functionality is not lost, but is updated and embedded within our new search engine for openly licensed content. In addition, the External Sources feature builds on this functionality, allowing us to quickly add new sources to External Sources as we discover them, and support new content types in the future, as we expand.", |
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 blocking for this PR, but I think this statement is probably not true since we've removed the filters from the External Sources.
} | ||
}, | ||
"relationships": "This functionality also allows us to start conversations and build relationships with sources that may like to be included in {openverse} in the future. Finally, we can also offer external sources of media types we do not include in {openverse} yet, but plan to.", | ||
"explanation": "You can find links to external sources at the bottom of every {openverse} search results page; on pages for searches which return no results; and on pages for media types we do not yet support but intend to." |
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.
"explanation": "You can find links to external sources at the bottom of every {openverse} search results page; on pages for searches which return no results; and on pages for media types we do not yet support but intend to." | |
"explanation": "You can find links to external sources at the bottom of every {openverse} search results page, on pages for searches which return no results, and on pages for media types we do not yet support but intend to." |
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.
Would comma be better here?
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.
Everything is updated, redirect works well, and the text updates are great. I hope this time we can merge this :)
Thanks you for updating the snapshots, @obulat! |
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.
These are very welcome changes.
My biggest suggestion is to quote "External Sources" when using it in a sentence as a feature name or to lowercase it and integrate into the sentence otherwise (leaving comments for both such scenarios). It's way too generic a phrase to read on it's own as the name of a feature.
Approving so as not to block.
src/locales/en.json
Outdated
"title": "How does the External Sources feature work for indexed media types?", | ||
"demo-label": "Layout of External Sources for indexed media type, like images", |
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.
Since "External Sources" is so generic (unlike "Meta Search" which was a proper feature name) maybe we should quote it when using in sentences.
Co-authored-by: Dhruv Bhanushali <dhruv_b@live.com>
@WordPress/openverse-frontend Could someone help me here? I merged in
|
I'm able to run them locally, but it seems like it might be the build timing out for you based on the small logs you shared. Can you share the full build logs for you locally? They do run in CI as well, so I'd be surprised if it's a build performance issue given how small the CI boxes are compared to our local machines. |
Fixes
Fixes #1197
Description
Renames meta search everywhere and improves + simplifies the page copy.
Testing Instructions
Checklist
Update index.md
).main
) or a parent feature branch.Developer Certificate of Origin
Developer Certificate of Origin