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
{{ message }}
This repository has been archived by the owner on Dec 11, 2021. It is now read-only.
So this idea was suggested in Friday's meeting , it sounds awesome but poses some challenges. I am pointing out a few :
The user will have to navigate through our demo pages to see the effect of each change. Unless we use some caching mechanism or have pages in a tab preloaded, this may mean a little lag on low bandwidths.
We may have many components in future, making the user go through so many pages to see the effects?
We have to figure out something that gives us the best of both worlds. maybe a summary page at first and rest of demo pages in tabs or something.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So this idea was suggested in Friday's meeting , it sounds awesome but poses some challenges. I am pointing out a few :
We have to figure out something that gives us the best of both worlds. maybe a summary page at first and rest of demo pages in tabs or something.
The text was updated successfully, but these errors were encountered: