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 fill in the blanks questions #788

rgaiacs opened this Issue May 10, 2018 · 3 comments


None yet
3 participants

rgaiacs commented May 10, 2018

I don't like how the "fill in the blanks" type of question is render.

screenshot from 2018-05-10 16-47-35

The use of ____ as the blank is not 100% clear to me. I would prefer to have something like

screenshot from 2018-05-10 16-44-17

In the previous screenshot, I have <input> to make clear to the reader were are the blanks. The limitation is that we can't use

$ cat 
> ~~~
> $ cp <input></input> .
> ~~~


$ kramdown 
  <pre><code>$ cp &lt;input&gt;&lt;/input&gt; .

And I don't know of any way to tell kramdown to escape the HTML tags. I would like to suggest to use &#9617;&#9617;&#9617;&#9617; instead of ____ to represent the blanks.

screenshot from 2018-05-10 17-10-46

I know that the rendering doesn't look like blanks but is the [UTF-8 block elements]( that I found more suitable. We can reword the exercise to "fill the shade" instead of "fill the blanks".


This comment has been minimized.


rgaiacs commented May 10, 2018

@ErinBecker what do you think about this from the pedagogical point of view?


This comment has been minimized.


ErinBecker commented May 10, 2018

I haven't personally had trouble with learners understanding the use of ___ as blanks, but I've only taught this lesson once. If you've noticed that people have trouble understanding those as blanks, then I'm all for changing the formatting to make that more clear. The shaded blocks look nice to me.


This comment has been minimized.


gcapes commented May 11, 2018

I've taught the lesson several times and it's always been clear to the learners. I think adding &#9617 to the .md files is more confusing, and time consuming if someone wants to add or change a fill in the blanks exercise.

See here google image results for fill in the blanks --- they're all lines (underscores).

So sorry, but this is a very strong vote against the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment