Skip to content
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

Some UX changes to make it clearer what mode user is in and faster to get back to editing #2

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

protostork
Copy link

Hi @simonxeko, lovely extension, works really well. I made a couple of UX tweaks for personal use, which you might want to consider merging if you like them.

A quick preview below:
image

In summary, the modifications do the following:

  1. They allow you to dismiss the preview when clicking on the actual preview box, which takes you back to the composer with the cursor focused where you had left off. This seems like it would be more natural and expected behaviour, since users might find themselves wanting to edit the preview and click on text they would expect to be editable. (the preview button also focuses the composer input element now, which is a bit smoother for workflow).

  2. The preview button is now highlighted with the Button--danger style (red in the default template), to make it very obvious that the preview is currently active to avoid some potential confusion for users. I found it wasn't necessarily clear for less technical users, whether it was wysiwyg or a passive preview.

  3. Along the above lines, while in preview mode, a grey 'eye' icon from font-awesome is rendered as a watermark behind the preview window. I tested this on mobile and desktop and it seemed fine, but your mileage may vary on whether you like this. I found it a useful secondary indicator that the text was an uneditable preview.

Do please let me know if any queries or feedback.

Ps.: Am a bit new to github, so I just saw the webpack dependency upgrade in composer.json - sorry, that should not have been included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant