Clear information about the initial, broken code in the Tutorial on svelte.dev/tutorial/

[lukaszpolowczyk]

Clear information about the initial, broken code in the Tutorial on https://svelte.dev/tutorial/

You are currently entering a Tutorial and what do you see ?:

• some code
• some instruction

Is it obvious to anyone that the code in the tutorial is broken? No!
I had it like that at the beginning, but I also read that others have it (in this svelte review).

What to do with this?

I think ABOVE the tabs/files bar there should be a Red bar, with info like:
"PRE-CODE, NOT FUNCTIONING - Take a tutorial to get it working"

This bar can have a cross to hide the belt with a warning, as he knows.

Additionally:
In addition, the "Show me / Reset" button is at the end of the tutorial, sometimes you can not even see it without scrolling.
Maybe it should also be on the warning bar? For example:
"PRE-CODE, NOT FUNCTIONING - Take a tutorial to get it working or [Show me]"

Another option:

• Pop-up message with the same information - definitely worse solved.
• The bar above the tutorial content - but that's a worse place.

[tanhauhau]

i believe the instructions in the beginning of the tutorial is quite clear.

[lukaszpolowczyk]

@tanhauhau Oh no... Really?
Do you really have this approach to improvements?

This is an obvious improvement, and you just throw it away, hoping to read the manual?
This is not something I will fight for.

It's sad that you have this approach.
There is a problem and a simple way to solve it? Don't throw it away!

This is not only my problem, but also an article on medium.com or another blog that mentioned this problem as not being obvious.

It is not obvious or intuitive. The interface should describe itself.

If you have this approach, there is no chance of popularizing svelte.

I wrote here about a way to remove some small initial barriers. It's always a good idea to remove them...

[antony]

@lukaszpolowczyk The tutorial is designed to be read and followed. If people aren't willing to read and follow the tutorial then they might as well not do it at all, and no amount of clutter, caused by plastering duplicate instructions all over the place is going to fix that. Why impede the experience for people willing to put the 45 minutes of effort into reading and following the tutorial, to assist the impatient who just want to skim and rush through it. It doesn't make any sense.

[lukaszpolowczyk]

"If people aren't willing to read and follow the tutorial then they might as well not do it at all"
I believe this is a wrong approach.
You are assuming someone's ill will.
In my opinion, you have to assume that someone might misuse your tool.

I do not consider this info bar to be something terrible, as it could be simply closed.

It wouldn't be a copy of the instructions, just one simple sentence.

[lukaszpolowczyk]

@antony Hey, I see you guys did what I asked.
In this:
https://learn.svelte.dev/tutorial

:D

And you said " It doesn't make any sense". xD

When someone on your team does it, it suddenly makes sense? xDD

@tanhauhau

[antony]

Hi Łukasz,

As always, we may implement ideas which go against our own judgement based on feedback from users, plural, not singular.

We admire your passion, but a breadth of feedback and experience over time is more insightful than that of a single individual and allows us to make decisions that benefit a larger group of users and negatively impact fewer users.

[lukaszpolowczyk]

@antony And sad, and funny. :P

But I take it you still think it's a bad idea?
You were just "outvoted"? :D

I gave the example of this blog has a medium (unfortunately I didn't have an url) who also had a similar opinion.
So my issue was not as a single person.

But I'm not droning on.

I am glad that you guys are implementing this because it will just be more convenient and intuitive.