19 comments

[ 3.1 ms ] story [ 43.7 ms ] thread
(comment deleted)
First things first... hella props for just going out and doing something creative.

Things I like:

1. It's obvious where sections begin and end.

2. PLENTY or margin and padding. I know some people try to cram as much info on a single line as possible. My old eyes prefer spacing; it helps them track the text.

3. With one exception (mentioned below) the font sizes seem to "look good."

Things I might suggest are improvable:

1. It's not obvious what the show/hide button at the top of the page does at first glance. The button is at the top of the page and its effects are seen at the bottom of the page. Maybe put another copy of the button immediately above the answer section?

2. Continuing the show/hide theme, the per-answer-section show/hide button hides the content, but maintains the blank space in the document. That seems "wrong" to me since I have to scroll past complete blank areas when looking at it on my phone. And I think we could have no end of discussion whether those buttons should be at the top or bottom of the section that gets hidden. I'd just suggest trying putting them at the top and see if they look better to you.

3. The "Objective", "Question", "Result", "Answer" sub-section headers seem like they should be a little bigger.

I don't know if you tested some of these options, and completely defer to you if you tested them and they look even weirder. Just my $0.02. Mostly looks great.

Great, thank you for your answer. I will make a few adjustments.
NP. I love seeing people experiment. Thanks for listening.
1) At the top of the page, the button reads: "SHOW ANSWERS."

2.1) There is no more blank space.

2.2) Buttons are at the top right of each QA.

3) Headers font size: 1.1rem -> 1.2rem

It looks better to me!

Does not render at all (blank screen) with javascript turned off by uBlockOrigin.
I see. Thank you for reporting. P.S. There are no ads or trackers of any kind on the website.
I can't see how to make the site usable without JS. It uses WebComponents (https://lit.dev) and JS here and there.
The individual “Show Answer” buttons are doing nothing on mobile Safari, though the top toggle button does work. Those fixed top buttons are also eating up a lot of space on a phone.

Otherwise, looks quite nice!

> Those fixed top buttons are also eating up a lot of space on a phone.

It should be fixed now.

> The individual “Show Answer” buttons are doing nothing on mobile Safari.

It should be fixed.

            :host(.hidden), :host(.hidden) * {
                /*
                 * display: none; does not work because of a bug.
                 * bug: https://bugs.webkit.org/show_bug.cgi?id=188259
                 */
                visibility: hidden;
                width: 0;
                height: 0;
            }
I'm a fan of the Little Schemer, so I'm happy you're trying this format. I hope you keep trying more than once. Sometimes these things take a while to get right and find the sweet spot.

Little Schemer was instantly appealing because it starts so simply:

    1. Is it true this is an atom? : atom
    2. Is it true this is an atom? : turkey
    3. Is it true this is an atom? : 1942
    6. Is it true this is a list? (atom)
    7. Is it true this is a list? (atom turkey or)
I came to your page wanting to learn P5.js, but it started a little too involved.

Consider starting with a few simpler questions and answers like this, which also helps just teach the format and interface, before asking the reader to work their brain much harder.

1. I have re-written a good part of the article to make the learning curve less steep.

2. The concepts to be illustrated are now mentioned in the "Discussion" section.

It is still not as detailed as The Little Schemer, but is it any good anyway?

“Show answer” should better be below the question, where the answer appears. Also so you don’t have to scroll up again for longer questions.
That would help a lot. Tuning on top of that would be graphic design, and maybe animated transition (if the graphic design isn't enough to expose what was happening).
Ok! Buttons are now below questions, is it better?
Yes, but Hide Answer should either be in the same place (so you can quickly toggle), or (for longer answers) it needs to automatically scroll up again because otherwise you land below the next question; or both.

Showing/hiding larger content with good UX isn't easy. Sometimes it's better to just stick with normal browser navigation (such as linking to answers on a separate page), where the browser takes care of proper navigation state.

A solution may be to avoid longer answers.