carletex
commented
1 year ago Hey @amy-jung, not sure what is best but sharing some thoughts here:
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 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) 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?)
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!)
damianmarti
amy-jung
How should we show content on a Record page that aren’t text heavy?
Such as:
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?)