You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, the current frontend part of the search functionality is still in its original "proof of concept" form. In other word: it's bad. It looks bad, it has surprising behavior (can't "close" the search, ...), has several bugs, and all of that. The code structure is also not ideal, I think.
We really have to take a good look at that again to make it look pretty and more functional. Pagination and filtering should also be considered (albeit not necessarily implemented right away).
Here are some random notes I collected on this topic:
Some style examples we could use as basis: one, two.
Probably just make search a proper overlay over the current route (and make query parameter search the trigger)
Put the video thumbnails on the right side
Have an icon for video/page/series on the left somewhere so that it's easy to see what kind of item you are seeing
separate creators with dot icon, not comma
show video timestamp
if there is no creator, dont show creator
The text was updated successfully, but these errors were encountered:
Have an icon for video/page/series on the left somewhere so that it's easy to see what kind of item you are seeing
One thing to note here is that currently, we only search for events and realms (aka pages) and not series. Sure, many series have their own realm, but I don't think it's possible to easily infer whether that realm has any other content.
So if we want to include every series, I think the we need to modify the search to also include "direct link" series pages.
If we have to prioritise (and I think we have to) I would skip searching both series and content pages and focus on "video search" (including metadata). To me, integrating
slide content,
subtitles, and
displaying search results along a video timeline
are more relevant.
Unfortunately, the current frontend part of the search functionality is still in its original "proof of concept" form. In other word: it's bad. It looks bad, it has surprising behavior (can't "close" the search, ...), has several bugs, and all of that. The code structure is also not ideal, I think.
We really have to take a good look at that again to make it look pretty and more functional. Pagination and filtering should also be considered (albeit not necessarily implemented right away).
Here are some random notes I collected on this topic:
Some style examples we could use as basis: one, two.
search
the trigger)The text was updated successfully, but these errors were encountered: