-
Notifications
You must be signed in to change notification settings - Fork 515
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
Improve affordance of interactive examples #1775
Comments
The reset button gives a hint about the editing capability so I'm not sure how much of an issue it is. Plus the article gives specific instructions about this:
|
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. |
Can you make the cursor blink? |
https://stackoverflow.com/a/42482756 sounds like it could work … |
The examples being discussed there aren't the Interactive Examples from this repo. Those are regular MDN examples, some of which are embedded right into the pages, I tend to do mine in the css-examples repo and then embed them (which is what these are). It works, but probably isn't the most elegant solution. |
@rachelandrew Do you want me to fill an issue against another repository then? |
I'm on it :) |
First off: I'm not entirely sure, whether this issue belongs into mdn/content or mdn/mdn-minimalist. Feel free to move it if you see apt.
My trigger for opening is a tweet by @codepo8 from the other day:
I asked him what could be done to improve the experience. His idea was to show a pen.
In my experience, a pen might be understandable to some people (basically anybody who have prior experience on editing on the web. Even GitHub shows a pen to edit files). I'm not 💯 sure, whether it is universally understood, though. Perhaps a word would be easier?
That being said, it could be a sign of bad design to … expressively expose this affordance. Good design should feel intuitive.
Nevertheless, it looks like even technical people struggle with our interactive examples, which should be reason enough to think about improvements here.
The text was updated successfully, but these errors were encountered: