Fixes some typos and missing words + Feedback #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey @slightlyoff, thanks for letting me checking out your draft!
I just fixed some typos and missing words.
In the "Essential Skills" section as well as the "HTML + CSS First" and "JS: Maybe?" sections is one aspect with which I tend to disagree, especially the sentence "[…] highest scorings given to pure HTML + CSS answers".
I am a strong believer in picking the tool with the least power — so HTML first, then CSS, but if necessary also JS. I have seen it too often (and did the mistake myself obviously) that developers want to solve something with HTML and CSS only, which might create a solution which is overly complicated and especially is not the most accessible one. Sometimes JS is necessary to create a truly accessible component. And knowing when to reach for JS (and when not) is a very important skill to me.
I think with the sentence "Some candidates may solve problems in this style by proposing a bit of backend templating plus some HTML and CSS;", you mean that those components can instead be implemented using some backend templating (changing a tab, opening a menu, or whatever). Is that correct? If so, I agree that backend logic should be in place in case JS cannot be executed (for whatever reason), but part of fundamental frontend skills to me is also creating the best possible UX and, imho, that — in certain cases — definitely involves JS.