Learn to Write Code owns the curriculum: lessons, explanations, and the order concepts are introduced in. Coders Rock does not teach any of that -- it practices what LTWC already taught. A challenge here may assume you've seen a concept, and may link back to the lesson that covers it, but it never becomes the lesson itself. If a challenge needed a concept LTWC hasn't taught yet, the fix is a new LTWC lesson, not a workaround written into a challenge brief.

That split shows up directly in the site structure: Coders Rock currently has 8 challenge sets, and each one has a `lessonSlug` pointing at the LTWC lesson it practices -- Variables & Data, Operators & Comparisons, Input/Output & Comments, Program Structure & Sequence, Conditions & Branching, Loops & Repetition, Functions & Reuse, and Objects & Blueprints, in that order. Follow a lesson on LTWC, then come here and open the matching set -- the slugs line up on purpose.

One direction this rule keeps sharp: a challenge brief says what output to produce, never how to produce it. "Show these four steps in the order that makes sense" is a challenge brief. Explaining what a sequence is, or why order matters in a program at all, is a lesson's job -- LTWC's, not this site's.

Everything above runs in this page, on your own machine. There is more of it on the practice pages.