-
Notifications
You must be signed in to change notification settings - Fork 1
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
UI for Long form Content on Record Page #22
Comments
Hey @amy-jung, not sure what is best but sharing some thoughts here:
I think this won't be scalable and would make our catalog less flexible. I personally think that having less info but more consistent is the way to go. One question: Should things like https://delegate.starknet.io/ be in the catalog? It's a super dynamic page, and isn't a "DAO event", is it?
A would be easy to implement (we could have a different UI for the detail record page when there is no content), and C too (maybe a bit ugly haha) One thing that also comes to mind for some non-text pages that are important: craft a summary / medium description (+ link to the source). It'd be manual tho (but might be worth it for some important ones!) |
I'm adding here a comment I made at #17 I think we should avoid working too much on cleaning stuff and take an approach similar to Google: Index all the content from each HTML document, show a summary (or a small text around the searched term) for each document at the search result, and then link to the original content. What do you think? |
For now, we're going with: Just a short excerpt and then "More on [link]" Mock up is "Desktop - Record View (html not available)" |
How should we show content on a Record page that aren’t text heavy?
Such as:
or
A lot of the Google Docs / Notion pages are like this. I can design a few iterations of "Content" sections, but we’ll have endless formats that will never be as clean as the original source itself. I’ve been thinking through these few UI perspectives, but curious if you see better solutions? A few ideas I had were:
A) In these cases, only provide a link out to the source (instead of hosting the full content)
B) Limit accepted content to these specific formats
C) Embed or Iframe the content directly (ie. https://archive.ph/5b6Xa), but miss out on searchable content (which in future iterations with AI it might not be a problem?)
The text was updated successfully, but these errors were encountered: