-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
🍱 Interactive widgets #42550
Labels
Comments
Btw this is a bit of an advanced and fancy example of how Microsoft does it with their Loop components (thanks @marcoambrosini for sharing). Fully collaborative, including live cursor and avatars on top: 00.StayInSyncHd_video_en-us-0x1080-6439k.mp4 |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
8 tasks
This was referenced Jan 17, 2024
This was referenced Jan 18, 2024
Closed
4 tasks
This was referenced Feb 8, 2024
Main parts are done, remaining issues are tracked separately. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Goal
Current link previews provide a simple, static preview but in lots of contexts it would be very helpful if users could work more interactively with the linked resource without navigating away to the actual app of it.
This is partly addressing a gap to competitor products like Notion, Microsoft Loop, Sharepoint when on the Collectives app, but also in other Nextcloud parts like Talk where team/discord can display more interactive widgets within the chat.
The goal is to add an additional way of rendering link preview widgets that provide more information, interactivity and possibly useful actions right away. The degree of what functions should be available for a widget may need further discussion on the individual apps.
Scope
Out of scope
Tracking issues
Follow-ups
Not planned at the moment
## More detailed draft notes
Notion examples:
Design spec
I had a call with @jancborchardt to outline the implementation in more detail:
Implementation questions
The text was updated successfully, but these errors were encountered: