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
Currently, we render the hyperlinks to the publish/preview pages in a toast that never closes. This is done because we want to ensure that the faculty doesn't miss the link and they can always click the link on time.
But one drawback to this approach is - let's say the faculty makes multiple edits and after each, they try to preview the page. The UI can easily become cluttered like this:
I suggest to just display toast for throwing errors or notifying if it is successful. But where exactly do we render these hyperlinks? I have three approaches in my mind.
Pop a tooltip over the button and this tooltip can be faded when the link is clicked.
Render "Here is the link" instead of the button and once it is clicked, hide the former and show the latter.
We can send them the links via notification.
Open to more suggestions. Let's decide what's the best way to go.
Note: Resolving this issue will require a running setup of CMS and its APIs as well.
The text was updated successfully, but these errors were encountered:
Currently, we render the hyperlinks to the publish/preview pages in a toast that never closes. This is done because we want to ensure that the faculty doesn't miss the link and they can always click the link on time.
But one drawback to this approach is - let's say the faculty makes multiple edits and after each, they try to preview the page. The UI can easily become cluttered like this:

I suggest to just display toast for throwing errors or notifying if it is successful. But where exactly do we render these hyperlinks? I have three approaches in my mind.
Open to more suggestions. Let's decide what's the best way to go.
The text was updated successfully, but these errors were encountered: